Hello,
i'm having problems with our activemq application in production environment.
the application core dumped several times during the last days when the
connection to the broker was lost. each time it was either caused by the
broker beeing restartet by our monitor/service application (noticing
instructions in the bottom of the page and patched
> AbstractRegion.java. It seems working fine now - at least I don't get this
> exception anymore.
>
> Hope it helps,
> Boris.
>
>
> pfid wrote:
>>
>> Hey cool, works ... kind of. I've removed all
> at
> org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:46)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201)
> at
> org.sp
I'm currently using a 4.1.1 broker with JAAS authentication, and it works
fine. Today i wanted to try out the 5.0.0. release version
(http://activemq.apache.org/activemq-500-release.html). The broker itself
will run out of the box without changing the original configuration files.
however i want t
I've had similar problems, and i found it was caused by an outdated tar
version, extracting some cpp files to *.cp instead of *.cpp, or *.h to *.
renaming the broken filenames fixed the problem for me.
Tim Bish wrote:
>
> Have you checked the src directory to see if that file was really
> ther
I'm having 2 problems with activemq-cpp-2.1.1 i just cant get rid off.
hopefully someone can help me out :) the broker i'm using is v4.1.1.
1) how does message redelivery work with the activemq-cpp-2.1.1 api?
according to
http://activemq.apache.org/message-redelivery-and-dlq-handling.html i need
I'm having problems with my client application, not beeing able to
send/receive messages (queue blocked) after a certain amount of messages
have been send (DeliveryMode::PERSISTENT, Session::CLIENT_ACKNOWLEDGE - all
messages get acknowledged upon receiving). Also, there seems to be problems
with m
ssue
> http://issues.apache.org/activemq/browse/AMQCPP and attach and example
> application that illustrates the problem.
>
> Nate
>
>> -Original Message-
>> From: pfid [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, November 13, 2007 8:41 AM
>> To: users@activemq.apach
tabish121 wrote:
>
> Please upgrade to ActiveMQ-CPP 2.1.1 as this sounds like an error that
> we fixed. Then let us know if it still misbehaves.
>
> Regards
> Tim
>
Still doesnt work.
I should mention though, that my test client uses 2 activemq queues at the
moment. The first one can be clos
I'm using ActiveMQ-CPP 2.1 in my client application, and the broker version
4.1.1.
in case the client loses its connection to the activemq broker, i want it to
close all activemq queue connections, and try to reopen them if possible.
i simulate this behaviour by stopping the broker via ctrl+c wh
James.Strachan wrote:
>
> On 23/09/2007, mythz <[EMAIL PROTECTED]> wrote:
>>
>> How can I check that the broker I'm listening on is still running?
>>
>> I have a master slave setup where if master broker goes down one of the
>> slaves takes over. The problem is that the listener does not reconn
i'm using a 4.1.1 broker, and cms-2.1.1 clients as consumers/producers,
working with queues, CLIENT_ACK mode.
i noticed some strange behaviour when the consumer is offline while the
producer sends. for testpurpose i have the producer send 300 messages to
some queue. i then start the consumer and
12 matches
Mail list logo
