Re: Persistent JMS Queue
Darryl, OC4J 1.0.2.2 roughly corresponds with Orion 1.5.2. The 1.0.2.2.1 release has many bugfixes that will (according to what I know) be integrated back into the orion codebase. Cheers, Scott -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World Darryl Dieckman wrote: > Thanks. We downloaded the latest orion server (1.5.2) and > found that the problem had been fixed. We are using the > Oracle OC4J, so I'm not really sure what version it truly is. > It reports an Oracle version, but I can assume that it is certainly > not 1.5.2. > > It says > Oracle9iAS (1.0.2.2.1) Containers for J2EE > > Just out of curiosity, does anyone know what version this > corresponds to? > > Darryl Dieckman > > > > >
RE: Persistent JMS Queue
This is Orion 1.5.2 plus a few extra fixes. -mike Mike Cannon-Brookes :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Darryl > Dieckman > Sent: Monday, September 17, 2001 12:37 PM > To: Orion-Interest > Cc: [EMAIL PROTECTED] > Subject: RE: Persistent JMS Queue > > > Thanks. We downloaded the latest orion server (1.5.2) and > found that the problem had been fixed. We are using the > Oracle OC4J, so I'm not really sure what version it truly is. > It reports an Oracle version, but I can assume that it is certainly > not 1.5.2. > > It says > Oracle9iAS (1.0.2.2.1) Containers for J2EE > > Just out of curiosity, does anyone know what version this > corresponds to? > > Darryl Dieckman > > >
RE: Persistent JMS Queue
Thanks. We downloaded the latest orion server (1.5.2) and found that the problem had been fixed. We are using the Oracle OC4J, so I'm not really sure what version it truly is. It reports an Oracle version, but I can assume that it is certainly not 1.5.2. It says Oracle9iAS (1.0.2.2.1) Containers for J2EE Just out of curiosity, does anyone know what version this corresponds to? Darryl Dieckman
RE: Persistent JMS Queue
Title: RE: Persistent JMS Queue I think its been fixed in 1.5.2. What version of orion are you using? Kesav Kumar Kolla Voquette Inc 650 356 3740(W) 510 889 6840(R) VoquetteDelivering Sound Information -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 13, 2001 10:45 AM To: Orion-Interest Subject: Persistent JMS Queue Hello, I've got an application setup using the Orion JMS Provider and some message driven beans. I turned on the persistence for the JMS queues in the JMS.xml. If I let messages get queued up in the queues by disabling my bean, and then shutdown the server, the messages in the queue are not delivered to my message driven bean the next time I start the server. There are definitely messages serialized in the queue, because I can see them by looking at the flat file. When I restart the server, my message driven bean successfully recieves new messages delivered to the queue. However, the messages persisted to the disk are never delivered. 1. Do I need to do something to cause the queues to be restored at startup? 2. Is there a bug in the JMS or message-driven bean that will not deliver messages that have been restored from a persistent queue? Darryl Dieckman
Persistent JMS Queue
Hello, I've got an application setup using the Orion JMS Provider and some message driven beans. I turned on the persistence for the JMS queues in the JMS.xml. If I let messages get queued up in the queues by disabling my bean, and then shutdown the server, the messages in the queue are not delivered to my message driven bean the next time I start the server. There are definitely messages serialized in the queue, because I can see them by looking at the flat file. When I restart the server, my message driven bean successfully recieves new messages delivered to the queue. However, the messages persisted to the disk are never delivered. 1. Do I need to do something to cause the queues to be restored at startup? 2. Is there a bug in the JMS or message-driven bean that will not deliver messages that have been restored from a persistent queue? Darryl Dieckman
