3.2.0 and 3.2.1 shutdown problems
jk.mkiii May 8, 2003 3:24 AMHi,
Background. We have made repository style system that connects to other parts of framework through webservices, or actually mostly others connect. So we have EJBs and permanent storage is done in HSQLDB.
Everything worked correctly in 3.2.0RC3.
Then switched to 3.2.0 and everything still worked correctly, except when shutdown server. When system was closing datasource used to store data I get following exception (actually this is from 3.2.1 but I think it was identical, at least top of it was)
2003-05-08 11:18:24,152 DEBUG [org.jboss.system.ServiceController] stopping service: jboss.jca:service=LocalTxCM,name=Data
2003-05-08 11:18:24,152 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Stopping
2003-05-08 11:18:24,182 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-05-08 11:18:24,182 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-05-08 11:18:24,182 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-05-08 11:18:24,172 INFO [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Exception destroying ManagedConnection
org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLException: The database is shutdown in statement [DISCONNECT])
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:445)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:229)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.doDestroy(InternalManagedConnectionPool.java:374)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.flush(InternalManagedConnectionPool.java:272)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.shutdown(InternalManagedConnectionPool.java:307)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool.shutdown(JBossManagedConnectionPool.java:670)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool.stopService(JBossManagedConnectionPool.java:373)
at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:236)
at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
at $Proxy11.stop(Unknown Source)
at org.jboss.system.ServiceController.stop(ServiceController.java:464)
at org.jboss.system.ServiceController.stop(ServiceController.java:456)
at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.stop(Unknown Source)
at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:373)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:177)
at $Proxy16.stop(Unknown Source)
at org.jboss.deployment.XSLSubDeployer.stop(XSLSubDeployer.java:236)
at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:497)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:480)
at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:368)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:808)
at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:783)
at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:771)
Caused by: java.sql.SQLException: The database is shutdown in statement [DISCONNECT]
at org.hsqldb.Trace.getError(Unknown Source)
at org.hsqldb.Result.(Unknown Source)
at org.hsqldb.jdbcConnection.executeHSQL(Unknown Source)
at org.hsqldb.jdbcConnection.execute(Unknown Source)
at org.hsqldb.jdbcConnection.close(Unknown Source)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:225)
... 44 more
2003-05-08 11:18:24,182 INFO [STDOUT] Thu May 08 11:18:24 EEST 2003 SHUTDOWN : System.exit() was not called
Then when noticed this I thought I would try 3.2.1 if this had been fixed in it. Result, same error plus one new.
New error in 3.2.1 shutdown was that when destroying StatelessSessionInstancePool JBoss tries to delete some beans that have already been undeployed (complaining that env not bound etc.)
Anyone had similiar experiences or otherwise know what might be wrong and what I could do to fix them ..besides sticking with 3.2.0RC3 version and informing other people who might want to run our system.