IBM Support

JR47116: ISSUE INVOKING AN AIS SERVICE IN PROCESS SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Issue invoking an AIS service in Process Server. The AIS
    invocation in one process app works and does not work in the
    other app. The AIS service is defined in the toolkit and both
    process apps use the same version of the toolkit. Issue does
    not occurr when the app is tested in the Process Center but
    only when the app is deployed in the Process Server. The app
    where the AIS invocation is not working is deployed in the
    Process Server and is active and the default version.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Applications deployed on Process Server     *
    *                  that have an AIS service integrated.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the process application is         *
    *                      deployed to a Process Server, the AIX   *
    *                      invocation does not work.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an AIS service is invoked inside a toolkit, an exception
    occurs and the process is interupted. A similar error may be
    seen in the trace logs:
    [4/18/13 10:01:07:811 EDT] 00000135 wle_javascrip E
    Exception received
    from AIS, contactInfoServiceRepsone is null, error = <error
    type="java.lang.RuntimeException"
    description="RuntimeException">
    <cause type="javax.naming.ServiceUnavailableException"
    description="ServiceUnavailableException">
    <cause type="javax.naming.NameNotFoundException"
    description="NameNotFoundException" id="id_2">
    ...
    <toString>org.omg.CosNaming.NamingContextPackage.NotFound:
    IDL:omg.org/CosNaming/NamingContext/NotFound:1.0</toString>
    <stackTrace>org.omg.CosNaming.NamingContextPackage.NotFound:
    IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
    at
    com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFoun
    d(WsnOpt
    imizedNamingImpl.java:2557)
    The issue only occurs when the process application is executed
    on a Process Server and is the activated default snapshot.
    

Problem conclusion

  • Code changes have been made to handle the lookup properly. An
    interim fix is available on v8.0.1.1. The fix will be
    integrated into the next fix pack.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47116

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-28

  • Closed date

    2013-07-10

  • Last modified date

    2014-02-03

  • 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

  • R800 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.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 February 2014