Hi,
I'm using ActiveMQ 5.8.0 on RHEL 6.1.
Any troubleshooting tips folks can share as to what might be causing
this exception to show up in my broker's log? Note the miss-speeling
of 'cylce' in the exception.
I was unable to get the broker to launch after this point despite
numerous restarts. In
Hi,
I'm using ActiveMQ 5.8.0 on RHEL 6.1
I have noticed the following exception appearing in my broker's log
file. It appears to be related to the once hourly check for expired
messages, as these occur at _exactly_ the same time past the hour, as
given by the expireMessagesPeriod attribute on our
On 09/26/2013 10:16 AM, moodycl wrote:
I think I have found the problem. In ClassLoadingAwareObjectInputStream.java
the load() method makes a call to Class.forName().
For the primitive types (int, boolean, etc.) this would result in a call
similar to:
Class.forName("int", false, loader); /
check the cache level. The consumer (where amq does redelivery) is
probably closed after each receipt, so the broker just does a
redispatch to one of the other available consumers.
The broker redelivery plugin can help but the root cause is session
level transaction enlistment which is done on sess
Any solution or suggestion to this problem?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Getting-ActiveMQObjectMessage-instead-of-TextMessage-tp4671877p4671977.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 09/30/2013 02:01 AM, HellKnight wrote:
I have upload my unit test project in a rar file , but it is not accepted by
the mailing list up until now.Can you download it or I have to send it to
you mailbox ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Individual-Ackn
