From: Magesh P. <m.p...@pi...> - 2003-05-23 15:00:00
|
I managed to fix it..=20 When I turned on to DEBUG mode, it clearly showed message "equals missing" = which meant I had to change UPDATE JMS_MESSAGES SET (TXID, TXOP) VALUES(?,?) WHERE MESSAGEID=3D? AND DE= STINATION=3D? to (to make it work in Oracle) UPDATE JMS_MESSAGES SET TXID=3D?, TXOP=3D? WHERE MESSAGEID=3D? AND DESTINAT= ION=3D? On 5/23/03 3:13 PM, Magesh Prabhu <m.p...@pi...> wrote: >Thanx a lot, > >That fixed it. Now the message is sent to the destination and the=20 >Listener gets the message on the receiving end as well. But I got=20 >a new exception when the message is sent. I never use XA transactions.=20 >I'm only using LocalTxDS. Could anybody advice me on this please. > >The stack shows: >15:08:03,912 ERROR [StdServerSession] failed to commit/rollback >javax.transaction.xa.XAException > at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:100) > at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.j= ava:294) > at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(S= pyMessageConsumer.java:603 >) > at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.j= ava:417) > at org.jboss.mq.SpySession.run(SpySession.java:296) > at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:17= 8) > at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Pool= edExecutor.java:655) > at java.lang.Thread.run(Thread.java:536) > >On 5/23/03 1:44 PM, ulf...@mo... wrote: >> >>Try using >> >>=A0 =A0 =A0 =A0BLOB_TYPE=3DBINARYSTREAM_BLOB >> >>and >> >>=A0 =A0 =A0 CREATE_MESSAGE_TABLE =3D CREATE TABLE JMS_MESSAGES ( MESSAGEI= D> > INTEGER NOT NULL, \ >>=A0 =A0 =A0 =A0 =A0DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP = CHAR(1),=20 > >>\ >>=A0 =A0 =A0 =A0 =A0MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION)= > ) >>=A0 =A0 =A0 CREATE_TX_TABLE =3D CREATE TABLE JMS_TRANSACTIONS ( TXID INTE= GER=20 > >>) >> >>Regards, >>Ulf >> >> >> >>Magesh Prabhu <m.p...@pi...> >>Gesendet von: jbo...@li... >>23.05.2003 13:01 >>Bitte antworten an jboss-user >>=A0 =A0 =A0 =A0 >>=A0 =A0 =A0 =A0 An: =A0 =A0 =A0 =A0<jbo...@li...> >>=A0 =A0 =A0 =A0 Kopie: =A0 =A0 =A0 =A0 >>=A0 =A0 =A0 =A0 Thema: =A0 =A0 =A0 =A0[JBoss-user] Oracle JDBC Persistenc= e Store=20 > >>for jbossmq >> >> >>Hi guys, >> >>I'm using JDBC Persistence store for Jbossmq. I configured jbossmq-servic= e.xml=20 > >>to use JDBCPersistence store instead of disk store. I'm using Oracle8i=20 > >>database server running on Jboss 3.0.4 >> >>In SqlProperties, I changed the SQL type 'OBJECT' to 'BLOB' and=20 >'INTEGER'> > to 'NUMBER' >> >>CREATE_MESSAGE_TABLE =3D CREATE TABLE JMS_MESSAGES ( MESSAGEID NUMBER=20 > >>NOT NULL, \ >> =A0 DESTINATION VARCHAR(50) NOT NULL, TXID NUMBER, TXOP CHAR(1),=20 >\ >> =A0 MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) >> >>CREATE_TX_TABLE =3D CREATE TABLE JMS_TRANSACTIONS ( TXID NUMBER ) >> >>When I tried to send JMS messages, I got this exception: >>org.jboss.mq.SpyJMSException: Could not store message: 0; - nested=20 > >>throwable: (java.sql.SQLException: Invalid column type) >> >>The stack trace is follows. Could somebody guide me on this please... >> >>11:58:01,787 ERROR [STDERR] Caused by: java.sql.SQLException: Invalid=20 > >>column type >>11:58:01,787 ERROR [STDERR] =A0 =A0 at oracle.jdbc.dbaccess.DBError.throw= SqlException(DBError.java:134) >>11:58:01,787 ERROR [STDERR] =A0 =A0 at oracle.jdbc.dbaccess.DBError.throw= SqlException(DBError.java:179) >>11:58:01,787 ERROR [STDERR] =A0 =A0 at oracle.jdbc.dbaccess.DBError.throw= SqlException(DBError.java:269) >>11:58:01,787 ERROR [STDERR] =A0 =A0 at oracle.jdbc.driver.OraclePreparedS= tatement.setObject(OraclePreparedStatement.java:2886) >>11:58:01,787 ERROR [STDERR] =A0 =A0 at oracle.jdbc.driver.OraclePreparedS= tatement.setObject(OraclePreparedStatement.java:3015) >>11:58:01,807 ERROR [STDERR] =A0 =A0 at com.p6spy.engine.spy.P6PreparedSta= tement.setObject(P6PreparedStatement.java:287) >>11:58:01,807 ERROR [STDERR] =A0 =A0 at org.jboss.resource.adapter.jdbc.lo= cal.LocalPreparedStatement.setObject(LocalPreparedStatement.java:625) >>11:58:01,807 ERROR [STDERR] =A0 =A0 at org.jboss.mq.pm.jdbc2.PersistenceM= anager.add(PersistenceManager.java:717) >>11:58:01,807 ERROR [STDERR] =A0 =A0 at org.jboss.mq.pm.jdbc2.PersistenceM= anager.add(PersistenceManager.java:667) >>11:58:01,807 ERROR [STDERR] =A0 =A0 ... 43 more >> >> >> >>********************************************************************** >>This email and its attachments are intended for the above >>named only and may be confidential. =A0If they have come to >>you in error, you must take no action based on them, nor >>must you copy or show them to anyone; please reply to this >>email and highlight the error. >>Security Warning: Please note that this email has been >>created in the knowledge that the internet email is not a >>100% secure communications medium. =A0We advise that you >>understand and observe this lack of security when emailing us. >>Viruses: =A0Although we have taken steps to ensure that this >>email and attachments are free from any virus, we advise >>that in keeping with good computing practice the recipient >>should ensure they are actually virus free. >>If you have received this email in error please notify: >>pos...@pi... >>********************************************************************** >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: ObjectStore. >>If flattening out C++ or Java code to make your application fit=20 >in=20 >>a >>relational database is painful, don't do it! Check out ObjectStore. >>Now part of Progress Software. http://www.objectstore.net/sourceforge >>_______________________________________________ >>JBoss-user mailing list >>JBo...@li... >>https://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> > > > >********************************************************************** >This email and its attachments are intended for the above=20 >named only and may be confidential. If they have come to=20 >you in error, you must take no action based on them, nor=20 >must you copy or show them to anyone; please reply to this=20 >email and highlight the error. >Security Warning: Please note that this email has been=20 >created in the knowledge that the internet email is not a=20 >100% secure communications medium. We advise that you=20 >understand and observe this lack of security when emailing us. >Viruses: Although we have taken steps to ensure that this=20 >email and attachments are free from any virus, we advise=20 >that in keeping with good computing practice the recipient=20 >should ensure they are actually virus free. >If you have received this email in error please notify: >pos...@pi... >********************************************************************** > > > >------------------------------------------------------- >This SF.net email is sponsored by: ObjectStore. >If flattening out C++ or Java code to make your application fit in=20 >a >relational database is painful, don't do it! Check out ObjectStore. >Now part of Progress Software. http://www.objectstore.net/sourceforge >_______________________________________________ >JBoss-user mailing list >JBo...@li... >https://lists.sourceforge.net/lists/listinfo/jboss-user > > ********************************************************************** This email and its attachments are intended for the above=20 named only and may be confidential. If they have come to=20 you in error, you must take no action based on them, nor=20 must you copy or show them to anyone; please reply to this=20 email and highlight the error. Security Warning: Please note that this email has been=20 created in the knowledge that the internet email is not a=20 100% secure communications medium. We advise that you=20 understand and observe this lack of security when emailing us. Viruses: Although we have taken steps to ensure that this=20 email and attachments are free from any virus, we advise=20 that in keeping with good computing practice the recipient=20 should ensure they are actually virus free. If you have received this email in error please notify: pos...@pi... ********************************************************************** |