PM00408: WHEN CLICKING ON THE START MONITORING, RECEIVED ERROR MESSAGE "AN ERROR OCCURRED WHILE STARTING MONITORING FOR SERVER"

Fixes are available

APAR status

Closed as program error.

Error description

Problem:
Within the Tivoli Performance Viewer (TPV), the following error
is returned when selecting the Start Monitoring button for an
applicaiton server


"An error occurred while starting monitoring for server {0} on
node
{1}."

Admin Agent SystemErr.log shows:

[9/3/09 18:26:26:229 CDT] 00000021 SystemErr     R
javax.management.InstanceNotFoundException: TPV MBean not found
on node
fds11
 at
com.ibm.ws.tpv.engine.TPVProxyEngine.lookupTPVMBean(TPVProxyEngi
ne.java:
614)
 at
com.ibm.ws.tpv.engine.TPVProxyEngine.findTPVMBean(TPVProxyEngine
.java:58
4)
 at
com.ibm.ws.tpv.engine.TPVProxyEngine.localInvoke(TPVProxyEngine.
java:517
)
 at
com.ibm.ws.tpv.engine.TPVProxyEngine.invoke(TPVProxyEngine.java:
487)
 at
com.ibm.ws.tpv.engine.TPVProxyEngine.disableServer(TPVProxyEngin
e.java:2
06)
 at
com.ibm.ws.console.tpv.model.WebEngine.removeAllUserData(WebEngi
ne.java:
79)
 at
com.ibm.ws.console.tpv.user.UserStateRegistry$SessionListener$1.
run(User
StateRegistry.java:323)
 at
com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
Impl.jav
a:4478)
 at
com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM
anagerIm
pl.java:4566)
 at
com.ibm.ws.console.tpv.user.UserStateRegistry$SessionListener.va
lueUnbou
nd(UserStateRegistry.java:321)
 at
com.ibm.ws.session.http.HttpSessionObserver.sessionDestroyed(Htt
pSession
Observer.java:191)
 at
com.ibm.ws.session.SessionEventDispatcher.sessionDestroyed(Sessi
onEventD
ispatcher.java:160)
 at
com.ibm.ws.session.StoreCallback.sessionInvalidated(StoreCallbac
k.java:1
26)
 at
com.ibm.ws.session.store.memory.MemorySession.invalidate(MemoryS
ession.j
ava:222)
 at
com.ibm.ws.session.store.memory.MemoryStore.runInvalidation(Memo
ryStore.
java:399)
 at
com.ibm.ws.session.WsSessionInvalidator.alarm(WsSessionInvalidat
or.java:
64)
 at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:127)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)

Local fix

<Work Around>

customer can use the workaround as follows:
 Stop the server xxx11011.
 Start the other server xxx1102.
 From Adminconsole startMonitoring.

For monitoring the other server , please repeat the same steps
as above while stopping xxx1102 and starting xxx1101.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: You are not able to access Tivoli       *
*                      Performance viewer console if the       *
*                      server is managed by AdminAgent .       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When Users of Websphere Application Server Version 7.0 try to
access Tivoli Performance viewer Console from the
Administrative Console of the AdminAgent Profile for the
servers managed by Administrative Agent, the following
exception is seen:

"An error occurred while starting monitoring for server {0} on
node {1}."

[9/3/09 18:26:26:229 CDT] 00000021 SystemErr     R
javax.management.InstanceNotFoundException: TPV MBean not
found on node fds11
at
com.ibm.ws.tpv.engine.TPVProxyEngine.lookupTPVMBean(TPVProxyEngi
ne.java:614)
at
com.ibm.ws.tpv.engine.TPVProxyEngine.findTPVMBean(TPVProxyEngine
.java:584)
at
com.ibm.ws.tpv.engine.TPVProxyEngine.localInvoke(TPVProxyEngine.
java:517)
at
com.ibm.ws.tpv.engine.TPVProxyEngine.invoke(TPVProxyEngine.java:
487)
.......
.......

 With current code the query for TPVMbean would always
result in more than one when multiple servers are managed by
Administrative Agent. The current code base expects only one
Mbean reference to be returned.

Problem conclusion

The Code has been modified to cater to AdminAgent Profile
scenario also by query for the exact server instead of a query
at the node level.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM00408
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-04
Closed date
2009-12-08
Last modified date
2009-12-08

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM00408: WHEN CLICKING ON THE START MONITORING, RECEIVED ERROR MESSAGE "AN ERROR OCCURRED WHILE STARTING MONITORING FOR SERVER"

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?