So debugging through the app and running the sql statement through isql the problem turns out to be our database default columns to Not Null while the activemq statement assume columns default to Allow Null. Also, it seems there is a mismatch is case for the TIME/time column for when the column is created (TIME) and when it is used (time). Defining my own ddl statement to create the tables fixed the problem
CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARCHAR(250), MSGID_PROD VARCHAR(250), MSGID_SEQ INTEGER, EXPIRATION DECIMAL, MSG IMAGE, PRIMARY KEY ( ID ) ) go CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS (MSGID_PROD,MSGID_SEQ) go CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER) go CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION) go CREATE TABLE ACTIVEMQ_ACKS(CONTAINER VARCHAR(250) NOT NULL, SUB_DEST VARCHAR(250), CLIENT_ID VARCHAR(250) NOT NULL, SUB_NAME VARCHAR(250) NOT NULL, SELECTOR VARCHAR(250), LAST_ACKED_ID INTEGER, PRIMARY KEY ( CONTAINER, CLIENT_ID, SUB_NAME)) go --the default activemq create statements assume columns default to allow null, our default to not null --the 'TIME' column seems to be unexpected case sensitive so 'time' is used instead CREATE TABLE ACTIVEMQ_LOCK( ID DECIMAL NOT NULL, time DECIMAL NULL, BROKER_NAME VARCHAR(250) NULL, PRIMARY KEY (ID) ) go INSERT INTO ACTIVEMQ_LOCK(ID) VALUES (1) go -- View this message in context: http://www.nabble.com/Invalid-column-name-%27time%27-when-using-Sybase-XA-tp17872586p17874705.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
