IBM Support

IC85036: MEDIATION FLOW CANNOT RESOLVE PORT WHEN HANDLING RESPONSE MESSAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using special characters, such as national language
    characters, in the name of a partner reference there can be
    issues seen when a Mediation Flow tries to process a response
    message.
    
    This exception may be seen due to this issue and a Failed Event
    may be generated.
     com.ibm.websphere.sca.ServiceRuntimeException:
    Cannot resolve port: MyPort
    at
    com.ibm.ws.sca.internal.scdl.resources.impl.BusResourceImpl.getE
    Object(BusResourceImpl.java:135)
     at
    org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(R
    esourceSetImpl.java:213)
     at
    org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:201)
     at
    com.ibm.ws.sca.internal.headers.impl.ManagedAsyncInteractionHead
    erImpl.eResolveProxy(ManagedAsyncInteractionHeaderImpl.java:64)
     at
    com.ibm.wsspi.sca.headers.impl.AsyncInteractionHeaderImpl.getCal
    lbackPort(AsyncInteractionHeaderImpl.java:596)
     at
    com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.getIn
    teractionInfo(MessageDispatcherImpl.java:1908)
     at
    com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce
    ssMessage(MessageDispatcherImpl.java:1625)
     at
    com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(
    ManagedMessageImpl.java:990)
     at
    com.ibm.ws.sibx.scax.runtime.handler.MFCImplementationHandler.pr
    ocessMessage(MFCImplementationHandler.java:375)
    
    You may see this issue after migrating to BPM/WESB 7.5 from a
    previous release.
    

Local fix

Problem summary

  • Special characters such as punctuation or national language
    characters in the name of a Partner Reference
    may lead to a ServiceRuntimeException due to the flow not being
    able to resolve a port.
    This is caused by issues decoding the name of the partner
    reference in UTF-8.
    

Problem conclusion

  • The code was modified to prevent the partner reference name
    being decoded
    
    This code fix was targeted to be included in the following fix
    packs:
    
    7.0.0 Fix Pack 6 (v7.0.0.6)
    7.5.1 Fix Pack 1 (v7.5.1.1)
    8.0.1            (v8.0.1.0)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC85036

  • Reported component name

    WEB ESB FOR WIN

  • Reported component ID

    5724I8200

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-02

  • Closed date

    2012-09-27

  • Last modified date

    2012-09-27

  • 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

  • R750 PSY

       UP

  • R751 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"751","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 March 2023