[jboss-user] [Messaging, JMS JBossMQ] - Re: different order between sending and receiving(FIFO)
If anyone can help me I would appreciate it. I have re-run my testing with some jboss server side logging enabled. I have also included some logging to let me know when the receiving Client experiences a timeout on the receive(2000) call. It times out more often that I would expect considering the fact that there is no lack of messages to read, but that could be associated with general house cleaning, etc. The following is an snippet from my simple client log indicating that right after the client timed out on a receive(2000) call and subsequently paused for .25 of a second before calling receive again it read the wrong message. As you can see the JMS Msg ID: 1-1196727135200779567 was received about 6 messages late... | 0:12:14 11/4/2007) Correct -- serial:[41553] MsgID:[1-1196727134895779565] | 0:12:15 11/4/2007) Correct -- serial:[41554] MsgID:[1-119672713509566] | 0:12:17 11/4/2007) (2) Sec TIMEOUT -- Delay .25 Secs, prev:[1-119672713509566] | 0:12:20 11/4/2007) Wrong -- serial:[41556] MsgID:[1-1196727135337779568] | 0:12:20 11/4/2007) Correct -- serial:[41557] MsgID:[1-1196727135484779569] | 0:12:20 11/4/2007) Correct -- serial:[41558] MsgID:[1-1196727135686779570] | 0:12:20 11/4/2007) Correct -- serial:[41559] MsgID:[1-1196727135792779571] | 0:12:20 11/4/2007) Correct -- serial:[41560] MsgID:[1-1196727136006779572] | 0:12:20 11/4/2007) Correct -- serial:[41561] MsgID:[1-1196727136131779573] | 0:12:20 11/4/2007) Wrong -- serial:[41555] MsgID:[1-1196727135200779567] | 0:12:20 11/4/2007) Wrong -- serial:[41562] MsgID:[1-1196727136262779574] | 0:12:20 11/4/2007) Correct -- serial:[41563] MsgID:[1-1196727136444779575] | 0:12:20 11/4/2007) Correct -- serial:[41564] MsgID:[1-1196727136657779576] | 0:12:20 11/4/2007) Correct -- serial:[41565] MsgID:[1-1196727136778779577] | It is important to Note: Although I had quite a few Timeouts I did not receive a message in the wrong order after every timeout. However, for each message that was out of order it was ALWAYS directly after a Timeout of the receive(2000). I have varied my subsequent delay after a receive() times out ranging from .125 - .5 seconds. Without fixing the problem! Do I need to pause in the order of multiple seconds? The following is a snippet from the jboss server logs indicated the basic queue activity at the time of the error. It also shows that the message in question was delivered late. However, it shows an interesting NACK to its Acknowledgment. The simple client that I use is set to read with Client Acknowledgment and I only ACK successful receives. In other words, I do not have any NACK code on my side. Again, I am using a default installation of 4.2.2GA with the exception that my db is mysql. I have added this log entry as an image because it is so large... [img]http://www.northstarssoccerclub.com/jboss_error.png[/img] Thanks In Advance! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4110354#4110354 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110354 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: different order between sending and receiving(FIFO)
One last point. In addition to using a 2 second timeout on the receive call, I also pause for .25 seconds before calling receive again if I do timeout. I was hoping to avoid that race condition that I have read is possible ( or was possible ). However, remember that messages are moving at around 200 ms intervals. I should never timeout. The only evidence that I have is that the logs on the sending side do not show any signs that writing to the Queue was delayed during any of the out of order periods. The logging on the receiving side is limited to just the bad messages. Thanks In Advance, for your help! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109389#4109389 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109389 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: different order between sending and receiving(FIFO)
I am seeing basically the same issue as the original poster - however, I can find no solution. -I am using multiple Solaris 8 platforms with older hardware. -I have experienced the problem on both jboss v4.0.5GA and v4.2.2GA. -I am using a default jboss configuration with the one exception that I have altered it to use an mysql backend. In my situation I have multiple servers involved in the messages lifespan but I do not use any clustering and I have only one poster/consumer on any one Queue at any time. Senerio: 1. Each message contains a unique (sequential) serial number in its body. 2. Messages are written to a JMS Queue A on server #1 at around 200 millisecond intervals. 3. Messages are read from the Queue A manipulated and sent thru other servers using ordinary TCP sockets. The destination server writes the resulting message back to a new JMS Queue B on server #5. 4. Final application is sitting in an infinite loop reading messages as fast as it can from Queue B with CLIENT_ACKNOWLEDGE set and using 'receive(2000)' - Note: 2 second timeout. Each message that is read is acknowledged then the unique serial number is parsed from the message contents and compared to previously received messages. I always receive about a half a dozen messages out of order in a 300-350 thousand message set. The unique serial number stays consistently in sync with the JMS Message ID that is stored in the message header. This implies that the messages are written to the JMS Queue B in the correct order. It is only when I read them back that they become out of order. Normally, an out of order message will only be off by one message. However, I have had examples where a message is actually retrieved 5 messages late ( roughly a second late ). Between the unique serial number in the message body and the JMS Message ID and logging that I perform on the sending side I am confident that the messages are being written in order. I have to be able to say(guarantee) that we can deliver message in a FIFO order. I can not find any comments or postings suggestion that anyone has a fix for this. I know current development is geared toward Jboss v5 and Jboss Messaging versus JbossMQ, but I need to find a fix for this! What can I do? Do you have any suggestions? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109386#4109386 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109386 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
