Oracle JMS PersistenceManager issues JBoss 3.2.3 - Exception
Hi,
I have the following setup; JBoss 3.2.3, JVM 1.4.2_04-b05 SPARC, Oracle 9.2.0.1.0. I have configured the JMS PersistenceManager to use Oracle for persisting JMS messages by removing the Hypersonic config file and replacing it with the Oracle one located in the docs/exampls/jms/oracle-jdbc2-service.xml.
When the server starts up it is creating the JMS_MESSAGES, and JMS_TRANSACTIONS tables ok (hence the Oracle thin client JCA DS is good). However as soon as a message is queued I get the following Exception stack;
Caused by: java.sql.SQLException: No more data to read from socket at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java) at oracle.jdbc.dbaccess.DBError.check_error(DBError.java) at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java) at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java) at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java) at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java) at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:324) at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:783) at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:730) ... 95 more 23:14:32,996 ERROR [STDERR] java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: null; CausedByException is: Could not store message: 1 msg=0 hard NOT_STORED PERSISTENT queue=QUEUE.reportDataEngine priority=4 hashCode=26560238; - nested throwable: (java.sql.SQLException: No more data to read from socket)
Has anyone else encountered this issue, and if so how do I go about rectifying the problem?
BTW - I have enabled TRACE level diagnostics via the log4j.xml as per the 'READ THIS FIRST' in the forum. The only JMS related stuff that I get is the following though
bash-2.05$ grep TRACE ../server/default/log/server.log 2004-10-16 23:10:25,823 TRACE [org.jboss.jms.jndi.JMSProviderLoader] Constructing 2004-10-16 23:10:25,839 TRACE [org.jboss.jms.asf.ServerSessionPoolLoader] Constructing 2004-10-16 23:12:58,557 TRACE [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Constructing 2004-10-16 23:13:02,768 TRACE [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Constructing 2004-10-16 23:13:05,549 TRACE [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Constructing 2004-10-16 23:13:10,587 TRACE [org.jboss.ejb.plugins.jms.DLQHandler] Constructing 2004-10-16 23:13:11,458 TRACE [org.jboss.ejb.plugins.jms.DLQHandler] Constructing 2004-10-16 23:13:11,838 TRACE [org.jboss.ejb.plugins.jms.DLQHandler] Constructing
Thanks and regards,
Andrew
