[JBoss-user] [Messaging, JMS JBossMQ] - Re: SQL exception with large number of JMS messages

2004-06-04 Thread genman
Oracle's thin driver is a broken Piece Of Shit which can cause broken connections, especially with BLOBs or CLOBs larger than 4k, so I suggest you use either the OCI driver or some other third party driver for JMS persistence. View the original post :

[JBoss-user] [Messaging, JMS JBossMQ] - Re: SQL exception with large number of JMS messages

2004-06-04 Thread hbaxmann
There is no problem to use 10g drivers for 8i, they are backward compatible with 8i. bax View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837589#3837589 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837589

[JBoss-user] [Messaging, JMS JBossMQ] - Re: SQL exception with large number of JMS messages

2004-06-03 Thread [EMAIL PROTECTED]
The first message is in the FAQ (but looks irrelevent?) The error says the db connection is broken. In fact, the part you posted is where it is trying to close the connection because it encountered a problem. P.S. As I've said many times, you don't need an XA connection for JBossMQ persistence,

[JBoss-user] [Messaging, JMS JBossMQ] - Re: SQL exception with large number of JMS messages

2004-06-03 Thread FBoss
The reason we switched to use XA with JMS is because we want the transaction of sending of JMS message to join with caller's transaction so they commit together as the message bean that does the post payment processing needs some data from the payment EJB commited to the database. I'll look