]
Mark Little updated JBESB-846:
------------------------------
Component/s: Deployment
Assignee: Kurt Stam (was: Mark Little)
Exception when deploying to JBoss AS
-------------------------------------
Key: JBESB-846
URL:
http://jira.jboss.com/jira/browse/JBESB-846
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment
Reporter: Tom Cunningham
Assigned To: Kurt Stam
Fix For: 4.2
I get this error on startup in jboss-4.2.0.GA and on jboss-4.2.1.GA
12:24:55,422 INFO [JBoss4ESBDeployer] create esb service, jbossesb.esb
12:24:55,446 INFO [DeadMessageQueue] Bound to JNDI name: queue/DeadMessageQueue
12:24:56,322 INFO [J2eeConnectionManager] initializing...
12:24:56,426 ERROR [MessageRedeliverer] Could not obtain messages.
org.jboss.soa.esb.services.persistence.MessageStoreException: java.sql.SQLException:
Table not found in statement [select uuid, message from message]
at
org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.getAllMessages(DBMessageStoreImpl.java:271)
at
org.jboss.soa.esb.actions.MessageRedeliverer.process(MessageRedeliverer.java:72)
at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:264)
at
org.jboss.soa.esb.listeners.ScheduleListener.onSchedule(ScheduleListener.java:79)
at
org.jboss.soa.esb.schedule.ScheduleProvider$ESBScheduledJob.execute(ScheduleProvider.java:180)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: java.sql.SQLException: Table not found in statement [select uuid, message from
message]
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeQuery(Unknown Source)
at
org.jboss.resource.adapter.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:171)
at
org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.getAllMessages(DBMessageStoreImpl.java:258)
... 6 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: