RE: problem with ResultSet Object
CachedRowSet doesn't participate in transactions as it is teared-off object and it stores stale (old) data. For high-volume concurrent updating requests use it with care ( or better not to use if you are not sure ). I use it for read-only data infrequent access. -Original Message- From: sachin mahajan [SMTP:[EMAIL PROTECTED]] Sent:15 2002 6:32 To: Orion-Interest Subject:Re: problem with ResultSet Object Hello Thanks. Can u explain me if i will use CachedRowSet object instead of ResultSet object. How my application is affected and it is scalable or not. sachin - Original Message - From: Dvornikov Victor [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Thursday, February 14, 2002 1:48 PM Subject: RE: problem with ResultSet Object ResultSEt is not a serializable object. For RMI purpose use CachedRowSet object Take into account that this object is not for scalable applications! -Original Message- From: sachin mahajan [SMTP:[EMAIL PROTECTED]] Sent: 14 2002 6:51 To: Orion-Interest Cc: sachin mahajan Subject: problem with ResultSet Object Dear Sir Currently i am working om the orion server. i have deployed my application properly. But i am facing some problem with transfering ResultSet object from my EJB to jsp . It error i am facing is this inside basedl The statement is oracle.jdbc.driver.OracleStatement@9617f825 inside basedl The resultset is oracle.jdbc.driver.OracleResultSet@c72ff82a Resultset is before returning :*** oracle.jdbc.driver.OracleResultSet@c72ff82a inside buildselect exception is com.evermind.server.rmi.OrionRemoteException: Error (de-)serializing object: ora cle.jdbc.driver.OracleResultSet at com.evermind.server.ejb.EJBUtils.cloneObject(Unknown Source) at ConnectionPool_StatelessSessionBeanWrapper0.read(ConnectionPool_State lessSessionBeanWrapper0.java, Compiled Code) can any body tell me how to solve this problem Waiting for your reply.. regds sachin _ 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: A word of warning: SwiftMQ and Resource providers.
Geoff, It IS fixed in 1.5.4, so please let us know what fails for you. Here is a sample setup: 1. Set up and start SwiftMQ. 2. In your /config/application.xml have a setup like the following: resource-provider class=com.evermind.server.deployment.ContextScanningResourceProvider display-name=SwiftMQ resource name=SwiftMQ description SwiftMQ resource provider. /description property name=java.naming.factory.initial value=com.swiftmq.jndi.InitialContextFactoryImpl / property name=java.naming.provider.url value=smqp://localhost:4001 / property name=resource.names value=testtopic,testqueue@router1,plainsocket@router1 / /resource-provider 3. Start Orion, deploy the ATM sample (it uses a MDB with a topic) 4. Configure the ATM sample to use your resource provider with something like the following in your orion-ejb-jar.xml: message-driven-deployment name=mainLogger destination-location=java:comp/resource/SwiftMQ/testtopic connection-factory-location=java:comp/resource/SwiftMQ/plainsocket@rout er1 ejb-ref-mapping name=ejb/mainLog / /message-driven-deployment Could you please let me know where/how this fails for you? WR -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Geoff Soutter Sent: den 18 februari 2002 02:50 To: Orion-Interest Subject: RE: A word of warning: SwiftMQ and Resource providers. FYI, this was not fixed in 1.5.4. Naughty Magnus! :-) Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ray Harrison Sent: Monday, 14 January 2002 8:50 AM To: Orion-Interest Subject: Re: A word of warning: SwiftMQ and Resource providers. According to Magnus R, the problem will be fixed in the next release. I don't know if you can use SwiftMQ / Topics with the Oracle code base (OC4J), but maybe worth a shot. Hopefully soon from the good folks at Orion! --- Graham Bennett [EMAIL PROTECTED] wrote: On Tue, Nov 20, 2001 at 12:29:54PM +0200, Lachezar Dobrev wrote: Recently looking at the Resource-Providers docs, and EAGER to use an external JMS for my MDBs I and a colleague decided to run the demos. As quite a surprise the demo run ok. The MDB did everything when a message was sent to the Queue. The BIG disappointment was, when we tried to do the same with the topic. In short: It does not work. Error deploying file:/D:/Temp/Orion/applications/Orion2SwiftMQ/Orion2SwiftMQ.jar homes: JMS Error: Queue 'testtopic' is not local! Can't create a Consumer on it! has this now been fixed? I'm getting the same error with SwiftMQ and the latest build. cheers, -- Graham Bennett [EMAIL PROTECTED] __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
