IBM Support

JR51110: RECEIVE ILLEGALSTATEEXCEPTION USING "COPY ITEM TO", "MOVE ITEM TO", "DUPLICATE", OR "CLONE PROCESS APP"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you try to copy, move, or duplicate an item in IBM Process
    Designer or you try to clone a process application in IBM
    Process Center, you might receive an IllegalStateException.
    
    PRODUCTS AFFECTED:
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

Problem summary

  • This problem occurs because the limit setting allows only a
    certain number of dependency types for a business process
    definition (BPD). You might see the following message and
    information that is similar to what is presented in the
    following stack trace:
    
    wle E   CWLLG2229E: An exception occurred in an EJB call.
    Error: null
                                     java.lang.IllegalStateException
     at
    com.lombardisoftware.server.ejb.repositoryservices.RefactoringSu
    pport.getPOTypeDependencyOrder(RefactoringSupport.java:3245)
     at
    com.lombardisoftware.server.ejb.repositoryservices.RefactoringSu
    pport.access$300(RefactoringSupport.java:120)
     at
    com.lombardisoftware.server.ejb.repositoryservices.RefactoringSu
    pport$8.call(RefactoringSupport.java:878)
     at
    com.lombardisoftware.server.ejb.repositoryservices.RefactoringSu
    pport$8.call(RefactoringSupport.java:843)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchMan
    ager$2.withWriteAccess(BranchManager.java:308)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImpl.writeAccessWithDBLock(BranchContextImpl.java:556)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImpl.writeAccessInTransaction(BranchContextImpl.java:492)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImpl.access$800(BranchContextImpl.java:69)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImpl$2.call(BranchContextImpl.java:435)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt$1.doInTransaction(ProgrammaticTransactionSupport.java:436)
     at
    org.springframework.transaction.jta.WebSphereUowTransactionManag
    er$UOWActionAdapter.run(WebSphereUowTransactionManager.java:306)
     at
    com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderNewUO
    W(EmbeddableUOWManagerImpl.java:790)
     at
    com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderUOW(E
    mbeddableUOWManagerImpl.java:369)
     at
    org.springframework.transaction.jta.WebSphereUowTransactionManag
    er.execute(WebSphereUowTransactionManager.java:252)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt.executeInNewTransaction(ProgrammaticTransactionSupport.java:4
    31)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt.execute(ProgrammaticTransactionSupport.java:294)
     at
    com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
    rt.executeWithLongTimeout(ProgrammaticTransactionSupport.java:24
    1)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImpl.writeAccessUnderVMLock(BranchContextImpl.java:431)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchCon
    textImpl.writeAccess(BranchContextImpl.java:200)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchMan
    ager.writeAccess(BranchManager.java:332)
     at
    com.lombardisoftware.server.ejb.persistence.versioning.BranchMan
    ager.writeAccess(BranchManager.java:233)
     at
    com.lombardisoftware.server.ejb.repositoryservices.RefactoringSu
    pport.duplicateItemsWithinProject(RefactoringSupport.java:595)
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.0.1 that changes the limit
    setting.
    
     On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR51110:
    
    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 JR51110, 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

Comments

APAR Information

  • APAR number

    JR51110

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-25

  • Closed date

    2014-09-26

  • Last modified date

    2014-09-26

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R850 PSY

       UP

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

Document Information

Modified date:
26 September 2014