IBM Support

PM63933: JAVA.SQL.SQLEXCEPTION, CANNOT DISABLE THE DEFAULT EJB TIMER DATABASE DERBY

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Running WebSphere Application Server BASE 7.0.0.7, not needing
    to use the default EJB Timer database which is Derby, trying to
    disable the EJB Timer Service by setting the "Number of timer
    threads" under "Application servers > server1 > EJB timer
    service settings" to 0, but this does not work and SystemErr.log
    showing exception:
    
    Thread[server.startup : 0,5,main] java.io.FileNotFoundException:
    /opt/ibm/was70/WebSphere/AppServer/derby/derby.log (Permission
    denied)
    
    Thread[server.startup : 0,5,main] Cleanup action starting
    java.sql.SQLException: Database
    '/opt/WASprofiles/myProfile/databases/EJBTimers/server1/EJBTimer
    DB' not found.
     at
    org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
    (UnknownSource)
     at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
    Source)
     at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
    Source)
     ...
    
    Caused by: java.sql.SQLException: Database
    '/opt/WASprofiles/myProfile/databases/EJBTimers/server1/EJBTimer
    DB' not found.
     at
    org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(U
    nknown Source)
     at
    org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTran
    sportAcrossDRDA(Unknown Source)
     ... 31 more
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server that would like to disable the EJB   *
    *                  Timer Service.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Setting the number of timer threads     *
    *                      to zero does not completely disable     *
    *                      the EJB Timer Service.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When attempting to disable the EJB Timer Service by setting the
    "Number of timer threads" under "Application servers > server1
    > EJB timer service settings" to 0, the timer service is not
    fully disabled and the following error is seen:
    java.io.FileNotFoundException:
    /opt/ibm/was70/WebSphere/AppServer/derby/derby.log (Permission
    denied)
    Caused by: java.sql.SQLException: Database
    '/opt/WASprofiles/myProfile/databases/EJBTimers/server1/EJBTimer
    DB' not found.
    

Problem conclusion

  • When the EJB Timer Service is disabled, the applicaiton server
    should not attempt to access the default EJB Timer database.
    This problem will be corrected by not accessing the database
    when the timer service is disabled.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.45, 7.0.0.25, 8.0.0.4, 8.5.0.1.  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

    PM63933

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-04

  • Closed date

    2012-05-17

  • Last modified date

    2012-05-17

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM63933

Modified date: 17 May 2012