« Return to Thread: Daisy Nightly Build 2.5 - sql exception with Daisy 2.1 data

RE: Daisy Nightly Build 2.5 - sql exception with Daisy 2.1 data

by Winslow, Andre - BLS :: Rate this Message:

| View in Thread

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thanks Paul, This corrected the issue. Thank you.

André

 

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Paul Focke
Sent: Wednesday, March 28, 2012 2:23 AM
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Daisy Nightly Build 2.5 - sql exception with Daisy 2.1 data

 

Hello André

 

Try dropping and recreating the activemq database. ActiveMQ will recreate all the necessary tables at statup

 

Paul

On Tue, Mar 27, 2012 at 9:55 PM, Winslow, Andre - BLS <Winslow.Andre@...> wrote:

I am attempting to start Daisy2.5 with my Daisy2.1 Mysql5.1.46 data. I attempted to start my Repository Server and I get this error:

 

Caused by: java.io.IOException: Failed to lookup subscriptions. Reason: java.sql.SQLException: Unknown column 'SUB_DEST' in 'field list'

Caused by: java.sql.SQLException: Unknown column 'SUB_DEST' in 'field list'

        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2928)

        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1571)

        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1666)

        at com.mysql.jdbc.Connection.execSQL(Connection.java:2994)

        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:936)

        at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030)

        at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:91)

        at org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doGetAllSubscriptions(DefaultJDBCAdapter.java:688)

        at org.apache.activemq.store.jdbc.JDBCTopicMessageStore.getAllSubscriptions(JDBCTopicMessageStore.java:322)

        ... 85 more

Startup failed. Will try to shutdown and exit.

[main] INFO  org.outerj.daisy.runtime.info - Shutting down component containers.

 

I have attempted to drop the table ACTIVEMQ_ACKS.

 

ALTER TABLE `ACTIVEMQ_ACKS` DROP `SUB_DEST`

 

… and then re-create it:

 

DROP TABLE IF EXISTS `ACTIVEMQ_ACKS`;

/*!40101 SET @saved_cs_client     = @@character_set_client */;

/*!40101 SET character_set_client = utf8 */;

CREATE TABLE `ACTIVEMQ_ACKS` (

  `CONTAINER` varchar(110) NOT NULL,

  `SUB_DEST` varchar(110) DEFAULT NULL,

  `CLIENT_ID` varchar(110) NOT NULL,

  `SUB_NAME` varchar(110) NOT NULL,

  `SELECTOR` varchar(110) DEFAULT NULL,

  `LAST_ACKED_ID` bigint(20) DEFAULT NULL,

  `PRIORITY` bigint(20) NOT NULL DEFAULT '5',

  PRIMARY KEY (`CONTAINER`,`CLIENT_ID`,`SUB_NAME`,`PRIORITY`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

/*!40101 SET character_set_client = @saved_cs_client */;

 

Same error.

 

Thanks,

André R. Winslow

BLS - OTSP,DOSP,DEWS

winslow.andre@...

 


_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

 


_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

 « Return to Thread: Daisy Nightly Build 2.5 - sql exception with Daisy 2.1 data