PI69328: CWWKZ0403E error message occurs due to error Unable to acquire the global write lock in time.

Fixes are available

APAR status

Closed as program error.

Error description

A timeout occurs while installing more than one OSGi
Application (EBA) to a liberty server.  The error message
generated in the logs is:
A CWWKZ0403E: A management exception was generated when
trying to install the application <application-name> into an
OSGi framework.  The error text from the OSGi framework is:
Unable to acquire the global write lock in time.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - OSGi Applications          *
****************************************************************
* PROBLEM DESCRIPTION: The following error message is reported *
*                      when installing an OSGi Application.    *
*                      Unable to acquire the global write lock *
*                      in time.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A timeout occurs while installing more than one OSGi Application
(EBA) to a liberty server.  The error message will look like the
following:
A CWWKZ0403E: A management exception was generated when trying
to install the application <application-name> into an OSGi
framework.  The error text from the OSGi framework is: Unable to
acquire the global write lock in time.

Problem conclusion

The timeout was hard-coded in the open source Apache Aries
subsystems implementation.  For large deployments this timeout
was not long enough.  The solution is to increase the default
timeout and to provide a way to override the length of the
timeout in Apache Aries subsystems.  The default timeout can be
overriden by setting a value for the key
org.apache.aries.subsystem.lock.timeout in the
bootstrap.properties.  The value is defined in seconds. For
example, the following value in the bootstrap.properties file
sets the timeout to 2 minutes:

org.apache.aries.subsystem.lock.timeout=120

The fix for this APAR is currently targeted for inclusion in fix
pack 16.0.0.4.  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
PI69328
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-16
Closed date
2016-10-18
Last modified date
2016-10-18

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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI69328: CWWKZ0403E error message occurs due to error Unable to acquire the global write lock in time.

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

RCD0 PSY

Document Information

Share your feedback

Need support?