IBM Support

IT02100: JAVA.LANG.NOSUCHMETHODERROR SEEN WHEN TRYING TO BUILD A SUBFLOW

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A java.lang.NoSuchMethodError may be seen when WESB attempts to
    build a subflow:
    
    Caused by: java.lang.NoSuchMethodError:
    com/ibm/ws/sibx/scax/mediation/model/Node.getNodeProperties()Lja
    va/util/HashMap;
    at
    com.ibm.ws.sibx.scax.mediation.component.ESBSubflowAnalyzer.reso
    lveProperties(ESBSubflowAnalyzer.java:417)
    at
    com.ibm.ws.sibx.scax.mediation.component.ESBSubflowAnalyzer.anal
    yze(ESBSubflowAnalyzer.java:212)
    at
    com.ibm.ws.sibx.scax.mediation.component.ESBFlowBuilder.createSu
    bflow(ESBFlowBuilder.java:377)
    at
    com.ibm.ws.sibx.scax.mediation.engine.MediationFlow.getSubflow(M
    ediationFlow.java:412)
    at
    com.ibm.ws.sibx.scax.mediation.engine.MediationFlow.invokeSubflo
    w(MediationFlow.java:199)
    at
    com.ibm.ws.sibx.mediation.primitives.subflow.SubflowMediation.me
    diate(SubflowMediation.java:339)
    at
    com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.per
    formInvocation(JavaMediationPrimitive.java:684)
    at
    com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.inv
    oke(JavaMediationPrimitive.java:369)7
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere Enterprise Service Bus v7 and Business
    Process Manger v7 and v8 who make use of subflows in their
    applications
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a user attempted to deploy and run their application a
    NoSuchMethodError exception was seen in the log and the flow
    failed to build. This was caused by the Node.getNodeProperties
    method having the wrong definition at compile time.
    

Problem conclusion

  • The code has been changed to ensure that the
    Node.getNodeProperties method has the correct definition at
    compile time and the flow builds without error.
    
    
    This code fix was targeted to be included in the following fix
    packs:
    
    7.5.1 Fix Pack 3 (v7.5.1.3)
    8.0.1 Fix Pack 4 (v8.0.1.4)
    
    | MDVPARTL - WESB 7.5.1.2 | Introduced by APAR IC90624
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT02100

  • Reported component name

    WEB ESB FOR WIN

  • Reported component ID

    5724I8200

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-02

  • Closed date

    2014-06-27

  • Last modified date

    2014-09-08

  • 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

    WEB ESB FOR WIN

  • Fixed component ID

    5724I8200

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC5MLJ","label":"APAR"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 September 2014