PM15766: PMI LOGGING NOT RESUMED WHEN DMGR GOT STOPPED

Fixes are available

APAR status

Closed as program error.

Error description

When trace is enabled for com.ibm.ws.tpv.engine.*=all
(Trace for com.ibm.ws.tpv.engine.buffer.*=all)
performance monitoring infrastructure ( PMI ) logging is not
resumed if the running deployment manager (DMGR) got stopped and
started again. This is because when DMGR is down the Alarm
thread which is running and periodically getting the stats
fails because we call AdminClient for this invoke. This causes
the stats to be null because the BufferMapper and the
BufferTable were disposed of.

But even DMGR is up again, and all initialization is
happening the alarm is not running. The stats are not
getting updated to the log file.

Local fix

Not enable trace or not stop DMGR while logging.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 who uses PMI logging in a cell  *
*                  topology.                                   *
****************************************************************
* PROBLEM DESCRIPTION: PMI logging stops when the dmgr gets    *
*                      stopped.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The scenario is: Connect to nodeagent and start logging in one
server. While logging is continuing restart DMGR. Now
logging fails. You can see that the log file doesn't grow.

The problem is because we use AdminClient to invoke the PMI
data. Therefore when DMGR goes down we get a ConnectorException
and the control goes away. We won't be able to invoke anything
in the setup.

Problem conclusion

We have made necessary changes to have a control by using
AdminService when DMGR goes down, so that nothing should get
affected and we resume using dmgr AdminClient once again
whenever the DMGR is restarted.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  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
PM15766
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-03
Closed date
2010-07-21
Last modified date
2010-07-21

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
WEBS APP SERV N
Fixed component ID
5724H8800

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

PM15766: PMI LOGGING NOT RESUMED WHEN DMGR GOT STOPPED

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?