PK87848: NAMING EXCEPTION MESSAGE NMSV0610 IN THE SYSTEMOUT.LOG

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere Application Server Version  7.0.0.3 on AIX Operating
System

Configuring JSR160RMIConnector as the remote connector
of a nodeagent in Application Server V7.0.0.3 produces a lot of
NMSV0610I warnings and Corba-Exception in the SystemOut.log of
the deployment manager, when Stopping the nodeagent with
stopNode.sh

When using SoapConnector as the remote connector the exceptions
are logged only under FFDC

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: In SystemOut.log, some of the warning   *
*                      and exception messages could be         *
*                      ignored and are confusing to            *
*                      administrators reviewing the log file.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Some of the warning and exception messages that could be safely
ignored in SystemOut are confusing to Application Server
administrators. For example, a NMSV0610I message when stopping
nodeagent with JSR160RMIConnector could be disregarded.

Problem conclusion

Changed various Tr.warning messages which print to SystemOut
to print to FFDC and debug trace instead.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK87848
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
2009-06-03
Closed date
2009-07-31
Last modified date
2009-07-31

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:
25 October 2021

Tips

PK87848: NAMING EXCEPTION MESSAGE NMSV0610 IN THE SYSTEMOUT.LOG

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?