views:

41

answers:

0

Trying to get my webapp to deploy to glassfish v3 and I am getting an odd error. If I startup the container, and ping the TimerPool through the Admin Interface, all is fine. If I deploy either from Netbeans directly, or through the admin interface before I ping the timerPool, I get the following error:

Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.1.v20100213-r6600): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause:       Connection could not be allocated because: Failed to start database '/home/dpb/opt/glassfish/v3/glassfish/domains/domain1/lib/databases/ejbtimer', see the next exception for details.
Error Code: 0
    at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:309)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:138)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94)
    at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:584)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:228)
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:369)
    ... 65 more
Caused by: java.sql.SQLException: Error in allocating a connection. Cause: Connection     could not be allocated because: Failed to start database '/home/dpb/opt/glassfish/v3/glassfish/domains/domain1/lib/databases/ejbtimer', see the next   exception for details.
    at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:112)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:126)
    ... 70 more

Of course there are about 30 other similar stack traces, and contrary to the message, none of them contains a more verbose message.

What could be going on here?

I also occasionally get the following error under similar circumstances. I haven't yet narrowed down when this one comes up.

WARNING: RAR8054: Exception while creating an unpooled [test] connection for pool [ __TimerPool ], WEB9031: WebappClassLoader unable to load resource [org/apache/derby/info/DBMS.properties], because it has not yet been started, or was already stopped