Hot deploy of ds.xml files generates errors
anshah1 Mar 10, 2006 2:16 PMHi,
I am using JBOSS 4.0.3SP1 with Java 1.5.2. I have noticed an issue when it comes to changing *ds.xml files present in the deploy directory.
I get this error.
10:57:39,588 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=KEGGDS,service=DataSourceBinding' from JNDI name 'java:KEGGDS'
10:57:39,603 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=IPDS,service=DataSourceBinding' from JNDI name 'java:IPDS'
10:57:39,603 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=BRMDS,service=DataSourceBinding' from JNDI name 'java:BRMDS'
10:57:40,650 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=BRMDS,service=DataSourceBinding' to JNDI name 'java:BRMDS'
10:57:40,650 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=IPDS,service=DataSourceBinding' to JNDI name 'java:IPDS'
10:57:40,650 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=KEGGDS,service=DataSourceBinding' to JNDI name 'java:KEGGDS'
10:59:06,702 ERROR [UserBean#findByName] Find failed
org.jboss.util.NestedSQLException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:79)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:210)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:128)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:47)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:589)
at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:300)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:236)
at org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1086)
at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:663)
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.invocation.Invocation.performCall(Invocation.java:345)
at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1113)
at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:189)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:180)
at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
It seems like it unbinds the JNDI name and rebinds it just fine, however the next time I try to connect, it throws the above error.
Any suggestions?
Thanks,
Anuj