If you have just hacked, er, modified the standard jbossmq-service.xml file, then the "CREATE_MESSAGE_TABLE" string will be wrong for Oracle, and this will yield the "invalid column type" exception that you are seeing below. There's an example of an Oracle jbossmq-service.xml in CVS (messaging/src/etc/server/examples/deploy/oracle-jbossmq-service.xml) which looks OK to me.
Steve Coy
On Saturday, February 15, 2003, at 10:20 PM, Marek Lange wrote:
Hi,
I just can't get the JBossMQ persistence manager to work with an Oracle8 data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are successfully created (using BLOB_TYPE=BLOB and the sql statement
CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \
DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) )
from jbossmq-service.xml.
When a message should be inserted, it fails throwing this SQL Exception:
An exception occured while sending message to the jms queue: org.jboss.mq.SpyJMSException: Could not store message: 4 msg=1 hard NOT_STORED PERSISTENT queue=QUEUE.smsMessageQueue priority=4 hashCode=11632138; - nested throwable: (java.sql.SQLException: invalid column type)
I think the problem is related to the oracle BLOB type. Is there a solution for this?
Thanks,
-marek
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
