[openjms-developer] [ openjms-Bugs-1491653 ] Failed to remove message error

[SourceForge.net]

Bugs item #1491653, was opened at 2006-05-19 07:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1491653&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: shellst (shellst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Failed to remove message error

Initial Comment:

Version: OpenJMS 0.7.7-alpha-3
Configured to use MySQL as the database vs Derby.
MySQL: 5.0.16-nt

Non-stop usage has produced the following error
messages, and leaves orphaned data in the messages
table. After 24 hours there are 10 orphaned rows in
the messages table.

Q1. Did these messages fail to get sent to client?
Q2. Any side effects beyond the orphaned entries in
the messages table?



03:59:38.928 ERROR [Scheduler-Worker-1] - Failed to
remove message
org.exolab.jms.persistence.PersistenceException:
java.sql.SQLException: Deadlock found when trying to
get lock; Try restarting tr
ansaction, message from server: "Lock wait timeout
exceeded; try restarting tra
nsaction"
at com.mysql.jdbc.MysqlIO.checkErrorPacket
(MysqlIO.java:1977)
at com.mysql.jdbc.MysqlIO.sendCommand
(MysqlIO.java:1163)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect
(MysqlIO.java:1272)
at com.mysql.jdbc.Connection.execSQL
(Connection.java:2236)
at
com.mysql.jdbc.PreparedStatement.executeUpdate
(PreparedStatement.java
:1741)
at
com.mysql.jdbc.PreparedStatement.executeUpdate
(PreparedStatement.java
:1588)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.ex
ecuteUpdate(Del
egatingPreparedStatement.java:101)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.ex
ecuteUpdate(Del
egatingPreparedStatement.java:101)
at org.exolab.jms.persistence.Messages.remove
(Messages.java:218)
at
org.exolab.jms.persistence.RDBMSAdapter.removeMessage
(RDBMSAdapter.ja
va:372)
at
org.exolab.jms.messagemgr.DefaultMessageCache.destroy
(DefaultMessageC
ache.java:196)
at
org.exolab.jms.messagemgr.CachedMessageRef.destroy
(CachedMessageRef.j
ava:119)
at
org.exolab.jms.messagemgr.AbstractMessageRef.dereferen
ce(AbstractMess
ageRef.java:130)
at
org.exolab.jms.messagemgr.AbstractMessageHandle.destro
y(AbstractMessa
geHandle.java:371)
at
org.exolab.jms.messagemgr.AbstractConsumerMessageHandl
e.destroy(Abstr
actConsumerMessageHandle.java:334)
at
org.exolab.jms.messagemgr.AbstractTopicConsumerEndpoin
t.doReceive(Abs
tractTopicConsumerEndpoint.java:410)
at
org.exolab.jms.messagemgr.AbstractConsumerEndpoint.rec
eive(AbstractCo
nsumerEndpoint.java:233)
at org.exolab.jms.server.SessionConsumer.send
(SessionConsumer.java:543)
at
org.exolab.jms.server.SessionConsumer.dispatch
(SessionConsumer.java:4
98)
at
org.exolab.jms.server.SessionConsumer.access$000
(SessionConsumer.java
:79)
at org.exolab.jms.server.SessionConsumer$1.run
(SessionConsumer.java:156)

at org.exolab.jms.scheduler.SerialTask.run
(SerialTask.java:164)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker
.run(Unknown So
urce)
at java.lang.Thread.run(Thread.java:595)



----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1491653&group_id=54559