Hi,
well I tried this in the past too :-(. But upgrading was the only successful
solution.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-1-weird-behaviour-tp4312895p4333256.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
olution.
Phi-Long
-Message d'origine-
De : Zagan [mailto:erbsen.fr...@gmail.com]
Envoyé : lundi 23 janvier 2012 08:48
À : users@activemq.apache.org
Objet : RE: ActiveMQ 5.4.1: weird behaviour
Hi, migrate to Active MQ 5.5.1, install SUN Java JDK 1.6.0.18+ if possible and
try it agai
Hi, migrate to Active MQ 5.5.1, install SUN Java JDK 1.6.0.18+ if possible
and try it again. If you face the same problems again I recommend you to
contact someone from Fusesource.com support.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-1-weird-behaviou
nvoyé : vendredi 20 janvier 2012 12:06
À : users@activemq.apache.org
Objet : Re: ActiveMQ 5.4.1: weird behaviour
I have not looked into that in detail, but I recall it is related to reaching
the journal max and rolling over. It seems the checkpoint is not smart enough
to deal with that case.
D
I have not looked into that in detail, but I recall it is related to
reaching the journal max and rolling over. It seems the checkpoint is
not smart enough to deal with that case.
Do all subsequent checkpoints fail? It may be that the only down side
is potential slow recovery or do you see other s
Chaps,
I've read lots of things on the web but no solutions at all about an error
message from activeMQ. The following error message occurs lots of time
My configuration: AIX 5.3 / IBM jvm 1.6.0 SR9
Stacktrace from active MQ:
2012-01-20 11:34:34,687 | ERROR | Failed to mark the Journal:
org.a
