Re: Do changes to activemq.xml require a broker restart?

On Fri, 2010-01-15 at 16:18 -0800, yello_downunder wrote: > Hi, > > Do changes to activemq.xml require a broker restart before they take effect? > Is this documented somewhere in the ActiveMQ docs? Yes, when you make changes to the xml config file you need to restart the broker, the broker doesn

Do changes to activemq.xml require a broker restart?

Hi, Do changes to activemq.xml require a broker restart before they take effect? Is this documented somewhere in the ActiveMQ docs? Jerry Seutter -- View this message in context: http://old.nabble.com/Do-changes-to-activemq.xml-require-a-broker-restart--tp27185449p27185449.html Sent from the

Re: Could not connect to broker URL: tcp remote connection failure

instead of defining tcp://localhost:port in your broker config - try tcp://0.0.0.0:port On 15 Jan 2010, at 22:43, quinn wrote: I am using ActiveMQ 5.3 and JDK 1.6. I have a XP box and an Ubuntu box. On either machine I can start an embedded broker and the vm and tcp transports work well o

Could not connect to broker URL: tcp remote connection failure

I am using ActiveMQ 5.3 and JDK 1.6. I have a XP box and an Ubuntu box. On either machine I can start an embedded broker and the vm and tcp transports work well on one machine. When I try to access the tcp transport from a remote machine I am unable to connect. The stack trace is attached. http:

Re: Problems with prefetch and TemporaryQueues

I have now registered this as a Jira issue along with a JUnit test case: http://issues.apache.org/activemq/browse/AMQ-2571 I added another observation. "When the TempQueue is auto(re)created it is not removed when the server closes its connection as one (or at least I) would expect. Also, the ser

[ANNOUNCE] Apache.NMS.Stomp v1.2.0-RC1 Released

* ANNOUNCEMENT * The Apache.NMS.Stomp 1.2.0 Release Candidate 1 is now available at the following location: This is the first release of the NMS Stomp client. Its being released as v1.2.0 to keep in step with the NMS API ve

Re: Non-persistent queue, asyncSend

I am not comparing the throughput of non-persistent messages with persistent messages that have asyncSend. I am just pointing out that your throughput for sending persistent messages will improve if you send the persistent messages with asyncSend. Question is, what is the risk-level of sending per

Re: Non-persistent queue, asyncSend

Much appreciated Joe. Let me get this straight: higher throughput with persistent messaging + asyncSend vs. non-persistent messaging? It wouldn't be the same throughput? Joe Fernandez wrote: > > Non-persistent messages are, by default, sent asynchronously (a.k.a., fire > and forget). > > Ye

Re: How to avoid "Slow KahaDB access: cleanup took 545" error msg?

I am also seeing these. I understand that you can set a thrreshold to stop it logging, but it seems that things slow down or stall while KahaDB performs an index. Ie- consumers of this broker are blocked waiting for the index to complete. This happens when my message store grows to several thousa

Re: Non-persistent queue, asyncSend

Non-persistent messages are, by default, sent asynchronously (a.k.a., fire and forget). Yes, if you send persistent messages with asyncSend, you will realize a nice boost in throughput. Joe http://www.ttmsolutions.com jongraf wrote: > > Two questions: > 1) Is asyncSend set to true by defaul

Re: [ANNOUNCE] Apache.NMS API 1.2.0 Released

Just a very small detail, as the release has been announced, we should update the corresponding wiki pages: http://activemq.apache.org/nms/activemq-net-120-release.html (still marked as *The Release is still in progress)* Seems a lot of improvments have been done, lets work hard on the next releas

Non-persistent queue, asyncSend

Two questions: 1) Is asyncSend set to true by default if I am using non-persistent messaging? The line of code where this is determined is ActiveMQSession line 1670, 1680: if (sendTimeout <= 0 && !msg.isResponseRequired() && !connection.isAlwaysSyncSend() && (!msg.isPersistent() ||

[ANNOUNCE] Apache.NMS API 1.2.0 Released

The Apache NMS team is pleased to announce the release of Apache NMS API 1.2.0. This version of the API will be the basis for the next set of NMS client releases including Apache.NMS.ActiveMQ and Apache.NMS.Stomp. Changes in this version include * Addition of ConnectionMeteData to the Connectio

Re: Handle leaks using CMS-3.1

On Fri, 2010-01-15 at 00:32 -0800, diedie wrote: > Hi, > > I recently upgraded my cms library from 3.0 to 3.1(built using vs-2005), > and face some issues that handle leaks when reconnecting to server. > > So I wrote a simple testing program based on vs2005-activemq-example, > and found that it

Re: why is activeMQ stalled?

Le 15/01/10 11:50, Rob Davies a écrit : > David - can you upgrade 5.3 ? Not immediatly, but worth a try > > On 15 Jan 2010, at 10:40, David Delbecq wrote: > >> Le 15/01/10 11:25, Gary Tully a écrit : >>> A thread dump of the broker jvm, when the clients are stalled, would >>> help >>> diagnose what

Re: why is activeMQ stalled?

David - can you upgrade 5.3 ? On 15 Jan 2010, at 10:40, David Delbecq wrote: Le 15/01/10 11:25, Gary Tully a écrit : A thread dump of the broker jvm, when the clients are stalled, would help diagnose what is going on. btw, what activemq version are you using? BrokerService

Re: why is activeMQ stalled?

Le 15/01/10 11:25, Gary Tully a écrit : > A thread dump of the broker jvm, when the clients are stalled, would help > diagnose what is going on. btw, what activemq version are you using? > BrokerService - ActiveMQ 5.2.0 JMS Message Broker (localhost) is starting I'll come back

Re: why is activeMQ stalled?

A thread dump of the broker jvm, when the clients are stalled, would help diagnose what is going on. btw, what activemq version are you using? 2010/1/15 David Delbecq > Le 15/01/10 10:24, Dejan Bosanac a écrit : > > Hi David, > > > > you're probably blocked by "producer flow control". Take a loo

Re: why is activeMQ stalled?

Le 15/01/10 10:24, Dejan Bosanac a écrit : > Hi David, > > you're probably blocked by "producer flow control". Take a look here > for more info: http://activemq.apache.org/producer-flow-control.html > > Cheers I already took a look at it, read it three time to be sure i understand. It's quite tech

Re: why is activeMQ stalled?

Hi David, you're probably blocked by "producer flow control". Take a look here for more info: http://activemq.apache.org/producer-flow-control.html Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/sny

why is activeMQ stalled?

Hello, can someone explain me why my activeMQ client is stalled in such situation (i have 10 threads blocked like this having as consequence a complete blocking of my client application): "http-8081-Processor6" daemon prio=10 tid=00841c38 nid=512 lwp_id=2426611 waiting on condition [236f3000.

Handle leaks using CMS-3.1

Hi, I recently upgraded my cms library from 3.0 to 3.1(built using vs-2005), and face some issues that handle leaks when reconnecting to server. So I wrote a simple testing program based on vs2005-activemq-example, and found that it occurs even I just create the connection and close it. Has an