IBM Support

PI74356: JAVA.LANG.ILLEGALARGUMENTEXCEPTION: LOGGER PASSED AS ARGUMENT TO SETATTRIBUTES MUST BE A NAMED LOGGER

Fixes are available

7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When java.util.logging.manager is configured as JVM
    system property to use an application specific logger, the
    transaction service fails.
    
    A message is written in the logs indicating that the
    initialisation of the transaction service has failed:
    
    WSVR0501E: Error creating component
    com.ibm.ws.runtime.component.TxServiceImpl@57445744
    java.lang.ExceptionInInitializerError
    
    
    This is caused by the following exception:
    
    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.ws.tx.jta.TransactionImpl.<clinit>(TransactionImpl.java:
    174)
    at java.lang.J9VMInternals.initializeImpl(Native Method)
    at
    java.lang.J9VMInternals.initialize(J9VMInternals.java:199)
    at
    com.ibm.ws.tx.jta.TranManagerImpl.createNewTransaction(TranManag
    erImpl.j
    ava:184)
    at
    com.ibm.ws.tx.jta.TranManagerImpl.begin(TranManagerImpl.java:374
    )
    ...
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Transaction service fails to            *
    *                      initialise due to an                    *
    *                      IllegalArgumentException when calling   *
    *                      LoggerHelper.setAttributes method       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APAR PM83781 made a change that added calls to
    java.util.logging classes in static initialization blocks
    within the transaction service called during its
    initialisation that are only applicable to the default Logger
    class com.ibm.ws.logging.WsLogger.  If a different Logger has
    been configured then a java.lang.IllegalArgumentException
    exception occurs and the transaction service fails to
    initialise.
    

Problem conclusion

  • The transaction service code was modified to check the type of
    the java.util.logging.Logger in use before calling methods on
    the Logger that are specific to the default WebSphere
    implementation.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.43, 8.0.0.14, 8.5.5.12 and 9.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

    PI74356

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-04

  • Closed date

    2017-03-01

  • Last modified date

    2017-03-01

  • 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

[{"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":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 June 2020