How do you get your application to deploy after the datasource has been bound in JBoss 4.2? -



How do you get your application to deploy after the datasource has been bound in JBoss 4.2? -

i have jboss 4.2 appserver running, mysql-ds.xml defined. have set of custom jars want deployed mbean, utilize bounded mysql connection java:/mysqlds.

however, seems jars loaded before datasource bounded.

is there way ensure mbean loaded after datasource bounded?

here log entries:

11:39:29,639 fatal [datasourceconnectionprovider] not find datasource: java:/mysqlds javax.naming.namenotfoundexception: mysqlds not bound @ org.jnp.server.namingserver.getbinding(namingserver.java:529) @ org.jnp.server.namingserver.getbinding(namingserver.java:537) @ org.jnp.server.namingserver.getobject(namingserver.java:543) ... 11:39:29,666 error [hibernateutil] building sessionfactory failed. org.hibernate.hibernateexception: not find datasource @ org.hibernate.connection.datasourceconnectionprovider.configure(datasourceconnectionprovider.java:56) @ org.hibernate.connection.connectionproviderfactory.newconnectionprovider(connectionproviderfactory.java:124) @ org.hibernate.connection.connectionproviderfactory.newconnectionprovider(connectionproviderfactory.java:56) ... caused by: javax.naming.namenotfoundexception: mysqlds not bound @ org.jnp.server.namingserver.getbinding(namingserver.java:529) @ org.jnp.server.namingserver.getbinding(namingserver.java:537) @ org.jnp.server.namingserver.getobject(namingserver.java:543) @ org.jnp.server.namingserver.lookup(namingserver.java:296) @ org.jnp.interfaces.namingcontext.lookup(namingcontext.java:667) @ org.jnp.interfaces.namingcontext.lookup(namingcontext.java:627) @ javax.naming.initialcontext.lookup(initialcontext.java:411) @ org.hibernate.connection.datasourceconnectionprovider.configure(datasourceconnectionprovider.java:52) ... 106 more

then later on:

11:39:30,524 info [connectionfactorybindingservice] bound connectionmanager 'jboss.jca:service=datasourcebinding,name=mysqlds' jndi name 'java:/mysqlds'

ok had add together depends statement in mbean declaration:

<depends>jboss.jca:service=datasourcebinding,name=mysqlds</depends>

jboss datasource managed-bean

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -