[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
I'm labouring this one a bit more, I know... but having seen this in the server.log... I'm trying my luck... | | 2009-02-13 10:45:14,913 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) org.jboss.messaging.core.impl.failoverwai...@128b200 blocking on the failover lock, waiting for failover to start | 2009-02-13 10:45:15,750 DEBUG [org.jgroups.protocols.MERGE2] (Timer-4,192.168.8.117:7900) 192.168.8.117:7900 is looking for merge candidates, found initial_mbrs=[[own_addr=192.168.8.118:7900, coord_addr=192.168.8.117:7900, is_server=true], [own_addr=192.168.8.117:7900, coord_addr=192.168.8.117:7900, is_server=true]] | 2009-02-13 10:45:16,360 DEBUG [org.jgroups.protocols.MERGE2] (Timer-9,192.168.8.117:49704) 192.168.8.117:49704 is looking for merge candidates, found initial_mbrs=[[own_addr=192.168.8.118:56013, coord_addr=192.168.8.117:49704, is_server=true], [own_addr=192.168.8.117:49704, coord_addr=192.168.8.117:49704, is_server=true]] | Then later on | | 2009-02-13 10:46:14,914 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) org.jboss.messaging.core.impl.failoverwai...@128b200 releasing the failover lock, checking again whether failover started ... | 2009-02-13 10:46:14,914 DEBUG [org.jboss.messaging.core.impl.FailoverWaiter] (WorkerThread#6[192.168.8.125:47389]) Timed out waiting for failover to start | 2009-02-13 10:46:14,915 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (WorkerThread#4[192.168.8.125:47391]) removing callback handler ServerInvokerCallbackHandler[5c4o83h-nlkeqt-fr4rzxwx-1-fr4sagqo-s2g+5c4o83h-nlkeqt-fr4rzxwx-1-fr4sagr5-s2l] | 2009-02-13 10:46:14,915 DEBUG [org.jboss.remoting.InvokerRegistry] (WorkerThread#4[192.168.8.125:47391]) removed SocketClientInvoker[11aed12, bisocket://192.168.8.125:342501498] from registry | 2009-02-13 10:46:14,917 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] (WorkerThread#4[192.168.8.125:47391]) SocketClientInvoker[11aed12, bisocket://192.168.8.125:342501498] disconnecting ... | 2009-02-13 10:46:14,919 DEBUG [org.jboss.jms.server.remoting.ServerSocketWrapper] (WorkerThread#4[192.168.8.125:47391]) wrote CLOSING byte This has happened, but my client apps still continue to send/receive messages after this. So I assume that it just picked up the same JMS connection and continued? Thanks again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209864#4209864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209864 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Thanks. Appreciate the response... maybe you can persuade the powers that be to get a support contract ;) I'll take a look at the jgroups, but one thing that comes to mind are the effects (good or otherwise) of running the cluster in Virtual environments - are there any known issues with this? Given that we're running both JBoss and MySQL in VMs? I've not seen anything obvious, but in some searches I'm sure I've seen passing comments on this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209827#4209827 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209827 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Sounds to me like your nodes aren't forming a cluster either due to some network issue between them, or some problem in your config. To see if they are forming a cluster just start one up, you'll see a load of JGroups output on the console. Then start the other one up, as the other one starts up you should see the first one recognise the second one has joined the group in the console output. Also have a look at the JGroups docs, which has stuff about diagnosing network problems. Best bet for you is to use your support contract if you have one - the support team are experienced in taking people through installation / environment / config issues. If you don't have a support contract it's very hard for us to provide in depth debugging of a remote setup. Any help on the forums is done off our own backs / in our free teams, and the main work that we get paid for takes priority. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209819#4209819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209819 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
I was wondering if there are any takers for this one? There doesn't seem to be anything obviously wrong with our setup (in terms of the mysql-d.xml and ndb-persistence-service.xml). What we're seeing is 1. Periodically messages will node be pulled across from one node to another. This can happen straight after starting up the JBoss cluster. Sender application sends messages in, but the receiver doesn't pick them up. (Yes, we've seen this even running the sample distributed queue application. Again, though this doesn't happen all the time) 2. After the above, if we stop the "Sender" JBoss instance and fail the messages over to the other node in the cluster, the receiver gets the messages. 3. Another scenario - under load (e.g. trying to send in 4 messages of 20k characters) both sender and receiver applications will throw repeated exceptions from the FailoverCommandCenter indicating that there's been failover of the underlying JMS connection. The set-up is that we're running the JBoss/MySQL cluster on 2 VMs Any suggestions? Thanks, View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209816#4209816 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209816 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
anonymous wrote : If the example doesn't work then then the most likely cause is a problem in your environment. OK. That's been my question - where to look for anything obvious. The problem doesn't happen all the time - I can see that. I'm printing out the publisher's and consumer's serverID and can see that they're different . I have LoadBalancing=true so that two calls to the connection factory get two different connections. It appears to be that sometimes I bring up the cluster and it's OK; other times starting the 2 instances gives me these problems. At first I thought it was specifically related to higher message load, but obviously not if the test program fails. Any takers on this one? I appreciate people are busy, so any suggestions are welcome. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209005#4209005 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209005 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
The distributed queue examples should demonstrate messages being pulled from one node to another. If the example doesn't work then then the most likely cause is a problem in your environment. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208993#4208993 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208993 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Thanks for the info. Yes, I had seen the wiki, and I've been using the ndb persistence file. I've run the distributed-queue example from the 1.4.1-Beta download - I think that should be closest to what's in JBoss5 - and have substituted the JBoss5 client jars in there.. What I'm seeing is that messages are only read from the node that they are sent in on i.e sender node 0, receiver node 1 - message is not picked up, Next time is sender node 1, receiver node 0, then it picks up the previous message So messages are not being pulled across the cluster - which is similar to some of the other problems I'm seeing. But, based on what I've seen before this doesn't always happen. Any pointers? Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208985#4208985 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208985 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
"jbabad" wrote : Hi, | | Apologies for giving this one a nudge, but I've just had the scenario again where I'm sending in messages to one half of a Jboss/MySQL cluster and a receiver connected to the other half of the cluster doesn't pick up the messages unless I fail over the "sender" side of the cluster. | | Thanks again for people's time. | Joseph. Have you read this wiki? http://www.jboss.org/community/docs/DOC-10095 Also did you run the clustered examples from the distro successfully? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208955#4208955 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208955 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
"jbabad" wrote : | | I seem to be hitting a brick wall in terms of JBM and MySQL clustering. Does anyone have a representative set of config parameters for JBM and MySQL NDB? | | JBM 1.4 ships with a ndb-persistence-service.xml in with all the other xxx-persistence-service.xml files. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208952#4208952 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208952 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Hi, Apologies for giving this one a nudge, but I've just had the scenario again where I'm sending in messages to one half of a Jboss/MySQL cluster and a receiver connected to the other half of the cluster doesn't pick up the messages unless I fail over the "sender" side of the cluster. Thanks again for people's time. Joseph. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208944#4208944 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208944 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Hi, a couple more questions to add to the list... - in JBM_POSTOFFICE table, should the ALL_NODES field for the clustered queues be set to Y or N? In my setup it is 'N', the CLUSTERED column is 'Y' for both references to the clustered queue on each node. - I've noticed that when messages get stuck in my scenario (messages come in via JBoss1/mysql1 and are read view Jboss2/mysql2) - forcing a failover will often change the channel Id in JBM_MSG_REF from Jboss1's channel to Jboss2 - and will mean that the receiver now reads the "stuck" messages. I seem to be hitting a brick wall in terms of JBM and MySQL clustering. Does anyone have a representative set of config parameters for JBM and MySQL NDB? Cheers, Joseph View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208495#4208495 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208495 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Hi, Sorry, for my lack of MySQL knowledge - what parameter is that? I can find references to an innodb buffer variable, but for clustering we're using the ndb engine. Thanks, Joseph. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4208160#4208160 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4208160 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
can you try increasing the size of the MySQL lock table overflow View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207769#4207769 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207769 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Hi, This is a follow-on... similar testing I've now seen the set of exceptions below. Is there some configuration of JBoss/MySQL that I'm missing? It's quite difficult to reliably replicate the problem at a known point, but I am seeing these errors and the ones in the previous posting happen on a regular basis. Any help/suggestions would be really appreciated. The other question I suppose I should ask is whether people have experienced these sorts of issues either with JBoss4.2.x/JBossMQ combination or with JBoss4.2.x/JBM1.4.2 Thanks, Joseph. | 13:54:48,442 WARN [JDBCSupport] SQLException caught, SQLState HY000 code:1296- assuming deadlock detected, try:1 | java.sql.SQLException: Got error 4010 'Node failure caused abort of transaction' from NDB | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447) | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951) | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101) | at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2554) | at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1761) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2046) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1964) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1949) | at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365) | at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(JDBCPersistenceManager.java:1637) | at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JDBCPersistenceManager.java:1370) | 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:1408) | at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:226) | at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2212) | at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:499) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:755) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:397) | 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.invokeTarget(SessionAdvised$send_7280680627620114891.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157) | at sun.reflect.GeneratedMethodAccessor281.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 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:908) | at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) | 13:54:48,444 WARN [JDBCSupport] Trying again after a pause | 13:54:48,525 WARN [TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.txconnectionmanager$txconnectioneventliste...@9eb61a[state=normal mc=org.jboss.resource.adapter.jdbc.local.localmanagedconnect...@1323140 handles=1 lastUse=1233928488441 permit=true trac
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
OK, here are some errors that I'm seeing 09:44:14,178 WARN [JDBCSupport] SQLException caught, SQLState HY000 code:1296- assuming deadlock detected, try:1 | java.sql.SQLException: Got error 266 'Time-out in NDB, probably caused by deadlock' from NDB | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447) | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951) | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101) | at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2554) | at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1761) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2046) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1964) | at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1949) | at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365) | at org.jboss.messaging.core.impl.JDBCPersistenceManager.cacheID(JDBCPersistenceManager.java:1637) | at org.jboss.messaging.core.impl.JDBCPersistenceManager$1AddReferenceRunner.doTransaction(JDBCPersistenceManager.java:1370) | 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:1408) | at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:226) | at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2212) | at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:499) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:755) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:397) | 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.invokeTarget(SessionAdvised$send_7280680627620114891.java) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157) | at sun.reflect.GeneratedMethodAccessor283.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 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:908) | at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) | 09:44:14,189 WARN [JDBCSupport] Trying again after a pause | 09:44:14,282 WARN [JDBCSupport] Update worked after retry | Also, this one... | 09:45:15,657 WARN [JDBCSupport] SQLException caught, SQLState HY000 code:1296- assuming deadlock detected, try:1 | java.sql.SQLException: Got error 286 'Node failure caused abort of transaction' from NDB | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3515) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3447) | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1951) | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2101) | at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImp
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
probably you have another consumer somewhere which has buffered those messages ready for consumption. see prefetchsize this has been discussed a lot before View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207618#4207618 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207618 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
anonymous wrote : So, what I see is that for normal operation, messages go into the cluster via Jboss1/mysql2, but get pulled off via Jboss2/mysql2 yes thats correct. anonymous wrote : But... when I sent 5000 messages in, I'm seeing 100-200 messages getting stuck and not being picked up by the receiver process. Hmmm, have you checked the logs for any errors? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207617#4207617 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207617 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Thanks guys for the responses. Can I move the question a bit? As I said we're running a JBoss Cluster using MySQL 5.0.51 as the underlying JMS data store. I'm trying to send 5000 messages (20k each) through the system - with a sender and receiver client. Lets call the 2 JBoss instances Jboss1 and Jboss2 and the two MySQL data notes mysql1 and mysql2 Jboss1 has a datasource pointing to mysql1; Jboss2 points to mysql2. My sender app is connecting to the JNDI on Jboss1 and getting a ClusteredConnectionFactory, The receiver is doing the same, but on Jboss2. So, what I see is that for normal operation, messages go into the cluster via Jboss1/mysql2, but get pulled off via Jboss2/mysql2 But... when I sent 5000 messages in, I'm seeing 100-200 messages getting stuck and not being picked up by the receiver process. Any ideas? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207452#4207452 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207452 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
anonymous wrote : Sorry, just to clarify... are you saying that blobs are not stored in the table and it's just the reference that is stored? sorry for the typo, I mean internally the database stores the blob reference/pointer to the table row, the contents of blob (which can be huge) has another location to store. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207266#4207266 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207266 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
anonymous wrote : Sorry, just to clarify... are you saying that blobs are not stored in the table and it's just the reference that is stored? The message is payload is stored as a blob in the JBM_MSG table. anonymous wrote : Also, do you know if there's a maximum message size - as I mentioned we tried 10k, but potentially we could be using 20k+? Only memory will restrict how big a message is. Also afaik mysql cluster maximum row size does not include blobs so you are ok. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207255#4207255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207255 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Hi, thanks for the response, anonymous wrote : 10k message is ok. Blobs are not store in the table as references or pointers. Sorry, just to clarify... are you saying that blobs are not stored in the table and it's just the reference that is stored? Also, another silly question... but in that case how/where is the actual blob data stored? Also, do you know if there's a maximum message size - as I mentioned we tried 10k, but potentially we could be using 20k+? Thanks for you help View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207248#4207248 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207248 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: MySQL in Cluster question
Hi, 10k message is ok. Blobs are not store in the table as references or pointers. So 8k should be ok enough. JB5's messaging are tested against mysql 5.0.x, so if you upgrade, it's all st your own risk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207194#4207194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207194 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
