Client problem recovering from a restart of a broker

2008-12-08 Thread amiko
Hi We're using activemq 5.1.0, the client connects to the broker using failover: new ActiveMQConnectionFactory( "failover:" + brokerUri ); The problem is that after the brokers restart there seems to be a problem with the reconnect of the client (Received unexpected response for command id ...)

Re: duplicate message problem on ActiveMQ5.2.0

2008-12-08 Thread Leon Liu
Hi gary, The fix can migrate to version 5.2.0? I think it is a critical bug. Leon Liu Gary Tully 写道: > Leon, > can you try a recent snapshot[1], I think your issue may be another > variant of https://issues.apache.org/activemq/browse/AMQ-2020 which I > fixed last week. > > [1] > http://people.apa

Re: [ANNOUNCE] Apache ActiveMQ 5.2.0 Released

2008-12-08 Thread Willem Jiang
Hi There is no any news about the ActiveMQ 5.2.0 release in [1][2]. But I saw you updated the news in the confluence page. Maybe we need export the static page files from confluence. [1]http://cwiki.apache.org/ACTIVEMQ/ [2]http://activemq.apache.org/ Willem Gary Tully wrote: > The Apache Active

Re: Admin Web Console not showing messages in queue.

2008-12-08 Thread JeanNiBee
Okay so what I'm gleaming from my reading is that I have a VM configured broker so it runs inside my Java process (In Spring / Tomcat). This is actually preferable to installing a service/binary and connecting to that as I originally thought I was doing. (As it's more portable) The 'out of the bo

RE: Broker not releasing memory

2008-12-08 Thread Frugia, Kirby A
5.1.0. I believe it's happening with 5.2.0, too, but have not thoroughly tested. The problem is that the broker runs out of memory. At the point in time of the failure, no more messages could be sent anyway because the broker is out of memory. So we're less worried about blocking producers a

Re: Broker not releasing memory

2008-12-08 Thread Bruce Snyder
On Mon, Dec 8, 2008 at 7:28 AM, Frugia, Kirby A <[EMAIL PROTECTED]> wrote: > I can reproduce this with the non-embedded, out-of-the-box broker. I also > think it's an under-the-hood problem. > > Until we get a fix, we've set pending message queue limits on our busy > topics. So, for example, th

Re: Interfacing with legacy Websphere MQ clients

2008-12-08 Thread James Strachan
2008/12/4 James Strachan <[EMAIL PROTECTED]>: > 2008/12/4 Stephen J <[EMAIL PROTECTED]>: >> >> If I try with camel I receive the following error: >> >> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to >> resolve endpoint: mqtestserver://TEST.OUTBOUND?targetClient=1 due to: Ther

Re: Admin Web Console not showing messages in queue.

2008-12-08 Thread JeanNiBee
Hi I guess I am really misunderstanding the use of the technology then. If I have a queue called "jbtesting" on a ActiveMQ instance (the only 1 I have setup anywhere) and my webapp is connecting to localhost and posting messages into jbtesting, as illustrated by my Spring config files sent in or

Re: Admin Web Console not showing messages in queue.

2008-12-08 Thread Dejan Bosanac
Hi, the web console is not automatically integrated in your application when you embed the broker. You need to embed Jetty (or some other servlet container) as well and deploy web console app Take a look at the default conf/activemq.xml and webapps/admin folder to find out how things are done in

Re: Admin Web Console not showing messages in queue.

2008-12-08 Thread JeanNiBee
I guess this will be a case of "RTFM" for me. ;) I just was looking at the Web Console that is provided from the default 'getting started' so I didn't really configure anything other than click the link in the doc. Pointer to any info to help me understand this would be great. (As is the ActiveM

RE: Broker not releasing memory

2008-12-08 Thread Frugia, Kirby A
I can reproduce this with the non-embedded, out-of-the-box broker. I also think it's an under-the-hood problem. Until we get a fix, we've set pending message queue limits on our busy topics. So, for example, the broker will only queue up 500 messages on a particular topic per consumer. This

Re: Urgent: ActiveMQ CMS multi handlers?

2008-12-08 Thread Timothy Bish
On Sun, 2008-12-07 at 22:59 -0800, prasha8 wrote: > Have been working on a pilot project to use ActiveMQ as core message provider > for a legacy system (which is C++ based) > > One of the critical requirement is to figure out the best approach to solve > following problem > 1. I have ESB convertin

Re: Spring + embedded ActiveMQ Broker

2008-12-08 Thread Dejan Bosanac
Hi, I don't see anything wrong with your configuration. You just might consider adding depend-on for connection factory bean or the follwing URL vm://localhost?create=false&waitForStart=1 (if you use 5.2.0) to ensure your broker starts before the connection factory. Take a look at this link fo

Re: Admin Web Console not showing messages in queue.

2008-12-08 Thread Dejan Bosanac
Hi, I can't see fro you example how you initialize your web console. Are you sure it points to the right broker? Cheers -- Dejan Bosanac http://www.ttmsolutions.com - get a free ActiveMQ user guide ActiveMQ in Action - http://www.manning.com/snyder/ Scripting in Java - http://www.scriptingin

Re: duplicate message problem on ActiveMQ5.2.0

2008-12-08 Thread Gary Tully
Leon, can you try a recent snapshot[1], I think your issue may be another variant of https://issues.apache.org/activemq/browse/AMQ-2020 which I fixed last week. [1] http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/apache-activemq/5.3-SNAPSHOT/ 2008/12/8 Leon Liu <[EMAIL P

Moving a message to DLQ after the TTL has expired

2008-12-08 Thread Gert Vanthienen
L.S., Is it possible to move a message to the DLQ after the TTL has expired? When using ActiveMQ queues for communicating between applications, it would be nice to know if a message consumer somewhere has died by attaching a consumer to the DLQ for 'catching' the errors. Regards, Gert -

Re: Broker not releasing memory

2008-12-08 Thread Will van der Leij
I use an embedded broker too and have gone through all the possible iterations of config options for threading, acknowledgements and message storage. Alas, an apparent "memory leak" still persists with slow consumers that close/die with messages still in-flight/pending. I've had several other pe