IBM Support

PM17190: PROBLEM TRYING TO START AN APPLICATION IN A OSGI BUNDLE WHEN USING A CODE COVERAGE TOOL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem trying to start a code coverage enabled application in
    a OSGi bundle. The exception that causes the problem is:
    
    Caused by: java.lang.StringIndexOutOfBoundsException
    at java.lang.String.substring(String.java:1092)
    at
    com.ibm.ws.eba.internal.framework.EBAClassLoader.loadLocalClass(
    EBAClassLoader.java:134)
    at
    com.ibm.ws.eba.internal.framework.EBAClassLoader.loadClass(EBACl
    assLoader.java:82)
    at $Proxy36.<clinit>(Unknown Source)
    at java.lang.J9VMInternals.initializeImpl(Native Method)
    at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users deploying OSGi applications with the  *
    *                  IBM WebSphere Application Server V7         *
    *                  Feature Pack for OSGi Applications and      *
    *                  Java Persistence API 2.0                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using a code coverage tool to      *
    *                      gather statistics from an OSGi          *
    *                      Application, an exception is seen and   *
    *                      the application fails                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An example of the exception that might be seen when
    using code coverage tools with OSGi applications is as follows:
    
    Caused by: java.lang.StringIndexOutOfBoundsException
    at java.lang.String.substring(String.java:1092)
    at
    com.ibm.ws.eba.internal.framework.EBAClassLoader.loadLocalClass(
    EBAClassLoader.java:134)
    at
    com.ibm.ws.eba.internal.framework.EBAClassLoader.loadClass(EBACl
    assLoader.java:82)
    at $Proxy36.<clinit>(Unknown Source)
    at java.lang.J9VMInternals.initializeImpl(Native Method)
    at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
    

Problem conclusion

  • The fix for this APAR is currently targeted for inclusion in
    fixpack 1.0.0.1 of the Feature Pack for OSGi Applications and
    JPA 2.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM17190

  • Reported component name

    JPA OSGI FEATUR

  • Reported component ID

    5724J0857

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-24

  • Closed date

    2010-09-10

  • Last modified date

    2010-09-10

  • 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

    JPA OSGI FEATUR

  • Fixed component ID

    5724J0857

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2020