Error After Updating JMS table names

[tregulski]

Hello,

We have a requirement to make sure the JMS tables used by JBoss are placed in a specific schema on SQL Server 2005. When we update the mssq-jdbc2-service.xml file, a sample of it looks like the following:

BLOB_TYPE=BINARYSTREAM_BLOB
INSERT_TX = INSERT INTO XYZ.JMS_TRANSACTIONS (TXID) VALUES (?)

Every table name has been prefixed with the schema name XYZ. The hsqldb-jdbc-state-service has also been updated with the schema names.

The tables themselves appear to be created just fine, with the correct schema name being used. The problem occurs when we try to use the queue. When we try to save content to the queue, we get the enclosed error message below.

When we don't use the schema name prefix and just go with the default, everything appears to work just fine. It's just when we try adding a schema name that we get error messages.

TIA,
Tim


2008-09-18 14:45:08,256 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for ConsumerMDB
javax.naming.NameNotFoundException: XAConnectionFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:182)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428)
at java.lang.Thread.run(Unknown Source)


2008-09-18 14:47:19,995 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for SumEnrollmentStoreMDB
javax.naming.NameNotFoundException: XAConnectionFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:182)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428)
at java.lang.Thread.run(Unknown Source)

[clebert.suconic]

It probably means something else didn't start correctly. You should look for more errors at your logs.

We have a requirement to make sure the JMS tables used by JBoss are placed in a specific schema on SQL Server 2005.

If you change our schema by your own schema, you're responsible for maintaining it :-).

Make sure you test it. I would probably download the source code from SVN and run the testsuite with your schema. Or make sure you test it well.


And BTW I'm not sure if you should change the schema. That DB is like a repository for JBossMessaging, you shouldn't even mess with those tables. (Lots of blobs, trying to get most of the performance), so I'm not sure why your DBA is picking up on that. (BTW: on JBM2 the default config won't even use a Database.)

[tregulski]

Thanks for the tip. Will review the logs some more and get back to you.

I'm with you on not changing the table names or definitions. Some our our clients have "strict" requirements on where tables are created (arggh).

[tim.shaw]

Can you not just modify the datasource to put the tables elsewhere? I just change defaultDS to point to a tidy spot (seperate MySQL database)
Not sure about SQL Server.