IBM Support

IT19841: UNABLE TO RESOLVE MESSAGE IN DEPLOYED RESOURCE FILE WHEN THROWING MBUSEREXCEPTION IN A JAVACOMPUTENODE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a user tries to throw an MbUserException in a JavaCompute
    node and reference a message in a deployed properties file then
    the message will not be found when deployed in an Application.
    The user will see the text "Unable to resolve message" in the
    generated BIP4367 error message.
    This lookup will work fine if the JCN and properties files is
    deployed to the integration server.
    

Local fix

  • N
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus who try to reference a custom
    message in a deployed properties file in a JavaCompute node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a user tries to throw an MbUserException in a JavaCompute
    node and reference a message in a deployed properties file then
    the message will not be found when deployed in an Application.
    The user will see the text "Unable to resolve message" in the
    generated BIP4367 error message.
    This lookup will work fine if the JCN and properties files is
    deployed to the integration server.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT19841

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-23

  • Closed date

    2017-05-25

  • Last modified date

    2017-05-25

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020