-
1. Re: datasource error. The DS loads after the entity beans
mkprim Oct 9, 2003 12:20 PM (in response to mkprim)I forgot to say i'm using JBoss 3.0.8 in the 'all' server and MySQL 3.23.54
-
2. Re: datasource error. The DS loads after the entity beans
chuckharris Oct 9, 2003 12:31 PM (in response to mkprim)Try adding a to your xml descriptor.
jboss.jca:service=LocalTxCM,name= DefaultDS
jboss.jca:service=ManagedConnectionFactory,name= DefaultDS
jboss.jca:service=ManagedConnectionPool,name= DefaultDS
This works for 3.2.2. -
3. Re: datasource error. The DS loads after the entity beans
mkprim Oct 9, 2003 12:41 PM (in response to mkprim)You mean adding it in the mysql-service.xml?
-
4. Re: datasource error. The DS loads after the entity beans
chuckharris Oct 9, 2003 12:45 PM (in response to mkprim)No for the bean.
-
5. Re: datasource error. The DS loads after the entity beans
mkprim Oct 9, 2003 12:47 PM (in response to mkprim)How can I do that? And where???
-
6. Re: datasource error. The DS loads after the entity beans
chuckharris Oct 9, 2003 1:05 PM (in response to mkprim)My thought is that your problem is similar to one i just had: http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=
-
7. Re: datasource error. The DS loads after the entity beans
mkprim Oct 9, 2003 1:33 PM (in response to mkprim)OK, I See... but my drivers load well.
I was asking if you know where is the ejb-development service descriptor so i can add the depends in that place.
Thank you for the help. -
8. Re: datasource error. The DS loads after the entity beans
frito Oct 10, 2003 1:53 AM (in response to mkprim)There is something wrong with your deplyoment. This is the order of the deployment sorter:
"sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip", "*" .
Your datasource must be deployed before your beans by default.
Greetings,
Frito -
9. Re: datasource error. The DS loads after the entity beans
mkprim Oct 10, 2003 10:17 AM (in response to mkprim)OK, I tried this:
1) I used the 'default' configuration and it worked.
2) I tried the same in the 'all' configuration, and the problem kept on.
The deploy order seems to be correct.
I must say that I don't deploy de mysql datasource in a sar. I just put the mysql-service.xml in the deploy dir, the jar in the lib dir, and configured (changed the defaults) in the standard*.xml in the conf dir. (This might help a bit to find out the cause)
Thanks Frito. -
10. Re: datasource error. The DS loads after the entity beans
mkprim Oct 10, 2003 10:29 AM (in response to mkprim)I've just fixed the problem, mixing the solutions from both of you.
I just opened the config/jboss-service.xml and then I added the line in bold
<!-- EJB deployer, remove to disable EJB behavior-->
true
false
false
true
<!-- Add a dependency on the JMS provider(jms-service.xml) for MDBs. If
you are not using MDBs and JMS remove these.
-->
sdadas jboss.mq:service=JMSProviderLoader,name=JBossMQProvider
jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool
jboss.jca:service=LocalTxCM,name=MySqlDS -
11. OK, it's my turn now
huskerchen Oct 10, 2003 2:47 PM (in response to mkprim)I am using JBoss to connect SQLServer datasource. I manually deploy the SQLServer-ds.xml into the deployment folder and jboss responds:
[SQLServerDS]Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=LocalTxCM,name=SQLServerDS to JNDI name 'java:/SQLServerDS'
Then I deploy the CMP, JBOSS responds:
org.jboss.deployment.DeploymentException: Error: can't find data source: SQLServerDS; - nested throwable: (javax.naming.NameNotFoundException: SQLServerDS not bound)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:125)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:443)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:371)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:152)
at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:343)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
.....
I add the in jboss-service.xml and tried to re-deploy everything again in the above order, the problem is still there.
Any ideas?
Thanks! -
12. Re: OK, it's my turn now
mkprim Oct 15, 2003 9:15 AM (in response to mkprim)Did you add the mysqlserver-service.xml in the deploy dir?
Also, have you modified the standardjbosscmp-....xml and the standardjaws.xml adding your database?