IBM Support

PM59386: Improve ejbdeploy error message when having problem creating temp files

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Errors encountered by EJBDeploy while creating temporary files
    are not clearly reported in error output.
    
    Problem:
    
    While executing ejbdeploy the following error was reported while
    invoking RMIC
    
      Installing Utility Module facet...
    [*Error] An unexpected exception was thrown.  Halting execution.
    Shutting down workbench.
    
    Error executing deployment: java.lang.NullPointerException.
    Error is null.
    java.lang.NullPointerException
            at
    com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEjbR
    eferences(BatchExtension.java:2917)
            at
    com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeplo
    y(BatchExtension.java:545)
    
    It was found that the actual problem was that ejbdeploy was
    having a problem creating temporary files.  The error message
    should have clearly indicated that this was the issue.
    
    Local fix:
    
    Ensure that where ever ejbdeploy places temporary files has
    enough space to create the required temporary files.  The amount
    of space required depends on the project being deployed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When EJBDeploy is run it generates the RMIC code into a
    temporary directory before merging it into the EJB module.
    If errors occur while generating this RMIC code then the
    full error message is not returned to the end user.
    

Problem conclusion

  • The reason for why the temporary folder could not be used is
    now written to the workspace log file. The fix for this
    APAR is included in Rational Application Developer v8.0.4.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM59386

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-29

  • Closed date

    2012-05-15

  • Last modified date

    2012-05-15

  • 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

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R800 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 May 2012