Cann't invoke a service after changing the db for JBoss Messaging

[ingedeut]

Hello,

i have tried to change the db of JBossMessaging from Hsqldb to Mysql. When trying to invoke a simple esb service the following error is occured. For the change was the invocation successfully.

16:20:03,068 ERROR [ChannelSupport] Failed to handle message
java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.put(Unknown Source)
at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(
JDBCPersistenceManager.java:1632) at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(
JDBCPersistenceManager.java:1358) at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(
JDBCSupport.java:474) at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(
JDBCSupport.java:512) at org.jboss.messaging.core.impl.JDBCPersistenceManager.addReference(
JDBCPersistenceManager.java:1396) at org.jboss.messaging.core.impl.ChannelSupport.handle(
ChannelSupport.java:226) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(
MessagingPostOffice.java:2208) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(
MessagingPostOffice.java:494) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(
ServerConnectionEndpoint.java:755) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(
ServerSessionEndpoint.java:391) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(
SessionAdvised.java:87) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.container.SecurityAspect.handleSend(
SecurityAspect.java:157) at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(
PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(
SessionSendRequest.java:95) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(
JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(
ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(
ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(
ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(
ServerThread.java:173) 16:20:03,072 ERROR [ExceptionUtil] SessionEndpoint[o2-f1izu6fg-1-agmru6fg-rsaaxt-194o4c5] send [p2-oiizu6fg-1-agmru6fg-rsaaxt-194o4c5]
javax.jms.JMSException

: Failed to route Reference[21084458233511968]:RELIABLE to org_pi4soa_fcdchain_fcdchain_FcdChainProcess_DataImporterParticipant at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(
ServerConnectionEndpoint.java:757) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(
ServerSessionEndpoint.java:391) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(
SessionAdvised.java:87) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.container.SecurityAspect.handleSend(
SecurityAspect.java:157) at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(
PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(
SessionSendRequest.java:95) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(
JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(
ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(
ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(
ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(
ServerThread.java:173) 16:20:03,431 ERROR [ChannelSupport] Failed to handle message
java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.put(Unknown Source)
at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(
JDBCPersistenceManager.java:1632) at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(
JDBCPersistenceManager.java:1358) at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(
JDBCSupport.java:474) at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(
JDBCSupport.java:512) at org.jboss.messaging.core.impl.JDBCPersistenceManager.addReference(
JDBCPersistenceManager.java:1396) at org.jboss.messaging.core.impl.ChannelSupport.handle(
ChannelSupport.java:226) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(
MessagingPostOffice.java:2208) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(
MessagingPostOffice.java:494) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(
ServerConnectionEndpoint.java:755) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(
ServerSessionEndpoint.java:391) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(
SessionAdvised.java:87) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.container.SecurityAspect.handleSend(
SecurityAspect.java:157) at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(
PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(
SessionSendRequest.java:95) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(
JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(
ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(
ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(
ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(
ServerThread.java:173) 16:20:03,432 ERROR [ExceptionUtil] SessionEndpoint[o2-f1izu6fg-1-agmru6fg-rsaaxt-194o4c5] send [q2-osizu6fg-1-agmru6fg-rsaaxt-194o4c5]
javax.jms.JMSException

: Failed to route Reference[21084458239311905]:RELIABLE to org_pi4soa_fcdchain_fcdchain_FcdChainProcess_DataImporterParticipant at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(
ServerConnectionEndpoint.java:757) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(
ServerSessionEndpoint.java:391) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(
SessionAdvised.java:87) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.container.SecurityAspect.handleSend(
SecurityAspect.java:157) at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(
PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(
SessionSendRequest.java:95) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(
JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(
ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(
ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(
ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(
ServerThread.java:173)

any help please?

--Regards

Younes

[tcunning]

Younes,

Did you use the schema tool that Martin suggested in the previous thread to change the database?     If you did, try the helloworld quickstart - does that work?

[ingedeut]

Thanks Tom,

i have changed the db using the schema tool and it runs right with the helloworl quickstart. But some issues are presented:

• The schema tools change all the databse for JBoss ESB (juddi, jbossmessaging, jbpm, managemnet db and message store db) and put all tabe in the same db (e.g soaesb1_as). When trying to change only the db of juddi and jbossmessaging a problem is occured by server startup. I think there are dependencies between all db so that all db must be in one db merged or all db muss be running in the same VM (like ny hsqldb). Any suggestions please?
  
• I have tried to build a cluster of JBoss esb between two nodes in the same network. I have deployed the quickstart_hello_world in node 1 and node 2. and i make the two server nodes using a shared db for all databases. Also i have set the attribute clustered als true for the quick_start_hello_world_queue_gw. The clustered attribute of post-office is also set to true. when undeploying the quickstart_hello_worl service from node1 , thisone in node2 don't react. I guess that the a jgroups-comfiguration is wrong or the jndi-configuration. Any suggestions please?
  

--Regards

Younes

[tcunning]

The schema tools change all the databse for JBoss ESB (juddi,  jbossmessaging, jbpm, managemnet db and message store db) and put all  tabe in the same db (e.g soaesb1_as). When trying to change only the db  of juddi and jbossmessaging a problem is occured by server startup. I  think there are dependencies between all db so that all db must be in  one db merged or all db muss be running in the same VM (like ny hsqldb).  Any suggestions please?

My guess is that you missed a required configuration file, but I don't have any idea which one.      There isn't any requirement that all the databases must be in the same instance.      You could use the schema tool and work backwards to figure out which one you missed, or you could just use the schema tool which has been fully tested.

I have tried to build a cluster of JBoss esb between two nodes in the  same network. I have deployed the quickstart_hello_world in node 1 and  node 2. and i make the two server nodes using a shared db for all  databases. Also i have set the attribute clustered als true for the quick_start_hello_world_queue_gw. The clustered attribute of  post-office is also set to true. when undeploying the  quickstart_hello_worl service from node1 , thisone in node2 don't react.  I guess that the a jgroups-comfiguration is wrong or the  jndi-configuration. Any suggestions please?

How to cluster JMS is a better question for the JBoss Messaging forum :

http://community.jboss.org/en/jbossmessaging?view=discussions