IBM Support

PK81673: SECJ0306E WHEN WEBSPHERE RA IS DISCARDING CONFIGOBJECT DURING TX RECOVERY FOR FLATFILE. THIS CAUSES J2CA0154E AND WTRN0005W

Fixes are available

7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When starting an AppServer that has an ear with a FlatFile
    Adapter embedded as a JCA 1.5 resource adapter, the following
    errors are logged when the AppServer tries to recover these
    transactions.  This problem is similar to the problem described
    in PK78385.  The problem in this case is when the AppServer
    is trying to discard the ConfigService element it got to
    be able to access the WebSphere AppServer configuration.
    .
    [2/17/09 23:27:02:214 EST] 00000015 RoleBasedAuth E SECJ0306E:
    No received or invocation credential exist on the thread. The
    Role based authorization check will not have an accessId of the
    caller to check. The parameters are: access check method
    discard:com.ibm.websphere.management.Session on resource
    ConfigService and module ConfigService. The stack trace is
    java.lang.Exception: Invocation and received credentials are
    both null
     at
    com.ibm.ws.security.role.RoleBasedAuthorizerImpl.checkAccess(Rol
    eBasedAuthorizerImpl.java(Compiled Code))
     at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy.sec
    urityCheck(ConfigServiceServerProxy.java:1022)
     at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy$4.r
    un(ConfigServiceServerProxy.java:177)
     at
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
    troller.java(Compiled Code))
     at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy.dis
    card(ConfigServiceServerProxy.java:174)
     at
    com.ibm.ejs.j2c.RALifeCycleManagerImpl.isProviderInstalled(RALif
    eCycleManagerImpl.java:2753)
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXAResourceFactoryImpl.java:85)
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData
    .java:590)
     at
    com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTab
    le.java:514)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManage
    r.java:1896)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.j
    ava:2608)
     at java.lang.Thread.run(Thread.java:571)
    .
    [2/17/09 23:27:02:217 EST] 00000015 RoleBasedAuth A   SECJ0305I:
    The role-based authorization check failed for admin-authz
    operation
    ConfigService:discard:com.ibm.websphere.management.Session.  The
    user UNAUTHENTICATED (unique ID: unauthenticated) was not
    granted any of the following required roles: administrator,
    operator, monitor, configurator.
    [2/17/09 23:27:02:219 EST] 00000015 RALifeCycleMa E   J2CA0154E:
    The method queryConfigObjects on class ConfigService returned
    the following exception:
    com.ibm.websphere.management.exception.ConfigServiceException:
    com.ibm.ws.security.role.RoleBasedAppException: ADMN0022E:
    Access is denied for the discard operation on ConfigService
    MBean because of insufficient or empty credentials.
     at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy$4.r
    un(ConfigServiceServerProxy.java:179)
     at
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
    troller.java(Compiled Code))
     at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy.dis
    card(ConfigServiceServerProxy.java:174)
     at
    com.ibm.ejs.j2c.RALifeCycleManagerImpl.isProviderInstalled(RALif
    eCycleManagerImpl.java:2753)
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXAResourceFactoryImpl.java:85)
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData
    .java:590)
     at
    com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTab
    le.java:514)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManage
    r.java:1896)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.j
    ava:2608)
     at java.lang.Thread.run(Thread.java:571)
    Caused by: com.ibm.ws.security.role.RoleBasedAppException:
    ADMN0022E: Access is denied for the discard operation on
    ConfigService MBean because of insufficient or empty
    credentials.
     ... 10 more
    .
    [2/17/09 23:27:02:267 EST] 00000015 InboundFileRe E
    com.ibm.j2ca.flatfile.util.FlatFileVerifier
    verifyDefaultObjectName CWYFF0073E: An error occurred while
    validating the DefaultObjectName value, because it is invalid.
    DefaultObjectName = FlatFileBG  error message :
    com.ibm.j2ca.base.exceptions.BusinessObjectDefinitionNotFoundExc
    eption: Business object definition for 'FlatFileBG' in namespace
    'http://www.ibm.com/xmlns/prod/websphere/j2ca/flatfile/flatfileb
    g' not found.
    [2/17/09 23:27:02:269 EST] 00000015 ASXAResourceF <
    getXAResource Exit
    
    javax.resource.spi.InvalidPropertyException: Could not create an
    instance of a BO with the specified NameSpace.
    http://www.ibm.com/xmlns/prod/websphere/j2ca/flatfile/flatfilebg
    /FlatFileBG
     at
    com.ibm.j2ca.flatfile.util.FlatFileVerifier.verifyDefaultObjectN
    ame(FlatFileVerifier.java:804)
     at
    com.ibm.j2ca.flatfile.util.FlatFileVerifier.verifyActivationSpec
    Parameters(FlatFileVerifier.java:546)
     at
    com.ibm.j2ca.flatfile.FlatFileEventStoreWithXid.<init>(FlatFileE
    ventStoreWithXid.java:153)
     at
    com.ibm.j2ca.flatfile.FlatFileResourceAdapter.createEventStore(F
    latFileResourceAdapter.java:115)
     at
    com.ibm.j2ca.base.WBIResourceAdapter.getXAResourcesForAssuredEve
    ntDelivery(WBIResourceAdapter.java:705)
     at
    com.ibm.j2ca.base.WBIResourceAdapter.getXAResources(WBIResourceA
    dapter.java:354)
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXAResourceFactoryImpl.java:112)
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData
    .java:590)
     at
    com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTab
    le.java:514)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManage
    r.java:1896)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.j
    ava:2608)
     at java.lang.Thread.run(Thread.java:571)
    
    [2/17/09 23:27:02:272 EST] 00000015 XARecoveryDat W   WTRN0005W:
    The XAResource for a transaction participant could not be
    recreated and transaction recovery may not be able to complete
    properly. The resource was
    com.ibm.ws.Transaction.JTA.ASWrapper@4df83b2a. The exception
    stack trace follows:
    com.ibm.ws.Transaction.XAResourceNotAvailableException:
    javax.resource.spi.InvalidPropertyException: Could not create an
    instance of a BO with the specified NameSpace.
    http://www.ibm.com/xmlns/prod/websphere/j2ca/flatfile/flatfilebg
    /FlatFileBG
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXAResourceFactoryImpl.java:117)
     at
    com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData
    .java:590)
     at
    com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTab
    le.java:514)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManage
    r.java:1896)
     at
    com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.j
    ava:2608)
     at java.lang.Thread.run(Thread.java:571)
    Caused by: javax.resource.spi.InvalidPropertyException: Could
    not create an instance of a BO with the specified NameSpace.
    http://www.ibm.com/xmlns/prod/websphere/j2ca/flatfile/flatfilebg
    /FlatFileBG
     at
    com.ibm.j2ca.flatfile.util.FlatFileVerifier.verifyDefaultObjectN
    ame(FlatFileVerifier.java:804)
     at
    com.ibm.j2ca.flatfile.util.FlatFileVerifier.verifyActivationSpec
    Parameters(FlatFileVerifier.java:546)
     at
    com.ibm.j2ca.flatfile.FlatFileEventStoreWithXid.<init>(FlatFileE
    ventStoreWithXid.java:153)
     at
    com.ibm.j2ca.flatfile.FlatFileResourceAdapter.createEventStore(F
    latFileResourceAdapter.java:115)
     at
    com.ibm.j2ca.base.WBIResourceAdapter.getXAResourcesForAssuredEve
    ntDelivery(WBIResourceAdapter.java:705)
     at
    com.ibm.j2ca.base.WBIResourceAdapter.getXAResources(WBIResourceA
    dapter.java:354)
     at
    com.ibm.ws.Transaction.JTA.ASXAResourceFactoryImpl.getXAResource
    (ASXAResourceFactoryImpl.java:112)
     ... 5 more
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using XA recovery                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following message can be seen on    *
    *                      recovery path [2/17/09 23:27:02:214     *
    *                      EST] 00000015 RoleBasedAuth E           *
    *                      SECJ0306E: No received or invocation    *
    *                      credentials                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When starting an Application Server that has an ear with a
    FlatFile Adapter embedded as a JCA 1.5 resource adapter, the
    followingerrors are logged when the Application Server tries
    to recover these transactions. This problem is similar to the
    problem described in PK78385. The problem in this case is when
    the Application Server is trying to discard the ConfigService
    element it has to be able to access the Application Server
    configuration.
    .
    [2/17/09 23:27:02:214 EST] 00000015
    RoleBasedAuth E SECJ0306E:
    No received or invocation credential exist on the thread. The
    Role based authorization check will not have an accessId of the
    caller to check. The parameters are:
    access check method
    discard:com.ibm.websphere.management.Session on resource
    ConfigService and module ConfigService. The stack trace is
    java.lang.Exception: Invocation and received credentials are
    both null
    at
    com.ibm.ws.security.role.RoleBasedAuthorizerImpl.checkAccess(Rol
    eBasedAuthorizerImpl.java(Compiled Code))
    at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy.sec
    urityCheck(ConfigServiceServerProxy.java:1022)
    at
    com.ibm.ws.management.configservice.ConfigServiceServerProxy$4.r
    un(ConfigServiceServerProxy.java:177)
    at
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
    troller.java(Compiled Code))
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PK81673

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-02

  • Closed date

    2009-04-08

  • Last modified date

    2009-07-13

  • 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

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021