>>> The reason is that the ActiveMQConsumer object is crashing during its
>>> destruction.
>>>
>>Stack traces and sample code that reproduces the issue are needed before
>>any help here, this could result from a number of different scenarios.
>
> I am in the process of creating a standalone example
*We are running ActiveMQ in JDBC master slave mode. A few days back we
observed the following log entries in the master log files:*
The connection to '/:' is taking a long time to shutdown. |
org.apache.activemq.broker.TransportConnection | ActiveMQ Task
.
.
.
ERROR | Could not accept connection
[Posting again as my previous post did not get requiredd help]
Hi All,
I am facing a very strange problem with ActiveMQ.
I have a java class that attaches itself to a queue. This class holds a
threadExecutor and once it gets a message, it uses the threadexecutor to run
a task with just arrived
Denis Baudin writes:
> Hello,
>
> I'm running ActiveMQ 1.5 on BEA Weblogic 8.1 and I ran into a
> classloader issue
> (...)
> The solution was to create an anonymous class which extended
> ObjectInputStream (call it from getObject) inside ActiveMQObjectMessage
> and get the contextclassloader
>
On Wed, 21 Sep 2011 08:23:40 -0400, Timothy Bish
wrote:
>On Wed, 2011-09-21 at 12:17 +0100, spam trap wrote:
>> I am writing a C++ application using the ActiveMQ CPP API. I have
>> based my code on the example in
>> http://activemq.apache.org/cms/example.html
>>
>> However I have moved the crea
On Wed, 2011-09-21 at 12:17 +0100, spam trap wrote:
> I am writing a C++ application using the ActiveMQ CPP API. I have
> based my code on the example in
> http://activemq.apache.org/cms/example.html
>
> However I have moved the creation of the Session, Destination and
> Consumer objects of the C
I'm running ActiveMQ 5.5.0 as a spring webapp rather than the standalone
version. Would you recommend the standalone one? Not sure how to use camel with
that though.
there's quite a high rate of packet loss on the network it seems and according
to this:
http://activemq.apache.org/async-sends.ht
What is the exact broker version used on your side?
In case its not the latest released version, can you try the latest version?
Do you set any particular headers on the Topic message in your producer?
On Sep 21, 2011, at 1:54 PM, Alistair Young wrote:
> I can't explain this at all. It's almo
I can't explain this at all. It's almost like the opposite of reliable
messaging. At times, almost 1 in 3 messages just disappears. No errors. The
KahaDB/db-*.log show no record of the message every arriving and yet the
producer doesn't get an error.
Alistair
--
mov eax,1
mov ebx,0
int 80h
yep, there is a durable topic consumer waiting for them
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 21 Sep 2011, at 12:20, Gary Tully wrote:
> topic messages are only persisted to the store if there are durable
> consumers/subscriptions
>
> On 21 September 2011 11:04, Alistair Young wrote
topic messages are only persisted to the store if there are durable
consumers/subscriptions
On 21 September 2011 11:04, Alistair Young wrote:
> I should say, the messages go to a topic on the broker and are then routed by
> camel to another topc. Would camel be dropping the messages? Would they
I am writing a C++ application using the ActiveMQ CPP API. I have
based my code on the example in
http://activemq.apache.org/cms/example.html
However I have moved the creation of the Session, Destination and
Consumer objects of the Consumer class to the constructor. I
understand that some of the
I should say, the messages go to a topic on the broker and are then routed by
camel to another topc. Would camel be dropping the messages? Would they not be
logged in the kahadb store no matter what though?
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 21 Sep 2011, at 10:25, Alistair Young w
I doubt it. In a batch of three messages sent in 2 seconds, one disappeard. Is
there a default throttle limit perhaps on the broker? But surely that would
cause the producer to error out or something?
Alistair Young
Àrd-Innleadair air Bathar-Bog
UHI@Sabhal Mò
Any chance you can reproduce this behavior in a little JUnit test case?
On Sep 21, 2011, at 10:15 AM, Alistair Young wrote:
>> There was no producer, broker or connection crash while the msg was in
>> transit?
> no, the logs show it was up and sending
>
>> The msg does not have an expiration
> There was no producer, broker or connection crash while the msg was in
> transit?
no, the logs show it was up and sending
> The msg does not have an expiration time?
no
> Are you certain that no consumer has got the msg already?
yes, there's no record of it arriving at the consumer and no lo
16 matches
Mail list logo