Wednesday, June 22, 2011

EMGC 11g - What is Support WorkBench for FMW?

Support Workbench is a feature where, on identification of a problem, targeted diagnostics data is dumped in a well-known format and location, for further analysis by administrators, Oracle Support and development. In case of Support Workbench for FMW, this feature works for Weblogic Server Targets.

Support Workbench depends on:• JRF and incidence creation need to be enabled on Target WLS.
• a local EM agent is required on the host where target WebLogic server is running.

To use Support Workbench, pl. follow given steps:
a. Click on WLS target name where you see alerts
b. On WLS home page, click on ‘WebLogic Server’ drop down and select ‘Support Workbench’ or click on ‘Support Workbench Incidents’ as given in screenshot

c. This will take you to Support Workbench Page as given below.

d. Now if you click on incident number, it will ask for Weblogic credentials and host credentials.
e. On providing credentials, it will take you to another page where it will show various files that have been collected as part of this incident. You can view the various files and analyze them.

Wednesday, June 15, 2011

EM11g - [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL

EMagent is deployed on target host. Target WLS is discovered.
But only the general information about WLS is visible on EMUI. Monitoring details like JDBC, applications, JMS resources etc. are all empty.

emagentfetchlet.trc contains
2011-06-16 11:54:10,211 [nmefmgr_getJNIFetchlet] WARN  JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3://hostname:6003/jndi/ for metric weblogic_j2eeserver:server_internal:: Couldn't connect to any host Cause: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203 completed: Maybe]

Action: Verify that Target Weblogic Server Domain->Advance settings should contain Platform MBean Server Enabled. Set 'PlatformMBeanServerEnabled' to True and restart the weblogic server.

Thursday, June 02, 2011

How to view JVMD thread trace(snapshot)?

1. As mentioned in previous article(, One can view JVM thread trace via
Targets->Middleware->JVM Diagnostics->Select specific JVM from left panel.
On right panel, from POOL/JVM dropdown, select Threads->Saved Traces option. It will show all saved traces. Select any trace, it will show trace details.

2. Basically trace shows the details of all the threads.

Trace shows following tables:
a. JVM Trace Details like JVM name, Threads, CPU, HeapSize, StartDate, Duration, Samples, Description, Filetrs like
Request, Method, JVM (thread) State.
b. Resource Usage - includes % CPU , Garbage Collection info, %Heap Usage, GC Time(ms)
c. Top States
d. Top Methods
e. Threads by State
f. Requests By State
g. Methods by State

3. Threads by State shows JVM threads in various activities/waits.

4. If one clicks on a specific thread in Threads by State table, one can see the Stack Trace on top of the page.

Expand the stack trace to see the breakdown resource waits by method.
One can narrow the search by selecting the “Percent”/“Abs Numbers” to view the exact state and the time
spent in various methods.