[help] jboss connected to mysql: where is the mistake?

[igorkey]

Hi everybody.
I'm trying to connect jboss 3.2.5 with a dBase under mysql (Ver 14.7 Distrib 4.1.14). I'm using gentoo, but I don't think this changes something....

I've configured these xml files:

/usr/share/jboss/server/default/mysql-ds.xml /usr/share/jboss/server/default/jms/mysql-jdbc-state-service.xml
/usr/share/jboss/server/default/jms/mysql-jdbc2-service.xml

I've moved away the configuration files for hypersonic, I've copied the mysql-connector-java in the default/lib directory.... I think I've done everything requested to make the stuff work, but after starting jboss, in the /var/log/jboss/server.log file i find the error message:

2005-12-01 09:54:12,818 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:

[...]

MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.jca:service=DataSourceBinding,name=mySQL
state: NOTYETINSTALLED
I Depend On:
Depends On Me: jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager

What do I miss?

Searching on the net i've found no clue, could anyone give me one?

thanks in advance

[igorkey]

Hi, again...
This morning I've tried the version available on this site, instead of the emerged one under gentoo... this one seems working, with the same steps followed for the configuration!

with the latest available version now I can connect to the mysql database (some tables have been created, infact), but when I start jboss I get this new error, complaining about the "DestinationManager":


[...]
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=DestinationManager
State: NOTYETINSTALLED
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq.destination:service=Queue,name=A
jboss.mq.destination:service=Queue,name=B
jboss.mq.destination:service=Queue,name=C
jboss.mq.destination:service=Queue,name=D
jboss.mq.destination:service=Queue,name=ex
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ

[...]

again, if anyone has some hints....


thanks!
bye

[igorkey]

Finally, I've managed to get a clear jboss startup: it was just a configuration issue in one xml (deploy/jms//mysql-jdbc2-service.xml)....

Let's go write some ejb! :)

bye