PM63258: Executing WebSphere Application Server EJBDeploy might fail with an ExceptionInInitializerError on the JcaPackage class

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to execute EJBDeploy in IBM WebSphere Application
    Server v8.0.0.2 and v8.0.0.3 on Solaris might result in error
    java.lang.ExceptionInInitializerError while attempting to
    initialize the class org.eclipse.jst.j2ee.jca.JcaPackage
    
    Problem:
    
    When executing the command ejbdeploy you obtain the following
    error:
    
    [wsejbdeploy] Exception in thread 'Thread-2'
    java.lang.ExceptionInInitializerError
    [wsejbdeploy]     at
    sun.misc.Unsafe.ensureClassInitialized(Native Method)
    [wsejbdeploy]     at
    sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFi
    eldAccessorFactory.java:25)
    [wsejbdeploy]     at
    sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory
    .java:122)
    [wsejbdeploy]     at
    java.lang.reflect.Field.acquireFieldAccessor(Field.java:918)
    [wsejbdeploy]     at
    java.lang.reflect.Field.getFieldAccessor(Field.java:899)
    [wsejbdeploy]     at java.lang.reflect.Field.get(Field.java:358)
    [wsejbdeploy]     at
    org.eclipse.emf.ecore.plugin.RegistryReader$EPackageDescriptor.g
    etEPackage(RegistryReader.java:274)
    [wsejbdeploy]     at
    org.eclipse.emf.ecore.impl.EPackageRegistryImpl.getEPackage(EPac
    kageRegistryImpl.java:133)
    [wsejbdeploy]     at
    org.eclipse.jst.j2ee.internal.J2EEInit$20.run(J2EEInit.java:351)
    [wsejbdeploy]     at java.lang.Thread.run(Thread.java:662)
    [wsejbdeploy] Caused by: java.lang.NullPointerException
    [wsejbdeploy]     at
    org.eclipse.emf.common.util.BasicEList.assign(BasicEList.java:12
    4)
    [wsejbdeploy]     at
    org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList.java
    :424)
    [wsejbdeploy]     at
    org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java
    :307)
    [wsejbdeploy]     at
    org.eclipse.emf.ecore.impl.ESuperAdapter.notifyChanged(ESuperAda
    pter.java:139)
    [wsejbdeploy]     at
    org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(Bas
    icNotifierImpl.java:380)
    [wsejbdeploy]     at
    org.eclipse.emf.common.notify.impl.NotificationImpl.dispatch(Not
    ificationImpl.java:1033)
    [wsejbdeploy]     at
    org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(N
    otifyingListImpl.java:367)
    [wsejbdeploy]     at
    org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java
    :345)
    [wsejbdeploy]     at
    org.eclipse.emf.ecore.impl.EClassImpl$9.delegateAdd(EClassImpl.j
    ava:1698)
    [wsejbdeploy]     at
    org.eclipse.emf.ecore.impl.EClassImpl$9.delegateAdd(EClassImpl.j
    ava:1)
    [wsejbdeploy]     at
    org.eclipse.emf.common.util.DelegatingEList.addUnique(Delegating
    EList.java:340)
    [wsejbdeploy]     at
    org.eclipse.emf.common.notify.impl.DelegatingNotifyingListImpl.d
    oAddUnique(DelegatingNotifyingListImpl.java:385)
    [wsejbdeploy]     at
    org.eclipse.emf.common.notify.impl.DelegatingNotifyingListImpl.a
    ddUnique(DelegatingNotifyingListImpl.java:281)
    [wsejbdeploy]     at
    org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java
    :307)
    [wsejbdeploy]     at
    org.eclipse.jst.j2ee.jca.internal.impl.JcaPackageImpl.initialize
    PackageContents(JcaPackageImpl.java:945)
    [wsejbdeploy]     at
    org.eclipse.jst.j2ee.jca.internal.impl.JcaPackageImpl.init(JcaPa
    ckageImpl.java:193)
    [wsejbdeploy]     at
    org.eclipse.jst.j2ee.jca.JcaPackage.?clinit?(JcaPackage.java:276
    )
    [wsejbdeploy]     ... 10 more
    
    Local fix:
    
    There is no known workaround at this time.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The order of the various initializers is causing trouble.
    

Problem conclusion

  • The order of the initializers was changed to correct the
    problem.
    
    The fix for this APAR is included in Rational Application
    Developer v8.0.4.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM63258

  • Reported component name

    RATL APP DEV SE

  • Reported component ID

    5725B4400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-25

  • Closed date

    2012-12-17

  • Last modified date

    2012-12-17

  • 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 SE

  • Fixed component ID

    5725B4400

Applicable component levels

  • R800 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Application Developer Standard Edition for WebSphere Software

Software version:

8.0

Reference #:

PM63258

Modified date:

2012-12-17

Translate my page

Machine Translation

Content navigation