IBM Support

JR64656: TRANSACTION ROLLBACK WHEN REMOVING AN USER FROM THE PROJECT AREA ON BAW SERVER.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When removing an user from the project area, the step to search
    the distinguished name in the LDAP causes the transaction
    rollback. BAW server trace log showed the following stacks:
    
    
    [3/15/22 21:26:22:929 CDT] 00000158 TRANSUMMARY   3
    Transaction setRollbackOnly.
    com.ibm.ws.tx.jta.TransactionImpl@cabc5133#tid=1108851072
                                     {XidImpl:
    formatId(57415344),gtrid_length(36),
    bqual_length(40),data(0000017f908c2a03000000014214e66cf8c748db58
    a428bd596fd3ff5eb62b11793444cf0000017f908c3478000000014217b98073
    e5812fad51fb12b6d60b6b6436e262aacabc1d00000001)}
    at
    com.ibm.ws.tx.jta.TransactionImpl.setRBO(TransactionImpl.java:10
    42)
    at
    com.ibm.ws.tx.jta.TransactionImpl.setRollbackOnly(TransactionImp
    l.java:2083)
    at
    com.ibm.ws.tx.jta.TransactionImpl.setRollbackOnly(TransactionImp
    l.java:2047)
    at
    com.ibm.tx.jta.impl.TranManagerImpl.setRollbackOnly(TranManagerI
    mpl.java:356)
    at
    com.ibm.tx.jta.impl.TranManagerSet.setRollbackOnly(TranManagerSe
    t.java:221)
    at
    com.ibm.ws.extensionhelper.tran.impl.TransactionControlImpl.hand
    leException(TransactionControlImpl.java:562)
    at
    com.ibm.ws.wim.tx.JTAHelper.closeTransaction(JTAHelper.java:213)
    at
    com.ibm.websphere.wim.ServiceProvider.get(ServiceProvider.java:3
    93)
    at
    com.ibm.ws.wim.registry.util.SecurityNameBridge.getUserSecurityN
    ame(SecurityNameBridge.java:224)
    at
    com.ibm.ws.wim.registry.WIMUserRegistry$7.run(WIMUserRegistry.ja
    va:779)
    at
    com.ibm.ws.wim.registry.WIMUserRegistry$7.run(WIMUserRegistry.ja
    va:768)
    at
    com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
    Impl.java:5536)
    at
    com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM
    anagerImpl.java:5662)
    at
    com.ibm.ws.wim.security.authz.jacc.JACCSecurityManager.runAsSupe
    rUser(JACCSecurityManager.java:438)
    at
    com.ibm.ws.wim.env.was.JACCAuthorizationService.runAsSuperUser(J
    ACCAuthorizationService.java:1086)
    at
    com.ibm.ws.wim.security.authz.ProfileSecurityManager.runAsSuperU
    ser(ProfileSecurityManager.java:285)
    at
    com.ibm.ws.wim.registry.WIMUserRegistry.getUserSecurityName(WIMU
    serRegistry.java:767)
    at
    com.ibm.ws.security.registry.UserRegistryImpl.getUserSecurityNam
    e(UserRegistryImpl.java:569)
    at
    com.ibm.websphere.security._UserRegistry_Stub.getUserSecurityNam
    e(_UserRegistry_Stub.java:433)
    at
    com.lombardisoftware.userorg.ws.WSAbstractUserRegistryModule.get
    UserPrincipalNameFromUniqueName(WSAbstractUserRegistryModule.jav
    a:2883
    at
    com.lombardisoftware.userorg.AbstractAccessControllerManager.get
    UserPrincipalNameFromUniqueName(AbstractAccessControllerManager.
    java:891)
    at
    com.lombardisoftware.server.core.UserCore.getUserPrincipalNameFr
    omUniqueName(UserCore.java:1506)
    at
    com.lombardisoftware.server.core.UserCore.getUserPrincipalNameFr
    omUniqueName(UserCore.java:1398)
    at
    com.ibm.bpm.util.CaseBPMUtils.getUserNameFromUniqueName(CaseBPMU
    tils.java:292)
    at
    com.ibm.bpm.util.CaseBPMUtils.updateProjectAclFromCase(CaseBPMUt
    ils.java:187)
    at
    com.ibm.bpm.util.CaseBPMUtils.updateProjectsACLFromCase(CaseBPMU
    tils.java:100)
    at
    com.ibm.bpm.caseintegration.api.impl.WorkflowApiImpl.updateProje
    ct(WorkflowApiImpl.java:95)
    
    PRODUCTS AFFECTED:
    IBM Business Automation Workflow
    

Local fix

  • n/a
    

Problem summary

  • The problem occurs when WebSphere federated repositories (VMM)
    fails to search for a user in the LDAP because the distinguished
     name has the wrong format. VMM triggers a transaction rollback
    in this case.
    
    
    PRODUCTS AFFECTED
    IBM Business Automation Workflow
    

Problem conclusion

  • The fix suppresses the transaction rollback by suspending the
    current transaction during the LDAP search. This avoids that
    LDAP read operation affect write transactions.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR64656

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    L00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-17

  • Closed date

    2022-03-21

  • Last modified date

    2022-04-28

  • 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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"21.0.2","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 August 2022