IBM Support

JR48610: INVOKER.JSP WITH BUSEROUTPUT=FALSE CAUSES CLASSCASTEXCEPTION WHEN INVOKING JAVA API EXTENTION POINT TRIGGER SCRIPT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Preface:
    
    1. You have a custom tool (ASP/JSP script). This custom tool
       makes use of a html <form>.
    
    2. The <form> makes use of the hidden input parameter
       "bUserOutput" which is set to "false".
       With this setting you want to show the user output only.
       You do not want to show the request protocols or script
       context.
          <input type="hidden" name="bUserOutput" value="false">
    
    3. When submitting the <form>, you invoke the invoker.jsp,
       launching a trigger script.
    
    4. This trigger script is a Java API extension point.
    
    5. Within the JavaAPI extention point class, you try to get
       the PrintWriter from the TriggerFunctionArguments.
       Here the relevant excerpt of your Java source code:
          protected static final Context ctx =
          PIMContextFactory.getCurrentContext();
          public void trigger(TriggerFunctionArguments inArgs) {
          PrintWriter cpOut = inArgs.getOutput();
    
    
    Current situation:
    
    1. When clicking submitting your <form>, you will run into
       this error "Exception: Generic Error"
    
    2. At the same time the subsequent exception is being thrown
       in the 'exception.log' of the application server:
       <time stamp> [jsp_110: invoker.jsp] ERROR
       com.ibm.ccd.common.error.AustinException -
       CWPCM0002E:Generic error / Exception: Generic Error,
       Exception:org.apache.jasper.runtime.JspWriterImpl
       incompatible with java.io.PrintWriter
          java.lang.ClassCastException:
          org.apache.jasper.runtime.JspWriterImpl incompatible
          with java.io.PrintWriter
          at
          com.ibm.ccd.api.extensionpoints.DefaultArgumentMappings.
          getOutput(DefaultArgumentMappings.java:1248)
          at
          com.ibm.ccd.api.extensionpoints.TriggerFunctionArguments
          Impl.getOutput(TriggerFunctionArgumentsImpl.java:56)
          ...
    
    3. When using 'bUserOutput=true' (or by skipping this
       parameter), you will see your desired user output in
       addition to the session diagnostic information.
    
    
    Desired situation:
    
       When using 'bUserOutput=false', you should see your custom
       output from your Java API extension point trigger script.
    

Local fix

  • 1. Use WPC script instead of Java API extension point.
    2. Use 'bUserOutput=true'.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Master Data Management Collaboration Server              *
    * implementations are affected by this issue.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * All Master Data Management Collaboration Server              *
    * implementations are affected by this issue.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * IBM recommends that customers facing the issue reported by   *
    * this APAR apply  Master Data Management Collaboration Server *
    * version 11.0.0-FP004 to gain resolution to this problem.     *
    ****************************************************************
    

Problem conclusion

  • A fix for this problem has been included in Master Data
    Management Collaboration Server version 11.0.0-FP004
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR48610

  • Reported component name

    MDM SERVER FOR

  • Reported component ID

    5724V5100

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-25

  • Closed date

    2014-07-07

  • Last modified date

    2014-07-07

  • 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

    MDM SERVER FOR

  • Fixed component ID

    5724V5100

Applicable component levels

  • RB00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS2U2U","label":"InfoSphere Master Data Management Collaboration Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
07 July 2014