glassfish
  1. glassfish
  2. GLASSFISH-20121

Lookup failed for JNDI name: jdbc/__TimerPool for standalone instances/cluster

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b82_EE7MS7
    • Fix Version/s: 4.0_b84_RC1
    • Component/s: batch
    • Labels:
      None

      Description

      Tested with latest nightly.

      1) Deploy sample batch applications in standalone instances/clusters and try to access the app.

      Issue -->
      [2013-04-01T19:25:52.859+0530] [glassfish 4.0] [SEVERE] [] [com.ibm.jbatch.container.services.impl.JDBCPersistenceManagerImpl] [tid: _ThreadID=30 _ThreadName=http-listener-1(4)] [timeMillis: 1364824552859] [levelValue: 1000] [[
      Lookup failed for JNDI name: jdbc/__TimerPool. One cause of this could be that the batch runtime is incorrectly configured to EE mode when it should be in SE mode.]]

        Activity

        Hide
        Mahesh Kannan added a comment -

        Changed the default to jdbc/__default. Note that you need to start derby before running batch apps. This is exactly what needs to be done to run ejb timer apps

        Show
        Mahesh Kannan added a comment - Changed the default to jdbc/__default. Note that you need to start derby before running batch apps. This is exactly what needs to be done to run ejb timer apps

          People

          • Assignee:
            Mahesh Kannan
            Reporter:
            arunkumar_s
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: