Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
When a standalone application is run using Embeddable EJB container, the transaction/partner logs get corrupted and following errors are written to the SystemOut.log: WTRN0112E: An unexpected error occured whilst opening the recovery log. The log configuration was MultiScopeRecoveryLog:serverName=\ Cell\Node\Server:clientName=transaction:clientVersion=1:logName= partnerlog:logIdentifier=2 @195300260 [FileFailureScope: Cell\Node\\Server [-274058493]] Exception in thread "Attach handler" java.lang.NullPointerException at java.io.File.<init>(File.java:262) at com.ibm.tools.attach.javaSE.IPC.getTargetDirectoryPath(IPC.java: 627) at com.ibm.tools.attach.javaSE.IPC.getNotificationSyncFile(IPC.java :511) at com.ibm.tools.attach.javaSE.AttachHandler.waitForNotification(At tachHandler.java:232) at com.ibm.tools.attach.javaSE.AttachHandler.run(AttachHandler.java :163)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of the * * Embeddable EJB Container * **************************************************************** * PROBLEM DESCRIPTION: WTRN0112E Transaction service logs * * corrupted when running multiple * * instances of the Embeddable EJB * * Container concurrently. * **************************************************************** * RECOMMENDATION: * **************************************************************** The transaction service requires persistent logs to store transaction state so that ACID properties of transactions can be maintained in the event of JVM termination. The logs must only be used by one process at a time and therefore if multiple instances of the Embeddable EJB Container are run concurrently these must specify a different location for the transaction service log directory. The transaction service log directory, if not specified, defaults to the user working directory (user.dir) of the JVM, typically the directory the JVM was invoked in. The transaction service always writes to its logs on startup and shutdown regardless of whether any transactional work is performed during the life of the Embeddable EJB Conatainer. Because of this, in cases where no transactional logging is actually required log corruption may still occur, and initialization of the Embeddable EJB Container may fail, if multiple containers are executed concurrently when configured to use the same logs.
Problem conclusion
The transaction service component was modified so that it can be configured to use in-memory logs. Such logs are not recoverable in the event of a JVM termination and should not be used if processing JTA transactions that involve multiple resources. However, if the Embeddable EJB Container is not being used to process JTA transactions that involve multiple resources then this setting may be used to allow multiple Embeddable EJB Containers to be executed concurrently without the need to allocate unique values for the transaction service log directory. To configure the transaction service in the Embeddable EJB Container to use in-memory logging the following property/value can be added to the Embeddable EJB Container's property file: com.ibm.websphere.tx.tranLogDirectory=;0 The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.13, 8.5.5.10 and 9.0.0.1. Please refer to the Recommended Updatespage for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Specify a unique value for the transaction service log directory for each concurrent invocation of the Embeddable EJB Container.
Comments
APAR Information
APAR number
PI61057
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-04-19
Closed date
2016-07-11
Last modified date
2016-07-11
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
R800 PSY
UP
Document Information
Modified date:
04 May 2022