WebSphere EJB monitoring

Similar Questions

• WebSphere Message Driven Bean pool lack of warning

  I receive after alarm frequently to an application running on WAS v7.

  Subject: JVMNAME_c1: WebSphere Message Driven Bean pool lack of warning

  Message Driven Bean 'JVMNAME_MDB' in the 'APPLICATIONEAR' application server 'JVM1' has a high percentage of pool narrowly with a percentage of 33% Miss. This exceeds the threshold of 25% warning. Please use the following URL for details of the alarm: https://xxxxxxxxxxx.

  According to the Foglight documents:

  If you experience performance problems, check the following:

  The minimum value of the pool size is set too low, so the container must keep naming new swimming entity bean

  ·         Try increasing the minimum size of pool on your application.

  The maximum value of the pool size is set too low, so any thread tries to get an entity bean from the pool to wait in the queue

  ·         Try to increase the number of maximum pool size on your application. For example, assign something exceeds the maximum number of concurrent users.

  I tried to increase the minimum values and maximum pool one at a time, but it did not help. The pool, I changed values to is the Thread Pool found here:

  Application servers--> "server_name"--> service listening for Message--> thread pool.

  Is this the correct pool, I should be hilarious? OR should I change the found here - QCF connection/session pool resources--> JMS--> factories of connection of the queue--> "QCF_NAME"--> Session/connection pools?

  Thanks in advance.

  You have access to the developer or the person who developed the archive application?

  In general as part of an ear or application jar file there are definitions of the minimum number of Maximum number of EJB and EJB in the pool, I think they are in WebSphere ejb - jar.xml and should look something like this.

  2000

  1000

  I see this in the IBM site on weblogic for websphere migration which can give more info

  http://www.IBM.com/developerWorks/WebSphere/library/techarticles/0706_vines/0706_vines.html#sec4c

  C. max-beans-in-free-pool and initial-beans-in-free-pool

  The element of max-beans-in free-pool sets the maximum size of the EJB free pool for a specific entity bean, bean session without State or message-driven bean. Each bean class can define the size of its own pool for free using this element.

  The element initial-beans on free-pool sets the initial number of instances of bean that will fill the free pool for a specific startup bean class. Filling the free pool with bodies improves initial response times, as initial applications for the bean can be met without generating a new instance.

  In WebLogic, every bean in the application can specify that its initial and maximum pool size and pool size may vary considerably from one Bean to another class.  To determine the specific pool size, see the weblogic-ejb - jar.xml for one of these items:

  


  To specify the size of the EJB pool in WebSphere Application Server, you can add an argument of the system to the JVM:

  1. In the administration console, select application-online-online Process Definition servername server => Java Virtual Machine.
  2. Add com.ibm.websphere.ejbcontainer.poolSize to the area of Generic JVM arguments, after all the existing JVM arguments. Here is an example that sets the size of the pool maximum and minimum of 1-5 for a bean called RuleEngineEJB:

  -Dcom.ibm.websphere.ejbcontainer.poolSize = myapp #RulesEngine.jar #example. RulesEngineEJB = 1, 5

  For more details, see WebSphere Tuning EJB container .

  Hope this helps

  Golan

• Foglight can monitor the WebSphere Process Server?

  You have experience in the monitoring of IBM products like WebSphere Process Server WebSphere Application Server-based? What about Portal Server?

  Thank you.

  Technically the Java agent monitors the Websphere server and whatever it is current running on a Websphere server support.

  We have customers using the agent Java for trade and Portal Server, I have not personally tested with the bailiff, but if it's a version supported Websphere server it should work.

  A couple of things I've seen with Logon/trade:

  1. in some cases, there is a need to play with the settings of the instrumentation to exclude classes called many be instrumented.

  2 transformation of URL is necessary because the URLS have parameters embedded in them, which makes the demand model are growing very fast.

  An example of transformation of URLS can be found here

  https://support.software.Dell.com/Foglight/KB/62707

  Hope this helps

  Golan

• Java EE is not enabled so that Websphere monitoring

  Hi all

  I got the following error while monitoring the monitoring of websphere. I gave everything but all the properties correctly by restarting webpshere startup scripts I am facing the below

  error:

  Attached the agent logs in your home reference and java path.

  

  

  Please help me in this regard.

  -Shiva

  Additional accessories:

  • Agent logs.log.zip
  • 
    JavaEE not enabled.jpg

  Shiva,

  To save time if it still does not recommend a case of pension to open as soon as possible so that they can work with you in your local time zone and a webex.

  To the extent where the script what you see that it resembles this AI a websphere integration is done for Caroline.

  We always work with 5.8.1 cartridge or have you you switch to 5.9.x?

  5.8.1 you can see the options in question

  http://eDOCS.quest.com/Foglight/565/doc/cartridge-app/JavaEECartridge-install/ConfigAppServers_JavaEE.018.3.php#416350

  The text that will show you almost looks like someone made integration agent node with 5.9.x, if that was the case that integration with a regular startup script should put text right running. There are also manual integration information that specifies the flags that are used

  http://eDOCS.quest.com/Foglight/5610/doc/cartridge-APM/JavaEECartridge-install/ManuallyIntegrating.6.php#425173

  Golan

• What is the difference between Foglight JavaEE and Foglight JMX monitoring?

  Hello

  I have a plan to monitor the 6.1.0.17 WebSphere Application Server (32 bit) and 7.0.0.5 (64-bit)

  But I understand not all Foglight for JavaEE and Foglight for JMX.

  Foglight for JavaEE or Foglight for JMX is able to monitor WebSphere?

  What is the difference between Foglight JavaEE and Foglight JMX monitoring?

  Thanks in advance

  Jeans

  Just to add to the excellent answers already posted.

  We have 2 agents which allows you to monitor Java:

  1. a JavaEE agent that runs inside the JAVA virtual machine and the information of both JMX and instrumentation.

  This Agent will give you JMX information like information of JVM (use of the bunch, son etc.), of the Application and server availability information and other information of JMX/PMI (connections pools, pools of ejb, servlets, jsp, JCA and more).

  Java EE & # 039agent also gives you information of the instrumentation - RFA count and response time, exceptional output and timeout information, distribution of queries (App/DB, component technology, server, application failure), object tracking, transaction flow and stransactional between servers and data sources) and ask traces (the ability to see the trees of the RFA at the method level to know where things are slow/stuck).

  2 JMX agent is running outside the JVM but can run on the same computer or on a remote computer, this agent requires access active, JMX. This agent gives you information JVM, availability server/applications, as well as some data as the application server published using JMX (pools of connections, JCA, EJB, servlets, etc.). The JMX agent also gives you the ability to see a list of the mbeans, get the data they expose (javaEE agent gets only a predefined list (same list that is used as a template for the application servers in the JMX agent)).

  Hope this helps

  Golan

• All monitors based on java out there?

  I have a monitor that queries a database using sqlplus command which belongs to the customer oracle installed on the server. The sqlplus command is encapsulated in a standard BB shell type monitor. It works fine, but my new servers do not have or need a client oracle in this way because they use type provided via WebSphere jdbc connections.

  In order to use JDBC to DB connector, I'll need to write the monitor directly as java, or have a java agent that updates a flat file that monitors the BB.

  I don't want a java agent if I can implement directly. Has anyone ever done this before and if so, willing to share a model of the java code base?

  I'll answer my own question here with what I was able to do.

  I found myself using groovy to do this and it works fine so far. Steps below;

  1 downloaded the package binary groovy and unpacked in my Big Brother PE file

  2. Add the ojdbc6.jar file in the lib subdirectory groovy directory

  3 created a groovy.env file in the directory ext of Big Brother (with additions GROOVY_HOME JAVA_HOME and PATH set)

  4. has created a simple groovy script that queried the database and output the results to standard output

  5. wrapped in a standard model of shell of Big Brother in the groovy script

  6. added the new monitor to bb-bbexttab

• Cannot control the Websphere application

  Hi all

  I deployed JavaEE cartridge on one of my server and activated monitoring websphere, but I make very few mistakes. Please find the attached agent logs and let me know what other things I have to do yet.

  Please answer as soon as possible.

  -Shiva G

  Agent Deployment log manager seems, journal of the preinstrumentor seems fine (if you can please keep the original log names so that we know where they come from).

  Have you tried to run startServer.sh? If so, what was the result?

  Golan

• Troubleshooting for websphere inactive agents

  Hi all

  I was sent followed on my systems WAS (I'm not an administrator WAS, and I understood some basic concepts before I deployed it). One of my agent is in idle state. I need to troubleshoot why its in idle state. I checked the startServer.sh of setupCmfline.sh and Cmdline.sh, the global profile, the startNode.sh, the startManager.sh and verified that everything is OK. Then, I checked the startserver newspaper and unfortunately it didn't there nothing that refers to Foglight_Agent_Manager or JavaEE.

  So I need help with the troubleshooting steps I need to follow here. Help, please.

  Kind regards

  Roshan

  Thanks for the screenshot.

  Java agents work a bit differently in the rest of the agents, you can stop/start data collection but you can't turn them becuse they are not started by the Agent Manager.

  Java agents are launched at the start of the JAVA virtual machine, we have parameters added to a Java Server start script and when a JVM starts the beginning of the agent, when a JVM stops at the stop of the agent.

  If these settings are made on the server to run the script and starts the JVM without our parameters we get an indicator showing that the agent is stopped even if the JVM is started because the JVM is started in the past with us (if it is registered with Foglight) but the agent is not running.

  In your case, it seems that websphere Deployment Manager and server are started (which is awesome, it means that we get data) but Caroline is not started or did not begin with our parameters, it is possible, it is upward, but simply not running with our parameters (maybe they were out).

  The good news is that the Caroline should reports no information of the JVM to foglight, dashboard status agent is the only one, it appears, it should not any sort of data report to us because it's just a mechanism to stop/start the servers.

  The bad news is that, in many cases we instrument the agent node as a mechanism to add our settings on the server, so when the servers are stopped and then started, they are started with our parameters. BUT it is also possible to stop servers start with scripts who have our parameters or add parameters directly in the console of Websphere.

  If the node agent is the only thing that is not of Foglight and servers always stop/start and connect to the Foglight information and report, it's the most important thing.

  You can look in the node agent startup script and see if our parameters were out, you can check if the node agent is active (it can have all stopped) but a point in Foglight you are ok because the node agent does not appear in the dashboard application server monitor

  Golan

• IBM Websphere followed in Foglight

  Hi all

  We got a new requirement for Websphere App Server monitoring. It requires an agent manager of Java EE deployment that is created after the installation of the cartridge of Java on the server.

  In websphere, we have four profiles viz: admin officer, independent, server, domain manager and federated mode... These are the things that we have in the Agent Properties.

  Please tell us about profiles and the need for them and also the beginning of the required scripts...

  Kind regards

  Guenoun

  I think that it is correct.

  My recommendation is to save your startup script (foglight backup scripts anyway, but it gives them long names and it may be easier to save them as .orig or .bak).

  The names of scripts are referenced in the documentation

  "

  Locate your specific profile startServer, startNode or StartManager script. Save a backup copy before you continue.

  "

  The windows service is specific to a case described in the documentation of use

  Hope this helps

  Golan

• followed a WebSphere Enterprise Service Bus

  All,

  I'm watching a cluster (2 knots) WebSphere Enterprise Service Bus (IBM), but I get mixed results.  I have two groups of modules that are very well monitored, however, there are two others who are not. the error I get is 'one or more modules of the SoaEndpointLookupModIID3758 application that is running on the server application.l12276 of cell BSE are not started.' but I see on the administration console that they actually work.  So, my questions are:

  1. Has anyone encountered a similar problem before?
  2. I looked at the document that told me the properties page for javaee surveillance (https://support.quest.com/SolutionDetail.aspx?id=SOL62266) and can these settings be filter the other two groups?  the groups similar supplychain. , application. , support. , and

  The model only the problem is that both groups have massive amounts of alarms and the others are golden color.

  Thanks for the help in advance,

  Kaleb

  A new script was necessary to solve the problem.  We had to use the following to find out what the problem was.

  ===

  com.quest.common.log import. *;

  CAT = LogCategory.getInstance ("JavaEECartridge");

  AVAILABLE = "available";

  PRESUMED_UNAVAILABLE = "PresumedStopped";

  PRESUMED_AVAILABLE = "PresumedStarted";

  Not AVAILABLE = "not available";

  MODULES_STARTED = "modulesStarted";

  MODULES_TARGETED = "modulesTargeted";

  Check for blackout agent

  try {}

  agentID = scope.monitoringAgent?. agentID;

  If (agentID! = 0)

  {

  If (server ['AgentService'] .findById (agentID.toString ()) .getIsBlackedOut ())

  Returns a null value.

  }

  }

  catch (System.Exception e)

  {

  CAT.ignoreException ("WebSphereApplicationInstance.RuntimeState: could not check for agent blackout.", e);

  }

  try {}

  msObs = server.get("DataService").retrieveLatestValue (range, MODULES_STARTED);

  long freshnessTestInMin is registry ("WebSphere_ApplicationState_Freshness_Minutes");.

  No current value for 5 minutes, don't assume demand is declining.

  If ((msObs == null) |) ((currentEvalTime - () .getTime ()) msObs.getEndTime > freshnessTestInMin * 60000) {}

  Return PRESUMED_UNAVAILABLE;

  }

  If (msObs.getValue () .getMin ()! = scope.get (MODULES_TARGETED)) {}

  Return UNAVAILABLE + ":Target:"+scope.get(MODULES_TARGETED)+":Started:"+msObs.getValue().getMin();

  } else {}

  Return AVAILABLE + ":Target:"+scope.get(MODULES_TARGETED)+":Started:"+msObs.getValue().getMin();

  }

  } catch (Exception ex1) {}

  CAT.errorUnexpected ("Derived metric 'WebSphereApplicationInstance.RuntimeState' encountered an error during the evaluation." + ex1.toString ());

  Return PRESUMED_AVAILABLE;

  }

  ===

  the final solution was to adapt the script parameters derived by the following:

  ===

  Thank you for the information.  To correct the problem.  Please make the following change to the metric calculation derived.

  Of

  If (msObs.getValue () .getMin ()! = scope.get (MODULES_TARGETED)) {}

  TO

  If (msObs.getValue () .getMin)< scope.get(modules_targeted))="">

  Please save (2 save the keys to hit).  And once which is recorded, in the collection intervals then 1 or 2 (less than 5 minutes) you should start to see the State properly.  Please let me know if that solves the problem.

  ===

  After that we had to remove all java legecy objects by using the following script

  ===

  topSvc = server.get ("TopologyService");

  OBJS = #! WebSphereCell # .getTopologyObjects ();

  msg = new StringBuilder();

  CELLINPUT = "Cellnames";

  APPINPUT = "ApplicationName";

  for (obj in objs) {}

  Count = 0;

  Cellnames = obj.getName ();

  Msg. Append ("\nWebSphere Cell Name is"). Append (Cellnames);

  println ("name of the WebSphere cell is" + Cellnames);

  If (cellName.equals (CELLINPUT)) {}

  applications = obj.get("applications");

  {(app in the applications)

  appName = app.getName ();

  If (appName.equals (APPINPUT)) {}

  Count ++;

  Msg. Append("\nFound application to delete"). Append (AppName);

  println ("found application to remove" + appName);

  try {}

  instances = app.get("instances");

  for (instance in instances) {}

  topSvc.deleteObject (instance);

  }

  topSvc.deleteObject (app);

  Msg. Append ("\nSuccessfully deleted application instance.");

  println ("instance successfully removed application.");

  } catch (Exception ex1) {}

  Msg. Append("\nException while Deleting application instance:"). Append (EX1);

  println ("Exception when deleting application instance:" + ex1);

  }

  }

  }

  If (County<>

  Msg. Append("\nNo applications with name:"). Append (APPINPUT).append("found_to_be_deleted_in_Cell:").append (CELLINPUT);

  println ("no application with the name:" + APPINPUT + "found in the cell to remove:" + CELLINPUT);

  }

  } else {}

  Msg. Append("...not desired Cell, skipping.:"). Append ("\n");

  println ("... not desired cell, jump");

  }

  }

  Return msg.toString ();

  ===

  I really hope this helps someone out there

• Question of WebSphere Application Server 6.1 (after application of the fix pack)

  Hyperic HQ Server and Agent are installed on Linux, both are at version 3.2.2. I use Sun j2sdk1.4.2_16 to run the server and java 1.5.0 IBM to run the agent (for WebSphere monitoring). Before applying a patch for WebSphere 6.1 (version 6.1.0.0), Hyperic can monitor WebSphere 6.1 successfully, but after you apply the patch fix 15 (version 6.1.0.15), Hyperic can no longer be configured correctly, the error I got is like below.
  
  Unexpected error running autodiscoverer for the plugin: WebSphere 6.1 Admin: ADMC0016E: the system cannot create a SOAP connector to connect to the host localhost port 8879.
  
  Is there anyone who knows what this problem is? Help, please!
  
  Thank you

  The Solution is to fill it with soap.client.properties and ssl.client.properties.

  When you start the agent and then make sure he finds the files you want (/conf/agent.properties set loglevel debug).

  Subsequently, it should work.

  concerning
  Roadrunner

• WLDF - Instrumentation for EJB call statistics

  Hello
  
  I'm new with Weblogic and I'm looking for stats about my EJB. I am using weblogic 10.3.
  With JMX I only found data on the size of the EJB pool but no statistics (such as the execution time)
  so, I'm looking for instruments using WLDF to see whether it is possible to get the execution time of an EJB method.
  
  First of all, I try to instrument a method, I used the following WebLogic - file diagnostic.xml.
  < wldf-resource xmlns = "http://www.bea.com/ns/weblogic/90/diagnostics" >
  < instrumentation >
  < enabled > true < / enabled >
  < include >. com.gemalto * < / include >
  < wldf-instrumentation-monitor >
  < name > ConfigurationManagerBean_Monitor < / name >
  < enabled > true < / enabled >
  < action > DisplayArgumentsAction < / action >
  <-location type > before < / location >
  < pointcut > execution (public * com.xxx. * get *;) < / pointcut >
  < / wldf-instrumentation-monitor >
  < / instrumentation >
  < / wldf-resources >
  
  
  When I put this file in my EAR of MEAT - INF, the deployment is OK but I'cant see nothing in the console WLDF extension?
  
  Could you please explain a little how to properly set up my instrumentation?
  
  I thank very you much.
  C.

  Thank you for your answer, it was very helpful!

  Glad to be of assistance.

  But I have a few questions on WLDF:
  Is it possible to get information on the tab "demand" for the console extension WLDF of MBeans? In my business, we used an internal tracking platform JMX tool when I do
  you want to have as standard JMX instrumentation data.

  It's an interesting proposal... I'll bring up with my teammates and see if we can get under a request for improvement. You can programmatically access the data in the archive of the instrumentation, but you would still build the call tree yourself. I can see how providing this type of correlation data would be useful for the analytical construction and custom visualizations.

  There is also an excellent article published by Phil Aston has http://www.oracle.com/technology/pub/articles/dev2arch/2007/09/mining-wldf-xslt.html, which shows how to build a call tree using the functions of extractDiagnosticData() WLST and XSL transforms. It might give you an option to extract trees of appeal for use by the program.

  Another question, is there any XSL document to the xml export data file beautiful?

  No, we provide a schema, but no XSL transforms. Most people would have their own styles they would rather apply.

• Need help to find an adapter for a third-party monitor

  Hi all! I find myself in need of a little guidance, and I hope that someone out there will have a quick n easy for me...

  I have a Mid-2011 27 'iMac. which has two ports Thunderbolt It is taken with a Wacom tablet that I use constantly, and the other is made by an external hard drive to a solid state, which has a built-in cable to Thunderbolt (no way to hang it on a different port). I also have a 27 "HP monitor that is currently connected via an HDMI USB adapter.

  The problem is that the HP monitor is actual "jiggy" - the USB does not seem fast enough to deal with requests for the monitor. It is almost unusable. I know I should run it via a HDMI adapter Thunderbolt, but as I have already mentioned the two my Thunderbolt ports are already in use.

  Someone at - it ideas? I need sort of three to two ports Thunderbolt hooks, but I can't seem to find anything for less than $300 that would work. (I am illiterate when it comes to the different cables, adapters, ports, etc., so I hope someone can point me in the right direction by using short words... Most of the products that I travel through list specifications that me Chicane).

  The monitor has two HDMIs and a VGA port, and my iMac has a Firewire 800 port, if that helps at all...

  2011 iMac have only 1 Thunderbolt port and there is no such thing as a Mid-2011, you must have an iMac of year later, if it has 2 ports Thunderbolt. All the 27 "iMacs, from 2012 to 2015 the current have 2 ports Thunderbolt.

• MBP: monitor detected but no image except by VGA

  I have a MBP of Mid 2012 running latest El Capitan.

  When I connect to an external monitor, it is detected correctly in views (exact name, resolution, etc.), but the monitor doesn't detect any image from the portable computer. I tried the DVI - D and DisplayPort with various cables and monitors with the same result, but a picture appears if I connect to VGA. It started in the past week.

  The built-in display does not work normally.

  Looks like a hardware failure in the computer DisplayPort connector laptop, as the pins are worn or something?

  Any other ideas?

  Hi johngirvin,

  Thank you for using communities Support from Apple. Sorry to hear that you had these display problems with your MacBook Pro. Looks like you've been on the right track trying to solve this problem. If you continue to have problems, you can find the additional steps described in the following article useful, up to and including contacting Apple Support if necessary:
  

  Get help with graphical problems on the external displays connected to your Mac - Apple Support

  Concerning

• Activity monitor close unexpectedly when running in the background on the left

  Recently upgraded to Mac OS Sierra and Activity Monitor to close unexpectedly when running back plan left (do not smoke and open the activity monitor window) to a blank desktop when you use an application in another office. Clean install I tried but the activity monitor would still be down at random times when left running in the background to another empty office. Someone at - there experience this problem? For most browsing on the web using Safari on another desktop computer when Activity Monitor quit unexpectedly.

  Activity monitor also using a lot of energy since the upgrade?

  Any help would be appreciated. Thank you.

  Model: MacBook Pro (retina, 13 inches, early 2015)

  OS: macOS Sierra: 10.12 (installed via the upgrade, own installed after this problem).

  Do not forget that you are using the activity monitor version which was installed when you upgraded to Sierra. Activity monitor located in the your Mac utilities folder.

  If you have moved a previous version to a different location, it will not work.

  If you are using the correct version, post crash report. Error reports lies in the application of the Console under System reports or reports from usersand end in the suffix .crash. If you choose to do so, omit or hide any information that you consider personal.