My JMS java client creates one consumer with a message selector and works
fine when receiving messages from WebSphere MQ. But seldom works when
receiving from a queue on ActiveMQ 5.3.1 and 5.4.1. Most of the time I
don't get any messages. I can consistently get it to work *IF* I am
stepping th
A couple of questions about threading model. First, it seems like (on the
client-side) there's a thread created per session. Is this true?
Second, it seems like a session is required per thread. Is that true as
well?
What I'm trying to accomplish is to implement a long-polling http service.
Hi Jeff. That's great news. I'm not very Java-savvy, but I've made a few
patches to the activemq ajax code in the past. I've spent a bit of time lately
trying to get junit test cases working for testing MessageListenerServlet, so I
haven't actually made much progress in solving the issue at h
hmmm, just had a peek at the memory topic store, and it uses an lru
cache for the message map with a limit of 100, so it is not ideal for
your use case. But you should see some messages with that impl.
Extending the memory store to change that is one option.
On 14 December 2010 16:18, Aleksandar I
Just committed a fix, you should be able to verify with tonights 5.5 snapshot
On 14 December 2010 10:40, develop wrote:
> Hi guys,
>
> is there any progress on jira task AMQ-2852?
>
> I am using 5.4.2 embedded broker + spring 3.0.5 + tomcat 7 and cannot find a
> way to gracefully stop the applica
Hi Alex,
Thanks for the response. We looked into it a bit more based on your
suggestion, and we discovered that there is an error occurring when the
continuation is resumed in onMessageAvailable in AjaxListener.java. It
looks like this onMessageAvailable handler is being called every time a new
Not really. Just tested on 5.4.1-fuse and messages are gone with the
wind ;)
Gary Tully
writes:
> with the caveat that there is no durability of the message. But yes,
> when a durable sub is offline, the persistent messages will be held in
> memory.
>
> On 14 December 2010 15:38, Aleksandar Iva
with the caveat that there is no durability of the message. But yes,
when a durable sub is offline, the persistent messages will be held in
memory.
On 14 December 2010 15:38, Aleksandar Ivanisevic
wrote:
> Gary Tully
> writes:
>
>> if you set persistent=false on BrokerService, (broker in xml con
It seems like there may be a JIRA open on this (my concern about the broker
hanging on startup if it cannot connect).
https://issues.apache.org/jira/browse/AMQ-2114
I'd still like to know how other people handle this situation, even if it
requires a heroic coding intervention.
--
View this mes
I was using the failover transport to supply multiple URIs, but I didn't
realize how configurable it was. The various parameters used to configure
how many reconnect attempts are made and the delay between those attempts
are very helpful.
The remaining question I have, though, it what is the bro
Gary Tully
writes:
> if you set persistent=false on BrokerService, (broker in xml config)
> it will use an in memory store.
And durable topics will keep working as they should?
>
> On 14 December 2010 10:01, Aleksandar Ivanisevic
> wrote:
>> Gary Tully
>> writes:
>>
>>> Non persistent message
I cannot see any references to an upgrade procedure for AMQ...
I can manually rsync -zarul --delete [bin/|lib/|webapps]
/opt/activemq/[bin/|lib/|webapps] but that seems rather haphazard. I've got
several servers to do this across possibly tomorrow evening.
So am I missing something or does it sim
Here is the gc.log and activemq logs, once again taken from a run where I
allowed it to process, block and then continue processing:
http://activemq.2283324.n4.nabble.com/file/n3087092/logs_verbose_gc.rar
logs_verbose_gc.rar
--
View this message in context:
http://activemq.2283324.n4.nabble.c
if you set persistent=false on BrokerService, (broker in xml config)
it will use an in memory store.
On 14 December 2010 10:01, Aleksandar Ivanisevic
wrote:
> Gary Tully
> writes:
>
>> Non persistent messages can be sent to a durable sub, but the durable
>> sub will only get the messages if it c
Hi,
There is no GC activity logs in the file you sent. How did you enable
verbose GC logging?
Try to use the following parameters:
-verbose:gc -XX:+PrintGC -XX:+PrintGCTimeStamps -Xloggc:gc.log
It will store all GC related logs in the gc.log file, more convenient
for analysis.
Regards,
Reynald
In order to try to work out just what is happening during these blocking
periods, I have used visual vm to perform cpu profiling, take a heapdump and
a thread dump when the broker becomes unresponsive. Here are the results:
http://activemq.2283324.n4.nabble.com/file/n3086836/visual_vm_analysis_du
Here is the activemq logs from a test run where I allowed it to begin
processing, block once and waited for it to resume processing, where I have
turned on verbose garbage collection output:
http://activemq.2283324.n4.nabble.com/file/n3086805/logs_with_verbose_gc.rar
logs_with_verbose_gc.rar
--
Hi guys,
is there any progress on jira task AMQ-2852?
I am using 5.4.2 embedded broker + spring 3.0.5 + tomcat 7 and cannot
find a way to gracefully stop the application without having leaks.
Thanks.
-simeon
I have left the test application running over night, it is still consuming
and producing messages but is blocking very often now (every 15-20 seconds
for around 10 seconds each time).
I used visualVM to analyse the garbage collection, which seems to be running
around once every two minutes or so
Hi,
did you check failover transport
http://activemq.apache.org/failover-transport-reference.html
Cheers
--
Dejan Bosanac
-
FuseSource - The experts in open source integration and messaging.
Email: dej...@fusesource.com
Web: http://fusesource.com
Twitter: http://twitter.com/deja
Gary Tully
writes:
> Non persistent messages can be sent to a durable sub, but the durable
> sub will only get the messages if it connected, a backlog will not be
> retained as the messages will not be stored
> It will behave like a regular topic subscription in this regard.
Thanks, thats what
Non persistent messages can be sent to a durable sub, but the durable
sub will only get the messages if it connected, a backlog will not be
retained as the messages will not be stored
It will behave like a regular topic subscription in this regard.
On 14 December 2010 09:13, Aleksandar Ivanisevic
FWIW, I've nailed down my problem, it was a heavy I/O process running
on the host node, sucking out all the I/O from the broker that was
running in a (somewhat misconfigured) VM.
That being said, is it possible to have a "diskless" broker and still
have persistence?
All my messages are persisten
23 matches
Mail list logo
