Fixes are available
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
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
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
I have one cluster with two members and I have set "Use internal EJB timer service scheduler instance" on both Cluster JVM inserting the datasource alias, ecc.. I want the EJB Timers to be shared between the two JVM so I have set th same "Table prefix" name on both the JVM, and it is FIRSTP_EJBTIMER_ . It works most of the times but sometime faiuls with the following exception. [3/28/17 8:07:42:124 CEST] FFDC Exception:com.ibm.websphere.csi.EJBContainerException SourceId:com.ibm.w s.runtime.component.EJBContainerImpl.getTimerServiceScheduler ProbeId:1772 Reporter:com.ibm.ws.runtime.component.EJBContainerImpl@a61038ad com.ibm.websphere.csi.EJBContainerException: EJB Timer Service not started ... Caused by: java.sql.SQLException: [SQL0601] FIRSTT_EJBTIMER_TASK in FIRSTTDAT1 tipo *FILE esiste già. at com.ibm.as400.access.JDError.throwSQLException(JDError.java:710) at com.ibm.as400.access.JDError.throwSQLException(JDError.java:676) at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCS tate ment.java:1021) at com.ibm.as400.access.AS400JDBCPreparedStatement.execute(AS400JDB CPre paredStatement.java:1409) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJ dbcP reparedStatement.java:1032) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbc Prep
Local fix
The customer should try specifying the schema in the table prefix (both cluster members). For example, MYSCHEMA.FIRSTI_EJBTIMER_
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Persistent EJB Timers * **************************************************************** * PROBLEM DESCRIPTION: EJB Timer Service does not start on * * second cluster member due to lock * * timeout in DB2 on i. * **************************************************************** * RECOMMENDATION: * **************************************************************** WSVR0111W warning appears in logs indicating that EJB timer service cannot start on a cluster member. FFDC logs show a SQL Exception with SQL0601 indicating that a table cannot be created because it already exists. The cluster member is therefore unable to run persistent EJB timer tasks.
Problem conclusion
Updated code to identify the lock timeout error raised by DB2 on i, and to interpret it as meaning the table already exists rather than indicating the table still needs to be created. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.12 and 9.0.0.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
PI80294
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-20
Closed date
2017-05-11
Last modified date
2017-05-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
R850 PSY
UP
Document Information
Modified date:
03 May 2022