that problem with the class cast exception was fixed today - might be
worth looking tomorrow
On 9 Jul 2008, at 14:07, Marjan wrote:
I tried the 5.2 SNAPSHOT. By the way, spring-aop.jar is missing from
the
distribution. I added it by myself. With this version the things are
even
worse. If some message expires, the consumer can't read and the
producer
can't produce messages. This is the stack trace on the server:
ERROR Queue - Failed to page in more queue
messages
java.lang.ClassCastException:
org.apache.activemq.command.ActiveMQObjectMessage
at
org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:104
5)
at
org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:103
7)
at
org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1117)
at
org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:119
6)
at org.apache.activemq.broker.region.Queue.iterate(Queue.java:
951)
at
org.apache.activemq.thread.DeterministicTaskRunner.runTask(Determinis
ticTaskRunner.java:84)
at
org.apache.activemq.thread.DeterministicTaskRunner$1.run(Deterministi
cTaskRunner.java:41)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:675)
at java.lang.Thread.run(Thread.java:595)
ERROR Queue - Failed to page in more queue
messages
java.lang.ClassCastException:
org.apache.activemq.command.ActiveMQObjectMessage
at
org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:104
5)
at
org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:103
7)
at
org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1117)
at
org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:119
6)
at org.apache.activemq.broker.region.Queue.iterate(Queue.java:
951)
at
org.apache.activemq.thread.DeterministicTaskRunner.runTask(Determinis
ticTaskRunner.java:84)
at
org.apache.activemq.thread.DeterministicTaskRunner$1.run(Deterministi
cTaskRunner.java:41)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:675)
at java.lang.Thread.run(Thread.java:595)
ERROR Queue - Failed to page in more queue
messages
java.lang.ClassCastException:
org.apache.activemq.command.ActiveMQObjectMessage
at
org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:104
5)
at
org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:103
7)
at
org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1117)
at
org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:119
6)
at org.apache.activemq.broker.region.Queue.iterate(Queue.java:
951)
at
org.apache.activemq.thread.DeterministicTaskRunner.runTask(Determinis
ticTaskRunner.java:84)
at
org.apache.activemq.thread.DeterministicTaskRunner$1.run(Deterministi
cTaskRunner.java:41)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:675)
at java.lang.Thread.run(Thread.java:595)
Can we expect that this will be fixed in the near future? It is not
trivial
and message expiration mechanism is one of the basic JMS principles.
Regards
--
View this message in context:
http://www.nabble.com/ActiveMQ-message-delivery-tp18355245p18361191.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
