PM60994: ILLEGALARGUMENTEXCEPTION: LOGGER PASSED AS ARGUMENT TO SETATTRIBUTE MUST BE A NAMED LOGGER

Fixes are available

APAR status

Closed as program error.

Error description

When java.util.logging.manager is configured as JVM
system property to use application specific logger, MDB listener
server session creation may fail with following exception:

[3/20/12 20:35:46:067 EDT] 0000002a WMQConnection 1
(com.ibm.msg.client.wmq.internal.WMQConnectionBrowserShadow)
[:/484e484e] Tracing exception:
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
at
com.ibm.ejs.jms.listener.ServerSessionPool.createServerSession(S
erverSes
sionPool.java:529)
at
...
...
Caused by: java.lang.IllegalArgumentException: Logger
passed as argument
to setAttributes must be a named logger
at
com.ibm.ws.logging.LoggerHelper.setAttributes(LoggerHelper.java:
192)
at
com.ibm.ejs.jms.listener.ServerSession.<clinit>(ServerSession.ja
va:167)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
... 7 more

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using their own logger with          *
*                  listener ports.                             *
****************************************************************
* PROBLEM DESCRIPTION: IllegalArgumentException when using     *
*                      custom logger.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Customers using their own logger rather than the logger
supplied with the application server will encounter the
IllegalArgumentException above if they attempt to make use of
listener ports. This is because the code made an assumption
that the application server default logger would always be
used.

Problem conclusion

The code has been altered to allow a customer specified logger
to be used.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.25 and 8.0.0.4.  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
PM60994
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
2012-03-22
Closed date
2012-05-24
Last modified date
2012-05-24

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
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
28 October 2021

Tips

PM60994: ILLEGALARGUMENTEXCEPTION: LOGGER PASSED AS ARGUMENT TO SETATTRIBUTE MUST BE A NAMED LOGGER

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

R800 PSY

Document Information

Share your feedback

Need support?