ConnectionFactoryLoader not in the CVS any more
Since the ConnectionFactoryLoader was removed from CVS, I am not able to get my Datasources running again. Before the update everything was running fine. Now I get the following messages:
18:57:02,233 INFO [CounterService] Started
18:57:02,233 INFO [MainDeployer] Successfully completed deployment of package: file:/C:/Programme/jboss-3.0.0/server/default/deploy/counter
-service.xml
18:57:02,233 INFO [MainDeployer] Starting deployment of package: file:/C:/Programme/jboss-3.0.0/server/default/deploy/scheduler-service.xml
18:57:02,249 INFO [MainDeployer] Successfully completed deployment of package: file:/C:/Programme/jboss-3.0.0/server/default/deploy/schedul
er-service.xml
18:57:02,249 INFO [MainDeployer] Starting deployment of package: file:/C:/Programme/jboss-3.0.0/server/default/deploy/jms-service.xml
18:57:03,077 INFO [JMSProviderLoader] Creating
[...]
18:57:12,108 ERROR [EntityContainer] Exception in service lifecyle operation: create
org.jboss.deployment.DeploymentException: Error: can't find data source: java:/msSQL; - nested throwable is: javax.naming.NameNotFoundEx
ception: msSQL not bound
javax.naming.NameNotFoundException: msSQL not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:365)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:349)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntityBridge.java:96)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:291)
at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:138)
at org.jboss.ejb.EntityContainer.create
[...]
(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:278)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:672)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:517)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:480)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:462)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:213)
at org.jboss.Main.boot(Main.java:138)
at org.jboss.Main$1.run(Main.java:371)
at java.lang.Thread.run(Thread.java:484)
org.jboss.deployment.DeploymentException: Error: can't find data source: java:/msSQLPrak; - nested throwable is: javax.naming.NameNotFoundEx
ception: msSQL not bound
I'm using the ms-sql-service.xml available at http://www.jboss.org/online-manual/HTML/ch03s12.html.
Has anybody the same problems? Or has anybody an idea to get the service running again?
