IBM Support

JR53865: THE UCA OF THE DEFAULT SNAPSHOT IS USED INSTEAD OF THE UCA OF THE CALLER'S SNAPSHOT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you model a human service with an Invoke UCA step, select
    "Target the snapshot of the installed process application that
    contains this service" on the implementation tab, and then run
    the service with a snapshot that is not the default snapshot, it
    invokes the UCA and the inbound message event of the associated
    business process definition (BPD) in the default snapshot and
    not in the snapshot that contains this service.
    
    If the UCA's input data object is different in the two
    snapshots, you see an exception like the following exception:
    
    Ä7/9/15 11:03:49:667 PDTÜ 0000021b wle           E   CWLLG2229E:
    An exception occurred in an EJB call.  Error: Attempt to
    deserialize element of complex type <Type> failed because the
    property name '<name>' specified in the XML content does not
    exist on the specified type.
    
    com.lombardisoftware.core.TeamWorksException: Attempt to
    deserialize element of complex type <Type> failed because the
    property name '<name>' specified in the XML content does not
    exist on the specified type.
     at com.lombardisoftware.core.VariableObjectSerializer.
      deserializeComplexType(VariableObjectSerializer.java:1147)
     at com.lombardisoftware.core.VariableObjectSerializer.
      deserialize(VariableObjectSerializer.java:917)
     at com.lombardisoftware.core.VariableObjectSerializer.
      deserialize(VariableObjectSerializer.java:113)
     at com.lombardisoftware.server.eventmgr.
      UnderCoverAgentExecutor.doGet(UnderCoverAgentExecutor.
      java:139)
     at com.lombardisoftware.server.eventmgr.
      UnderCoverAgentExecutor.get(UnderCoverAgentExecutor.java:79)
     at com.lombardisoftware.server.ejb.eventmgr.EventMgrCore$2.
      visit(EventMgrCore.java:129)
     at com.lombardisoftware.bpd.runtime.engine.message.
      DefaultMessageRoutingCache.visitByUCAID
      (DefaultMessageRoutingCache.java:101)
     at com.lombardisoftware.server.ejb.eventmgr.EventMgrCore.
      executeUCA(EventMgrCore.java:125)
     
    ..
    

Local fix

Problem summary

  • IBM BPM uses several different internal message types to invoke
    a UCA. When one specific message type (UCAIDMessage) is
    processed, the snapshot name is ignored and, therefore, the UCA
    is invoked in the default snapshot.
    

Problem conclusion

  • A fix is available for IBM BPM that processes the UCAIDMessage
    so that it honors the snapshot name that comes with this
    message.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53865:
    
    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 JR53865, 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

    JR53865

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-16

  • Closed date

    2015-09-16

  • Last modified date

    2015-09-16

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 August 2023