2 Replies Latest reply on Mar 24, 2006 1:20 PM by gqsmooth

    MSException: Could not store message:

    gqsmooth

      We are trying to convert an application from using the Hypersonic DB to SQL Server. During some simple testing, we are getting this error message when writing to the JMS_MESSAGES table:

      (org.jboss.mq.SpyJMSException: Could not store message: 5 m
      sg=4 hard NOT_STORED PERSISTENT queue=QUEUE.scheduleQueue priority=4 lateClone=false hashCode=843963; - nested throwable: (java.sql.SQLException: [Microsoft]
      [SQLServer 2000 Driver for JDBC]Unable to determine the type of the specified object.))
      at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:459)
      at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186)
      at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:182)
      at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:438)
      at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186)
      at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:166)
      at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:362)
      at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
      at java.lang.Thread.run(Thread.java:534)

      The JMS_MESSAGES schema looks like this:

      CREATE TABLE JMS_MESSAGES (
      MESSAGEID int NOT NULL ,
      DESTINATION varchar (255) NULL,
      TXID int NULL,
      TXOP char (1) NULL ,
      MESSAGEBLOB image NULL
      )
      GO

      CREATE UNIQUE INDEX JMS_MESSAGES_IDX ON dbo.JMS_MESSAGES(MESSAGEID, DESTINATION)
      GO

      CREATE INDEX JMS_MESSAGES_TXOP_TXID ON dbo.JMS_MESSAGES(TXOP, TXID)
      GO

      CREATE INDEX JMS_MESSAGES_DESTINATION ON dbo.JMS_MESSAGES(DESTINATION)
      GO

      We are using JBoss version 4.0.1SP1 on Windows 2000 EE SP1. We also tried this using Microsoft JDBC 1.2.2 SP1 and SP3 with no difference.

      Any help would be appreciated!