JMS/MDB JBoss 4.0.0 on mySQL

[jgoyvaer]

Hi !

As a newbie to JBoss I've downloaded and runned successfully the examples of the Getting Started with JBoss 4.0" booklet. Knowing I won't stick to HyperSQL, I'm trying to run the same examples on mySQL. I made the changes described in section 8.2. It all works well except for JMS/MDB. I've checked the forms first for a solution...

Changes I made for switching to mySQL:

1) Created the "jbossdb" database. (Which is listed as "jboss" in the booklet btw.)
2) Replaced the files related to hypersql in .../default/deploy by a modified example for mySQL and assign it DefaultDS.
3) Modified the file .../default/deploy/ejb-deployer.xml to have the TIMERS table created without SQL syntax errors. Replaced "others" by BLOB and "interval" by "intervals".
4) Replaced the hypersql reference by "mySql" in the file .../default/deploy/schedule-manager-service.xml
5) Set the mapping in .../default/conf/standardjaws.xml to "mySQL"
6) Set the mapping in .../default/conf/standardjbosscmp-jdbc.xml to "mySQL"
7) Copy the mysql-jdbc2-service.xml file into the .../deploy/jms directory and remove those of HyperSQL.
8) Remove all previously deployed applications of the previous examples.
9) Run JBoss default config with J2SE 1.4.2_06.

When Jboss starts for the first time it creates four tables:

jms_messages
jms_transactions
timers
hilosequences

Isn't it supposed to create more then those four tables ? Maybe something goes wrong in the process because I get on the console a lengthy list (see the complete underneath) ending with :

MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.mq:service=StateManager
state: NOTYETINSTALLED
I Depend On:
Depends On Me: jboss.mq:service=DestinationManager

I guess this means I'm forgetting something in the configuration of jboss messaging (i.e. "NOTYETINSTALLED"). I've tried to find an answer in the forums, but didn't succeed. Is there anybody who knows what I'm overlooking ?

When I deploy the application with the "deploy-mdb" target, I'm getting a at regular interval a stack trace (see complete underneath) ending with :

15:22:42,581 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound

I found the reference in the FAQ to this problem, made the change, but it didn't solve the problem. But maybe it's related to the previous problem.

Is there anybody who succeeded with this on JBoss 4.0.0 ? Or anybody who can give me a clue in which direction to look for the solution ?

Many thanks !!




C:\jboss-4.0.0\bin>SET JAVA_HOME=C:\j2sdk1.4.2_06
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\jboss-4.0.0\bin\\..
.
JAVA: C:\j2sdk1.4.2_06\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m
.
CLASSPATH: C:\j2sdk1.4.2_06\lib\tools.jar;C:\jboss-4.0.0\bin\\run.jar
.
===============================================================================
.
15:32:55,583 INFO [Server] Starting JBoss (MX MicroKernel)...
15:32:55,583 INFO [Server] Release ID: JBoss [Zion] 4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)
15:32:55,583 INFO [Server] Home Dir: C:\jboss-4.0.0
15:32:55,583 INFO [Server] Home URL: file:/C:/jboss-4.0.0/
15:32:55,583 INFO [Server] Library URL: file:/C:/jboss-4.0.0/lib/
15:32:55,593 INFO [Server] Patch URL: null
15:32:55,593 INFO [Server] Server Name: default
15:32:55,593 INFO [Server] Server Home Dir: C:\jboss-4.0.0\server\default
15:32:55,593 INFO [Server] Server Home URL: file:/C:/jboss-4.0.0/server/default/
15:32:55,593 INFO [Server] Server Data Dir: C:\jboss-4.0.0\server\default\data
15:32:55,593 INFO [Server] Server Temp Dir: C:\jboss-4.0.0\server\default\tmp
15:32:55,603 INFO [Server] Server Config URL: file:/C:/jboss-4.0.0/server/default/conf/
15:32:55,603 INFO [Server] Server Library URL: file:/C:/jboss-4.0.0/server/default/lib/
15:32:55,603 INFO [Server] Root Deployment Filename: jboss-service.xml
15:32:55,603 INFO [Server] Starting General Purpose Architecture (GPA)...
15:32:56,254 INFO [ServerInfo] Java version: 1.4.2_06,Sun Microsystems Inc.
15:32:56,254 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_06-b03,Sun Microsystems Inc.
15:32:56,254 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
15:32:56,844 INFO [Server] Core system initialized
15:32:59,618 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
15:33:21,290 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker
jboss.web:service=WebServer

Depends On Me:
ObjectName: jboss.mq.destination:name=testTopic,service=Topic
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me:
ObjectName: jboss.mq.destination:name=securedTopic,service=Topic
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me:
ObjectName: jboss.mq.destination:name=testDurableTopic,service=Topic
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me:
ObjectName: jboss.mq.destination:name=testQueue,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me:
ObjectName: jboss.mq.destination:name=A,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me:
ObjectName: jboss.mq.destination:name=B,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me:
ObjectName: jboss.mq.destination:name=C,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me:
ObjectName: jboss.mq.destination:name=D,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me:
ObjectName: jboss.mq.destination:name=ex,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me:
ObjectName: jboss.mq:service=Invoker
state: CONFIGURED
I Depend On: jboss.mq:service=TracingInterceptor

Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
jboss.mq:service=InvocationLayer,type=OIL
jboss.mq:service=InvocationLayer,type=OIL2
jboss.mq:service=InvocationLayer,type=RMI
jboss.mq:service=InvocationLayer,type=UIL2

ObjectName: jboss.mq:service=TracingInterceptor
state: CONFIGURED
I Depend On: jboss.mq:service=SecurityManager

Depends On Me: jboss.mq:service=Invoker

ObjectName: jboss.mq:service=SecurityManager
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: jboss.mq.destination:name=testTopic,service=Topic
jboss.mq.destination:name=securedTopic,service=Topic
jboss.mq.destination:name=testDurableTopic,service=Topic
jboss.mq.destination:name=testQueue,service=Queue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:name=DLQ,service=Queue

ObjectName: jboss.mq.destination:name=DLQ,service=Queue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me:
ObjectName: jboss.mq:service=InvocationLayer,type=JVM
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker

Depends On Me:
ObjectName: jboss.mq:service=DestinationManager
state: CONFIGURED
I Depend On: jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager

Depends On Me: jboss.mq.destination:name=testTopic,service=Topic
jboss.mq.destination:name=securedTopic,service=Topic
jboss.mq.destination:name=testDurableTopic,service=Topic
jboss.mq.destination:name=testQueue,service=Queue
jboss.mq.destination:name=A,service=Queue
jboss.mq.destination:name=B,service=Queue
jboss.mq.destination:name=C,service=Queue
jboss.mq.destination:name=D,service=Queue
jboss.mq.destination:name=ex,service=Queue
jboss.mq:service=SecurityManager
jboss.mq.destination:name=DLQ,service=Queue

ObjectName: jboss.mq:service=InvocationLayer,type=OIL
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker

Depends On Me:
ObjectName: jboss.mq:service=InvocationLayer,type=OIL2
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker

Depends On Me:
ObjectName: jboss.mq:service=InvocationLayer,type=RMI
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker

Depends On Me:
ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker

Depends On Me:

MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.mq:service=StateManager
state: NOTYETINSTALLED
I Depend On:
Depends On Me: jboss.mq:service=DestinationManager




15:22:42,581 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1272
)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:779)

[robisz]

You also have to modify default/deploy/jms/hsqldb-jdbc-state-service.xml
for your database. Probaby it's enough to change the name of datasource.

[jgoyvaer]

What do you know !? ;-)

It works ! I simply had to copy the file for hypersql since the SQL syntax is identical. New tables were created and the example works like a charm.

Speaking of a quick resolution of the problem.

Thanks a lot !!

[paul_zm]

It is probably easier and better to look for a suitable database file in the doc directory of the jboss install.

[joff]

There is no MySQL specific mysql-jdbc-state-service.xml in the examples, this is probably what led to the confusion...