[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=all ] Naveen Malik updated JBMESSAGING-1381: -------------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137845 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Naveen Malik commented on JBMESSAGING-1381: ------------------------------------------- Setup: 1. Install JBossAS 2. Deploy a MessagingDS pointing to the MySQL server. Database can be empty, JBM will create tables on startup. 3. Delete deploy/jboss-messaging.sar/clustered-hsqldb-persistence-service.xml 3. Copy the mysql-persistence-service.xml from the JBM release to deploy/jboss-messaging.sar 4. Edit persistence service to use MessagingDS. 5. Edit conf/login-config.xml to use MessagingDS for messaging. 6. Deploy mysql-connector-java-5.0.7-bin.jar in server lib. Attaching configuration files used. This happens when sending a message to the queue only. Startup occurs successfully. I can successfully send a message to a queue if I do not change the setup to use MySQL for message persistence. That is, do a base install of JBoss AS and it works out of the box with hsqldb and I can send a message to queue/testQueue. I did not use the process in the user guide to test this. SVN info for where I got the mysql-persistence-service.xml file: URL: http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_SP3_CP02 Repository Root: http://anonsvn.jboss.org/repos/messaging Repository UUID: b6fe21fe-e719-0410-baf4-a14e395396c4 Revision: 4519 Node Kind: directory Schedule: normal Last Changed Author: timfox Last Changed Rev: 4012 Last Changed Date: 2008-04-04 12:10:19 -0400 (Fri, 04 Apr 2008) Exception seen: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:846) at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(JDBCPersistenceManager.java: 1632) at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JD BCPersistenceManager.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(MessagingPostO ffice.java:2208) at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.ja va:494) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoi nt.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$advise d$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.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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(JMSServerInvocationHandle r.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:572) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) 2008-06-20 11:01:10,092 ERROR [org.jboss.messaging.util.ExceptionUtil] SessionEndpoint[i-8yetwohf-1- 6k8swohf-c909sv-z1a6ba] send [j-0fftwohf-1-6k8swohf-c909sv-z1a6ba] javax.jms.JMSException: Failed to route Reference[19889751164256256]:RELIABLE to testQueue at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoi nt.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$advise d$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.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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(JMSServerInvocationHandle r.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:572) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=all ] Naveen Malik updated JBMESSAGING-1381: -------------------------------------- Attachment: login-config.xml File used when mysql persistence for JBM doesn't work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Tim Fox commented on JBMESSAGING-1381: -------------------------------------- I'm confused about what version of eap you're using. Eap 4.3.0.GA cp01 already contains jbm 1.4.0.sp3_cp02 and all the config files, so no install necessary. Not sure why you're getting them from svn. Any other config is not supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Tim Fox commented on JBMESSAGING-1381: -------------------------------------- When you say jbossas, you mean eap right? (these days jbossas normally refers to the community edition). mysql-persistence-service.xml should be in the eap distro in the directory docs/examples/jms - no need to get it from svn. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Naveen Malik commented on JBMESSAGING-1381: ------------------------------------------- Yes, that is the upgrade path, EAP 4.3.0.GA to EAP 4.3.0.CP01. All tables in the messaging database were dropped. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Tim Fox commented on JBMESSAGING-1381: -------------------------------------- Naveen- Any update on this? Are you still having problems? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Clebert Suconic commented on JBMESSAGING-1381: ---------------------------------------------- The correct procedure to enable MySQL persistence on EAP should be: 1. Install JBossAS 2. Deploy a MessagingDS pointing to the MySQL server. Database can be empty, JBM will create tables on startup. 3. Delete deploy/jboss-messaging.sar/clustered-hsqldb-persistence-service.xml 3. Copy the mysql-persistence-service.xml from the /examples/jms (******..... not from the release ******) 4. Edit persistence service to use MessagingDS. 5. Edit conf/login-config.xml to use MessagingDS for messaging. 6. Deploy mysql-connector-java-5.0.7-bin.jar in server lib. I'm validating the procedure now, but I won't validate the install from the Release. It should be the same but i can't guarantee you would get the right version of the XML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ] Naveen Malik commented on JBMESSAGING-1381: ------------------------------------------- The mysql-persistence-service.xml in the release is identical to the file installed in docs/examples/jms. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=all ] Clebert Suconic closed JBMESSAGING-1381. ---------------------------------------- Resolution: Rejected This is certainly not a bug. I reproduced the entire install procedure and I never got the exception. Besides if this was an error, every JBM user would have been reporting this, as this is such a basic use case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1381?page=com.atlassian.ji... ] Naveen Malik commented on JBMESSAGING-1381: ------------------------------------------- Sorry for not stating earlier that I was using an RPM. The full filename for the RPM is jboss-messaging-1.4.0-1.SP3_CP02.0jpp.ep1.6.el4.noarch.rpm. I'll post more on where it came from when I can. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1381?page=com.atlassian.ji... ] Andrig Miller commented on JBMESSAGING-1381: -------------------------------------------- The EAP team produces the RPM's for RHEL 4 and 5, and that's why you wouldn't know anything about it. Fernando has commented that the RPM's are built in the same build as the official zip distributions, and that QE compares the two of them to make sure they are identical. With that process, its a mystery to me why there would be any issue here at all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1381?page=com.atlassian.ji... ] Tim Fox commented on JBMESSAGING-1381: -------------------------------------- The release notes for the JBM 1.4.0.SP3_CPO2 are explicit on this: http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_0_SP3_CP... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1381?page=com.atlassian.ji... ] Tim Fox reopened JBMESSAGING-1381: ---------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira