IBM Support

JR53310: YOU RECEIVE CWLLG0594E: TEAMWORKSEXCEPTION: TWOBJECT SHOULD HAVE BEEN ACTIVATED AFTER DE-SERIALIZATION VIA ACTIVATE()

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In IBM Business Process Manager (BPM) V8.5.6.0, you might
    receive the following
    com.lombardisoftware.core.TeamWorksException after the business
    object (TWObject) is deserialized because the activate() method
    is not called:
    
    EJBWorkflowMa E   CWLLG0594E: An exception occurred while
    initializing the runnable thread. Error:
    com.lombardisoftware.core.TeamWorksException: TWObject should
    have been activated after de-serialization via activate() method
    
    com.lombardisoftware.core.TeamWorksException: TWObject should
    have been activated after de-serialization via activate() method
     at
    com.lombardisoftware.core.TeamWorksException.
    asTeamWorksExceptio
    n(TeamWorksException.java:136)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContextHelper.getExecutionContextOfTask
      (ExecutionContextHelper.java:174)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean$3.doInTransaction
      (EJBWorkflowManagerBean.java:750)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean$3.doInTransaction
      (EJBWorkflowManagerBean.java:748)
     at com.lombardisoftware.server.core.TXCommand$2.call
      (TXCommand.java:85)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport$3.doInTransaction
      (ProgrammaticTransactionSupport.java:500)
     at org.springframework.transaction.jta.
      WebSphereUowTransactionManager$UOWActionAdapter.run
      (WebSphereUowTransactionManager.java:306)
     at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.
      runUnderNewUOW(EmbeddableUOWManagerImpl.java:791)
     at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.
      runUnderUOW(EmbeddableUOWManagerImpl.java:370)
     at org.springframework.transaction.jta.
      WebSphereUowTransactionManager.execute
      (WebSphereUowTransactionManager.java:252)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.executeInNewTransaction
      (ProgrammaticTransactionSupport.java:488)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.execute
      (ProgrammaticTransactionSupport.java:349)
     at com.lombardisoftware.server.core.TXCommand.
      executeInDeadlockRetryLoop(TXCommand.java:83)
     at com.lombardisoftware.server.core.TXCommand.
      execute(TXCommand.java:72)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.doResumeWorkflowEngine
      (EJBWorkflowManagerBean.java:748)
     at com.lombardisoftware.server.ejb.workflow.
      EJBWorkflowManagerBean.resumeTask(EJBWorkflowManagerBean.
      java:358)
     at com.lombardisoftware.server.ejb.workflow.
      EJSRemoteStatefulEJBWorkflowManager_82478d70.
      resumeTask(Unknown Source)
     at com.lombardisoftware.server.ejb.workflow.
      _EJBWorkflowManagerInterface_Stub.resumeTask
      (_EJBWorkflowManagerInterface_Stub.java:347)
     at com.lombardisoftware.component.common.workflow.
      EJBWorkflowManagerDelegateDefault.resumeTask
      (EJBWorkflowManagerDelegateDefault.java:107)
     at com.lombardisoftware.component.common.workflow.
      EJBWorkflowManagerDelegateWebSphere$2.run
      (EJBWorkflowManagerDelegateWebSphere.java:52)
     at java.security.AccessController.doPrivileged
      (AccessController.java:338)
     at com.lombardisoftware.client.delegate.common.
      WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive
      (WebsphereDelegateHelper.java:204)
     at com.lombardisoftware.client.delegate.common.
      WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive
      (WebsphereDelegateHelper.java:188)
     at com.lombardisoftware.component.common.workflow.
      EJBWorkflowManagerDelegateWebSphere.resumeTask
      (EJBWorkflowManagerDelegateWebSphere.java:50)
    Caused by: java.lang.IllegalStateException: TWObject should have
    been activated after de-serialization via activate() method
     at com.lombardisoftware.core.TWObject.getActiveForm
      (TWObject.java:1433)
     at com.lombardisoftware.core.TWObject.getMetadata
      (TWObject.java:1307)
     at com.lombardisoftware.component.common.workflow.
      SharedObjectProcessor.getSharedObjects
      (SharedObjectProcessor.java:238)
     at com.lombardisoftware.component.common.workflow.
      SharedObjectProcessor.loadSharedObjects
      (SharedObjectProcessor.java:162)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContext.restoreAfterDeserialization
      (ExecutionContext.java:1824)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContextHelper.loadExecutionContext
      (ExecutionContextHelper.java:69)
     at com.lombardisoftware.component.common.workflow.
      ExecutionContextHelper.getExecutionContextOfTask
      (ExecutionContextHelper.java:145)
     ... 80 more
    

Local fix

Problem summary

  • The exception occurs only in IBM BPM V8.5.6 and it occurs
    because the deserialized business object was not initialized
    before it was accessed inside a process application.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.6.0 that initializes the
    business object after it is deserialized to ensure it may be
    accessed.
    
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53310:
    
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    
    2. Select APAR or SPR, enter JR53310, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR53310

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-13

  • Closed date

    2015-07-07

  • Last modified date

    2015-07-07

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R856 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 July 2015