Understanding WebLogic (JMX) monitoring

What’s WebLogic (JMX) all about in LoadRunner? If you are not J2EE background professional and caught up in a load test for WebLogic servers, this article will be useful to you as we’ve put together information to help you get a better understanding of JMX (Java Management Extensions). We will be going through the fundamentals of JMX and how it works in together with LoadRunner. We will also be touching on the reference list of available counters provided by WebLogic. If you like to know the configuration details, look out the Monitor Reference that comes together with the installer (which is pretty easy to configure). Read the rest of this entry »

Parsing error. Details: host localhost,port 1112, line: 1. Reason: Invalid at the top level of the document.

Parsing error.
Details: host localhost,port 1112, line: 1.
Reason: Invalid at the top level of the document.
.
Contents: java.lang.Exception:java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogoc.admin.mbean, Administrators] [MsgId:MMSG-47587]

Background information: I’m monitoring 4 WebLogic servers using WebLogic (JMX) Monitor in LoadRunner and adding their JMX stats into Controller. Upon adding the subsequent server, the error appeared after entering the username and password to the Controller. I’m using LoadRunner 9.0 and Weblogic 8.1 in this context. Read the rest of this entry »

How do we determine which WebLogic thread is causing CPU contention using PsList?

As mentioned in the title, this is specified to WebLogic application instance. The purpose of doing this is to find out which thread is consuming the most CPU usage and what it is doing at that point of time. This is especially useful when your instance is running at 100% utilization and you want to troubleshoot the problem.

To do that, you have to download the utility, PsTools from Microsoft Sysinternals. PsTools has a command, PsList that can look at the thread level on the OS. Read the rest of this entry »