Are you using oci drivers for oracle? If not, then use them because the thin drivers have problems with large amounts of data..
I am using the normal thin driver for Oracle. I can see that the error appears when a JMS session should be closed. This happens after writing a message to a JMS queue (using the JDBC2 Persistence Manager for Oracle). After that the JBoss connection pool throws this error.
Can someone clarify the contexts between the JMS session, the JDBC Persistence Manager and the JBoss connection pool? I am still not sure what is causing this error. Does the connection pool size play a role here?
Thanks,
-marek
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
