APAR status
Closed as program error.
Error description
When a client saves the changes to the master configuration, the
dmgr might hang because of a multi-thread issue. From the
thread dumps of the hung dmgr process the following thread:
"SoapConnectorThreadPool : 241" daemon prio=5 tid=0x130aa20
nid=0x348b waiting on monitor [0xb807f000..0xb8081a00]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at
com.ibm.ws.util.lock.WriterPriorityReadersWriterLock.startWritin
g(WriterPriorityReadersWriterLock.java:78)
at
com.ibm.ws.management.repository.FileDocument.lockForWriting(Fil
eDocument.java:678)
...
This thread is taking the information from workspace and
pushing into the master config. It holds all the other
threads hanging the server. the other threads look like:
"SoapConnectorThreadPool : 406" daemon prio=5 tid=0x135a7f8
nid=0x377a waiting for monitor entry [0xc2280000..0xc2281a00]
at
com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl.getWorkSpace(W
orkSpaceManagerImpl.java:119)
at
com.ibm.ws.management.configservice.WorkspaceHelper.getWorkspace
(WorkspaceHelper.java:79)
at
com.ibm.ws.management.configservice.ConfigServiceImpl.getUnsaved
Changes(ConfigServiceImpl.java:378)
at java.lang.reflect.Method.invoke(Native Method)
...
This fix changes the design to fix this hang.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who *
* access the configuration and save the *
* workspace concurrently *
****************************************************************
* PROBLEM DESCRIPTION: Intermittently the configuration save *
* operation hangs which further leads *
* to a dmgr hang *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When enabling the trace with
com.ibm.ws.sm.workspace.*=all=enabled, the trace log will have
the following entry.
[1/28/05 9:36:19:405 EST] 18c73c WriterPriorit d Have to wait
for a reader
Problem conclusion
Modified the locking mechanism so that the save opeation will
not hang
The fix for this APAR is currently targeted for inclusion
in 5.02.11 and 5.1.1.5.
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 |
PK00348 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-01 |
Closed date |
2005-03-30 |
Last modified date |
2005-03-30 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS NETWRK DEPL |
Fixed component ID |
5630A3601 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|