IBM Support

PI05909: WSEJBDEPLOY ANT TASKDOES NOT ALLOW FOR PASSING IN <JVMARGS>

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The wsejbdeploy ant task shows no support for  <jvmargs>:
    
    Reference: - com.ibm.websphere.ant.tasks Class WsEjbDeploy
    - WebSphere Application Server V7 Information Center:
    http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%
    2Fcom.ibm.websphere.javadoc.doc%2Fweb%2Fapidocs%2Fcom%2Fibm%2Fwe
    bsphere%2Fant%2Ftasks%2FWsEjbDeploy.html
    - WebSphere Application Server V8.5 Information Center:
    http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%
    2Fcom.ibm.websphere.javadoc.doc%2Fweb%2Fapidocs%2Fcom%2Fibm%2Fwe
    bsphere%2Fant%2Ftasks%2FWsEjbDeploy.html
    
    It is necessary to be able to pass in a jvmarg for unique
    problem scenarios, just as it is possible in the editable
    command line ejbdeploy.{bat|sh} scripts.
    There is no way to pass in jvmargs into wsejbdeploy similar to
    system properties
    
    For example:
    
    <ejbDeploy
    inputJar="${working.compile.dir}/${type}/${module.name}.input.ja
    r"
    wasHome="${was.home}"
    
    workingDirectory="${working.compile.dir}/${type}/${module.name}"
    
    outputJar="${working.archive.dir}/${type}/${module.name}.jar"
    classpathref="compile.class.path"
    codegen="${ejbdeploy.codegen}"
    dbvendor="${ejbdeploy.dbvendor}"
    keepGenerated="${ejbdeploy.keep.generated}"
    quiet="${ejbdeploy.quiet}"
    noValidate="${ejbdeploy.no.validate}"
    failonerror="true"
    trace="${ejbdeploy.trace}"
    jvmMaxMemory="${ejbdeploy.jvm.max.memory}">
    
    <systemProperty value="osgi.clean=true"/>
    <jvmarg value="-XX:DoEscapeAnalysis"/>            <<< -XX
    or -D Not Supported
    
    </ejbDeploy>
    
    
    Problem scenario ...
    
    A JVM Crash occurs in the wsejbdeploy ant task. After
    analyzing the crash dumps, JVM support determined this may
    well be an instance of Sunbug 7026700:
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7026700
    
    (This is the strongest competitor of a few options.)
    There is a Java 6  Hotspot v21 fix -
    except its not delivered in the released Java 6 stream (Sunbug
    2209127).
    This is typical when there is an established workaround also
    available:
    
    The workaround is to pass in:
    
    1) -XX:DoEscapeAnalysis
    2) -XX:+ReduceFieldZeroing
    3)
    -XX:CompileCommand=exclude,org/eclipse/jst/j2ee/model/internal/
    validation/ValidationRuleUtility,getMethod
    
    
    It is necessary to use jvmargs, since a .hotspotrc file can no
    longer be used in a JDK 1.6 JVM
    This just for WebSphere Application Server.
    It is not anything to be fixed in RAD.
    
    Being able to pass in a jvmarg, just like for ejbdeploy.{bat|sh}
    is essential for any useable wsant task like wsejbdeploy in
    production environments.
    

Local fix

  • There is no known workaround at this time when using an ant
    build script.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The wsejbdeploy ant task shows no       *
    *                      supporty for  <jvmargs>                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running the wsejbdeploy ant task a JVM Crash occurs. In
    order to avoid such a crash, the following jvmargs have to be
    passed to the jvm: -XX:DoEscapeAnalysis, -
    XX:+ReduceFieldZeroing
    ,-
    XX:CompileCommand=exclude,org/eclipse/jst/j2ee/model/internal/
    validation/ValidationRuleUtility,getMethod, but the
    wsejbdeploy ant task does not support the passing of arguments
    to the jvm. So in order to apply the workaround the
    wsejbdeploy ant task needs to be enhanced to support the
    passing of jvm args.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI05909

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-11

  • Closed date

    2014-01-22

  • Last modified date

    2014-01-22

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022