org.jboss.deployment.DeploymentException: ManagedConnectionF

[fengbin98]

org.jboss.deployment.DeploymentException: ManagedConnectionFactory not set!

Anyone has some idea about how and why the exception happens?

[jaikiran]

Which version of JBoss and Java? When does this exception occur? And post the entire exception stacktrace.

[fengbin98]

Jboss 4.2.2GA
Jave: SDK 1.5

It seems to me that the problem is the application fails to get a database connection handle from the jboss server. But I am not sure whether it is caused by the fact that Jboss server is not running or the fact that the server config is wrong. Please help.

1112 [main] DEBUG org.jboss.util.NestedThrowable - org.jboss.util.NestedThrowable.parentTraceEnabled=true
1112 [main] DEBUG org.jboss.util.NestedThrowable - org.jboss.util.NestedThrowable.nestedTraceEnabled=false
1112 [main] DEBUG org.jboss.util.NestedThrowable - org.jboss.util.NestedThrowable.detectDuplicateNesting=true
1112 [main] ERROR com.wire.db.DataUtil - Exception caught in setupDataSource(): org.jboss.deployment.DeploymentException: ManagedConnectionFactory not set!
1134 [main] ERROR com.wire.db.DataException - Exception thrown while initializing DataSource
org.jboss.deployment.DeploymentException: ManagedConnectionFactory not set!
at org.jboss.resource.connectionmanager.ManagedConnectionPool.startService(ManagedConnectionPool.java:291)
at com.wire.db.ManagedConnectionPoolProxy.doStartService(DataUtil.java:718)
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:358)
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:241)
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:140)
at com.wire.db.DbConnUtil.getContext(DbConnUtil.java:109)
at com.wire.db.DbConnUtil.getConnection(DbConnUtil.java:40)
at com.wire.db.DbConn.getConnection(DbConn.java:180)
9563 [main] ERROR com.wire.db.DbConn - com.wire.db.DbConn::getConnection: Failed to get a connection.
com.wire.db.DataException: Exception thrown while initializing DataSource
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:474)
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:241)
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:140)
at com.wire.db.DbConnUtil.getContext(DbConnUtil.java:109)
at com.wire.db.DbConnUtil.getConnection(DbConnUtil.java:40)
at com.wire.db.DbConn.getConnection(DbConn.java:180)
Caused by: org.jboss.deployment.DeploymentException: ManagedConnectionFactory not set!
at org.jboss.resource.connectionmanager.ManagedConnectionPool.startService(ManagedConnectionPool.java:291)
at com.wire.db.ManagedConnectionPoolProxy.doStartService(DataUtil.java:718)
at com.wire.db.DataUtil.setupDataSource(DataUtil.java:358)

[jaikiran]

at org.jboss.resource.connectionmanager.ManagedConnectionPool.startService(ManagedConnectionPool.java:291)
at com.wire.db.ManagedConnectionPoolProxy.doStartService(DataUtil.java:718)

What is the doStartService in ManagedConnectionPoolProxy (which is not a JBoss class) trying to do? Can you post the code?

[fengbin98]

All it does is call the StartService() in org.jboss.resource.connectionmanager.JBossManagedConnectionPool.

[jaikiran]

I am sorry, but i am not understanding why you are calling the startService method on the JBossManagedConnectionPool. Are you trying to lookup a datasource?

[gcameo]

I have the same error somewhere in my logs on upgrading jbosss from 3.0.4 to 3.2.8-SPI

org.jboss.deployment.DeploymentException: Error: can't find data source: java:/LalPacDS; - nested throwable: (javax.naming.NameNotFoundException: LalPacDS not bound)

You can see a full list of the exception in the post "Upgrading jboss"

[fengbin98]

yes, this is datasource related.

[jaikiran]

If you are trying to lookup a datasource then you should first deploy it and then use JNDI to lookup the datasource. See these for details:


http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources

http://wiki.jboss.org/wiki/Wiki.jsp?page=DSdotXML

You can also find sample datasource files under %JBOSS_HOME%/docs/examples/jca folder.

[gcameo]

Thank you very much for the direction

I'm rewriting the existing *-service.xml used in the jboss-3.0.8 to *-ds.xml

in the service.xml, there is an mbean declaration like this

<mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=LalPacDS">

 <depends optional-attribute-name="ManagedConnectionFactoryName">

Do i have to include this declaration in the *-ds.xml