Re: Orion MDB reverses message order with SwiftMQ as well as OrionJMS (was RE: fyi: 1.5.4 still stacks rather than queues JMS messages)
Well, I just tested an MDB with SwiftMQ, and Orion still stuffs up the message ordering. --Geoff Soutter Please read the EJB2.0 spec before recording this as a bug. Message order is not guaranteed in MDB's. - Original Message - From: Geoff Soutter [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Sunday, February 17, 2002 10:45 PM Subject: Orion MDB reverses message order with SwiftMQ as well as OrionJMS (was RE: fyi: 1.5.4 still stacks rather than queues JMS messages) Well, I just tested an MDB with SwiftMQ, and Orion still stuffs up the message ordering. Presumably this means it's broken in the MDB implemenation rather than in Orion's JMS code, which is a pity. So, for all those using Orion MDBs, and relying on message ordering being preserved (if there are any apart from me :-), please check out bug 729 in Bugzilla. It contains demo code to demonstrate the problem under both Orion JMS and SwiftMQ. http://bugzilla.orionserver.com/bugzilla/show_bug.cgi?id=729 Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Geoff Soutter Sent: Monday, 18 February 2002 9:18 AM To: Orion-Interest Subject: RE: fyi: 1.5.4 still stacks rather than queues JMS messages Hi Mike, I didn't see that comment. Unfortunately this list is so flakey that I only get about 75% of the messages. I just checked the JMS 1.02 spec, here's what it has to say about message order (in 4.4.10.1 Order of Message Receipt): JMS defines that messages sent by a session to a destination must be received in the order in which they were sent (see Section 4.4.10.2, Order of Message Sends, for a few qualifications). So it seems that, contrary to what that someone said, message order _is_ important with JMS. Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Saturday, 16 February 2002 8:43 AM To: Orion-Interest Subject: Re: fyi: 1.5.4 still stacks rather than queues JMS messages Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
RE: Orion MDB reverses message order with SwiftMQ as well as OrionJMS (was RE: fyi: 1.5.4 still stacks rather than queues JMS messages)
Hi there, Actually I didn't read the EJB spec as I had guessed it was a JMS bug originally, so thanks for pointing that out. Very lazy of me. However, section 15.4.6 Concurrency of Message Processing of the EJB 2.0 spec says: the container should attempt to deliver messages in order when it does not impair the concurrency of message processing. I have max-instances set to 1, which means that there is _no_ concurrency. Thus, the container ought to deliver messages in order. Note also that the JMS spec mentions that messages ought to be delivered in order as well. Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Poop Sent: Tuesday, 19 February 2002 12:11 AM To: Orion-Interest Subject: Re: Orion MDB reverses message order with SwiftMQ as well as OrionJMS (was RE: fyi: 1.5.4 still stacks rather than queues JMS messages) Well, I just tested an MDB with SwiftMQ, and Orion still stuffs up the message ordering. --Geoff Soutter Please read the EJB2.0 spec before recording this as a bug. Message order is not guaranteed in MDB's. - Original Message - From: Geoff Soutter [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Sunday, February 17, 2002 10:45 PM Subject: Orion MDB reverses message order with SwiftMQ as well as OrionJMS (was RE: fyi: 1.5.4 still stacks rather than queues JMS messages) Well, I just tested an MDB with SwiftMQ, and Orion still stuffs up the message ordering. Presumably this means it's broken in the MDB implemenation rather than in Orion's JMS code, which is a pity. So, for all those using Orion MDBs, and relying on message ordering being preserved (if there are any apart from me :-), please check out bug 729 in Bugzilla. It contains demo code to demonstrate the problem under both Orion JMS and SwiftMQ. http://bugzilla.orionserver.com/bugzilla/show_bug.cgi?id=729 Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Geoff Soutter Sent: Monday, 18 February 2002 9:18 AM To: Orion-Interest Subject: RE: fyi: 1.5.4 still stacks rather than queues JMS messages Hi Mike, I didn't see that comment. Unfortunately this list is so flakey that I only get about 75% of the messages. I just checked the JMS 1.02 spec, here's what it has to say about message order (in 4.4.10.1 Order of Message Receipt): JMS defines that messages sent by a session to a destination must be received in the order in which they were sent (see Section 4.4.10.2, Order of Message Sends, for a few qualifications). So it seems that, contrary to what that someone said, message order _is_ important with JMS. Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Saturday, 16 February 2002 8:43 AM To: Orion-Interest Subject: Re: fyi: 1.5.4 still stacks rather than queues JMS messages Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
RE: fyi: 1.5.4 still stacks rather than queues JMS messages
Hi Mike, I didn't see that comment. Unfortunately this list is so flakey that I only get about 75% of the messages. I just checked the JMS 1.02 spec, here's what it has to say about message order (in 4.4.10.1 Order of Message Receipt): JMS defines that messages sent by a session to a destination must be received in the order in which they were sent (see Section 4.4.10.2, Order of Message Sends, for a few qualifications). So it seems that, contrary to what that someone said, message order _is_ important with JMS. Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Saturday, 16 February 2002 8:43 AM To: Orion-Interest Subject: Re: fyi: 1.5.4 still stacks rather than queues JMS messages Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve
RE: fyi: 1.5.4 still stacks rather than queues JMS messages
Yes, they should be received in order, but not necessarily stored/retrieved in order. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Geoff Soutter Sent: Sunday, February 17, 2002 5:18 PM To: Orion-Interest Subject: RE: fyi: 1.5.4 still stacks rather than queues JMS messages Hi Mike, I didn't see that comment. Unfortunately this list is so flakey that I only get about 75% of the messages. I just checked the JMS 1.02 spec, here's what it has to say about message order (in 4.4.10.1 Order of Message Receipt): JMS defines that messages sent by a session to a destination must be received in the order in which they were sent (see Section 4.4.10.2, Order of Message Sends, for a few qualifications). So it seems that, contrary to what that someone said, message order _is_ important with JMS. Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Saturday, 16 February 2002 8:43 AM To: Orion-Interest Subject: Re: fyi: 1.5.4 still stacks rather than queues JMS messages Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve
Orion MDB reverses message order with SwiftMQ as well as OrionJMS (was RE: fyi: 1.5.4 still stacks rather than queues JMS messages)
Well, I just tested an MDB with SwiftMQ, and Orion still stuffs up the message ordering. Presumably this means it's broken in the MDB implemenation rather than in Orion's JMS code, which is a pity. So, for all those using Orion MDBs, and relying on message ordering being preserved (if there are any apart from me :-), please check out bug 729 in Bugzilla. It contains demo code to demonstrate the problem under both Orion JMS and SwiftMQ. http://bugzilla.orionserver.com/bugzilla/show_bug.cgi?id=729 Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Geoff Soutter Sent: Monday, 18 February 2002 9:18 AM To: Orion-Interest Subject: RE: fyi: 1.5.4 still stacks rather than queues JMS messages Hi Mike, I didn't see that comment. Unfortunately this list is so flakey that I only get about 75% of the messages. I just checked the JMS 1.02 spec, here's what it has to say about message order (in 4.4.10.1 Order of Message Receipt): JMS defines that messages sent by a session to a destination must be received in the order in which they were sent (see Section 4.4.10.2, Order of Message Sends, for a few qualifications). So it seems that, contrary to what that someone said, message order _is_ important with JMS. Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Saturday, 16 February 2002 8:43 AM To: Orion-Interest Subject: Re: fyi: 1.5.4 still stacks rather than queues JMS messages Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve
RE: fyi: 1.5.4 still stacks rather than queues JMS messages
Hi Russ, What exactly do you mean by stored/retrieved? Is there a reference in the spec you can point out? Cheers Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Russ White Sent: Monday, 18 February 2002 11:47 AM To: Orion-Interest Subject: RE: fyi: 1.5.4 still stacks rather than queues JMS messages Yes, they should be received in order, but not necessarily stored/retrieved in order. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Geoff Soutter Sent: Sunday, February 17, 2002 5:18 PM To: Orion-Interest Subject: RE: fyi: 1.5.4 still stacks rather than queues JMS messages Hi Mike, I didn't see that comment. Unfortunately this list is so flakey that I only get about 75% of the messages. I just checked the JMS 1.02 spec, here's what it has to say about message order (in 4.4.10.1 Order of Message Receipt): JMS defines that messages sent by a session to a destination must be received in the order in which they were sent (see Section 4.4.10.2, Order of Message Sends, for a few qualifications). So it seems that, contrary to what that someone said, message order _is_ important with JMS. Cheers, Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Saturday, 16 February 2002 8:43 AM To: Orion-Interest Subject: Re: fyi: 1.5.4 still stacks rather than queues JMS messages Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve
Re: fyi: 1.5.4 still stacks rather than queues JMS messages
Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208
Re: fyi: 1.5.4 still stacks rather than queues JMS messages
Geoff, Also as someone said on this list just a few days ago - as per the JMS spec there is no guarantee that your messages turn up in the sequence you sent them. Cheers, Mike Mike Cannon-Brookes [EMAIL PROTECTED] Atlassian :: www.atlassian.com Supporting YOUR world On 16/2/02 12:55 AM, Stephen Davidson ([EMAIL PROTECTED]) penned the words: Geoff Soutter wrote: Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff I am using the Orion JMS, but the way the code is set up, it does not care about the order the messages arrived. I had never noticed the Out of Order issue, as it was not applicable. -Steve
fyi: 1.5.4 still stacks rather than queues JMS messages
Re the problem reported a couple weeks back by Jorge Jimenez and confirmed by myself, I tested 1.5.4 to see if they had fixed this problem, but it's still there. Just set max-instances to 1 and load up with a lot of messages, it works just like a stack. Doh. Maybe I'll have time to put this into Bugzilla next week... Is _everyone_ using a third party JMS with Orion? geoff
