PI58591: DEADLOCK ON STARTUP BETWEEN TWO SERVER.STARTUP THREADS

Fixes are available

APAR status

Closed as program error.

Error description

Deadlock on startup between two WebSphere server.startup
threads.  "server.startup : 0" is waiting for "server.startup :
1", and "server.startup : 1" is waiting for "server.startup : 0"

Example:
"server.startup : 0"
Java Stack Frames:
com.ibm.ws.runtime.component.ResourceMgrImpl.
  getIsolatedClassLoader(ResourceMgrImpl.java:2032)
com.ibm.ejs.j2c.J2CUtilityClass.getIsolatedClassLoader
  (J2CUtilityClass.java:2315)
com.ibm.ejs.j2c.J2CUtilityClass.createMCFEntry
  (J2CUtilityClass.java:445)
com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.
createMCFandPM(ConnectionFactoryBuilderServerImpl.java:591)
.... more lines in stack

---
server.startup : 1
Java Stack Frames:
com.ibm.ws.eba.launcher.ServiceRegistryShelf.
  addToServiceRegistry(ServiceRegistryShelf.java:89)
com.ibm.ws.runtime.component.ResourceMgrImpl.bind
  (ResourceMgrImpl.java:549)
com.ibm.ws.runtime.component.ResourceMgrImpl.
  installResourceProvider(ResourceMgrImpl.java:1545)
com.ibm.ws.runtime.component.ResourceMgrImpl.
  installResource(ResourceMgrImpl.java:1391)
.... more lines in stack

Local fix

```
None available
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Deadlock between server startup         *
*                      threads                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A deadlock situation can occur between the resource manager
and EBA (OSGi application) framework, as indicated in the
stacks shown in the error description.

Problem conclusion

The scope of synchronization in the resource manager was
narrowed to avoid the deadlock situation.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.5.5.11 and 9.0.0.2.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI58591
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-03-04
Closed date
2016-08-24
Last modified date
2016-11-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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R850 PSY
UP
R900 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:
04 May 2022

Tips

PI58591: DEADLOCK ON STARTUP BETWEEN TWO SERVER.STARTUP THREADS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?