IBM Support

PM77910: LOOSECONFIGREGISTER NEEDS TO BE SYNCHRONIZED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Startup bean fails with ConcurrentModificationException.
    
    The log show the following stack trace:
    
    java.util.ConcurrentModificationException
     at
    org.eclipse.emf.common.util.BasicEList$EIterator.checkModCount(B
    asicELis
    t.java:1327)
     at
    org.eclipse.emf.common.util.BasicEList$EIterator.next(BasicEList
    .java:12
    75)
     at
    org.eclipse.jst.j2ee.commonarchivecore.looseconfig.internal.Loos
    eConfigR
    egister.findLooseApplicationIfLoaded_platform(LooseConfigRegiste
    r.java:8
    64)
     at
    org.eclipse.jst.j2ee.commonarchivecore.looseconfig.internal.Loos
    eConfigR
    egister.findLooseApplication(LooseConfigRegister.java:584)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Directo
    ryArchiv
    eLoadStrategyImpl.getLooseArchive(DirectoryArchiveLoadStrategyIm
    pl.java:
    46)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStr
    ategyImp
    l.getBinariesPath(LoadStrategyImpl.java:539)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStr
    ategyImp
    l.getAdditionalBinariesPath(LoadStrategyImpl.java:1362)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Directo
    ryLoadSt
    rategyImpl.collectFilesFromBinaries(DirectoryLoadStrategyImpl.ja
    va:1035)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.LoadStr
    ategyImp
    l.collectFiles(LoadStrategyImpl.java:744)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerIm
    pl.getFi
    les(ContainerImpl.java:473)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl
    .getFile
    s(EARFileImpl.java:2472)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerIm
    pl.getFi
    le(ContainerImpl.java:222)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleRefIm
    pl.initM
    oduleFileFromEAR(ModuleRefImpl.java:146)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleRefIm
    pl.getMo
    duleFile(ModuleRefImpl.java:120)
     at
    org.eclipse.jst.j2ee.commonarchivecore.internal.impl.EARFileImpl
    .getModu
    leFile(EARFileImpl.java:144)
     at
    com.ibm.etools.commonarchive.impl.EARFileImpl.getBindings(EARFil
    eImpl.ja
    va:690)
     at
    com.ibm.etools.commonarchive.impl.WebModuleRefImpl.getBindings(W
    ebModule
    RefImpl.java:347)
     at
    com.ibm.ws.batch.EndpointComponentImpl.getEndpointWebServicePort
    s(Endpoi
    ntComponentImpl.java:1124)
     at
    com.ibm.ws.batch.EndpointComponentImpl.getInstalledApps(Endpoint
    Componen
    tImpl.java:994)
     at
    com.ibm.ws.batch.EndpointComponentImpl.init(EndpointComponentImp
    l.java:3
    73)
     at
    com.ibm.ws.batch.BJEEStartupBean.start(BJEEStartupBean.java:56)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deployment using loose configuration    *
    *                      scenarios may encounter a Concurrent    *
    *                      Modification exception.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Application deployment using loose configuration scenarios,
    for example, Rational Application Developer,
    may fail in rare instances with concurrent modification
    exceptions. This is due to a lack of synchronization in the
    loose configuration code.
    The exception will look similar to the following:
    java.util.ConcurrentModificationException
    at
    org.eclipse.emf.common.util.BasicEList$EIterator.checkModCount(B
    asicEList.java:1327)
    at
    org.eclipse.emf.common.util.BasicEList$EIterator.next(BasicEList
    .java:1275)
    at
    org.eclipse.jst.j2ee.commonarchivecore.looseconfig.internal.Loos
    eConfigRegister.findLooseApplicationIfLoaded_platform(LooseConfi
    gRegister.java:864)
    at
    org.eclipse.jst.j2ee.commonarchivecore.looseconfig.internal.Loos
    eConfigRegister.findLooseApplication(LooseConfigRegister.java:58
    4)
    

Problem conclusion

  • Necessary synchronization was added to the loose configuration
    code.
    
    APAR PM77910 is currently targeted for inclusion in
    Service Level (Fix Pack) 7.0.0.29 of WebSphere
    Application Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM77910

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-27

  • Closed date

    2012-12-17

  • Last modified date

    2013-07-03

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK94926

       UP13/06/20 P F306

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM77910

Modified date: 03 July 2013