2 Replies Latest reply on Sep 15, 2006 5:46 PM by Weston M. Price

    EJB3StandaloneBootstrap.shutdown() method hanging

    Andrig Miller Apprentice

      Has anyone seen this behavior when calling the shutdown method on EJB3StandaloneBootstrap?

      INFO 14-03 14:17:18,643 (SessionFactoryImpl.java:close:728) -closing
      WARN 14-03 14:19:41,073 (InternalManagedConnectionPool.java:fillToMin:496) -Unable to fill pool
      org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: No Driver class specified!)
       at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:177)
       at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:539)
       at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.fillToMin(InternalManagedConnectionPool.java:486)
       at org.jboss.resource.connectionmanager.PoolFiller.run(PoolFiller.java:74)
       at java.lang.Thread.run(Thread.java:788)
      Caused by:
      org.jboss.resource.JBossResourceException: No Driver class specified!
       at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getDriver(LocalManagedConnectionFactory.java:243)
       at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:168)
       ... 4 more

      I get this on a little embedded application that I am building that pulls data from Jira via SOAP, and persists it in a MySQL database. The application actually runs fine, and completes without any errors, but the shutdown hangs for a little bit, then spews the above, and then just stays hung forever (I hit Control-C to end it).

      I have not been able to reproduce this yet, and the same EJB's that I am using in the embedded application here, work just fine in all my JUnit tests in Eclipse. In fact, I am using the same configuration files between my unit tests and the actual run of the application.

      Any ideas?