ActiveMQ Admin or commandline-jmx to configure memoryLimit at run time

2011-11-18 Thread mrdiesel
Hello, I m trying to configure memory limit at run time to be able to throttle my producers. Using jconsole and jmx I m able to change *MemoryLimit* (which is highlighted in blue) and throttle the producers. But i want to be able to do this at run time, without having to restart the server. I t

Message groups interleaving

2011-11-18 Thread SergueiM
Hi, Having multiple message groups producers and multiple async consumers, would it be correct to anticipate that a single consumer may get the messages received being interleaved from different groups of messages? Example: - msg producer P1 sends a group of 2 msgs: P1.1 and P1.2, while at the sa

Live Broker and KahaDB on NFS4

2011-11-18 Thread Jeremy Deane
What are the implications to a live broker where the mount point containing the KahaDB fails? And what is the recommended process to recover from such a failure? -- View this message in context: http://activemq.2283324.n4.nabble.com/Live-Broker-and-KahaDB-on-NFS4-tp4083655p4083655.html Sent from

JMSException: The resource is allready being used in transaction context.

2011-11-18 Thread Mihai Osian
Hello, I get the exception from the subject when running a very simple test application deployed in Glassfish, if there are multiple JMS connections created in parallel. . The issue has been encountered before by other users: http://activemq.2283324.n4.nabble.com/Suspect-a-race-condition-

Re: AMQ does not respect the message priority order completely?

2011-11-18 Thread Gary Tully
not so, the message store read is also ordered, so the batch is read in priority order. there was a recent fix for non persistent messages with the file pending message cursor so you may be experiencing that. 2011/11/18 SuoNayi : > Hi all, I'm  not sure this is correct or not. > In order to respec

Re: Connection timeout 20 sec

2011-11-18 Thread Timothy Bish
On Thu, 2011-11-17 at 22:29 -0800, Ishitori wrote: > It seems I found the problem. It was a well-known problem of .NET: Connect() > method of the socket class doesn't have timeout property. > http://www.codeproject.com/KB/IP/TimeOutSocket.aspx And it takes from 20 to > 30 seconds for .NET to unders

Re: [HELP] IllegalStateException: Not supported with Tomcat 7.0.22 and AjaxServlet

2011-11-18 Thread Dejan Bosanac
Hi, this has something to do with continuation support in Tomcat 7 and how ti handles Jetty call. Frankly, I'm surprised ti works in Tomcat 6 at all. Regards -- Dejan Bosanac - http://twitter.com/dejanb - The experts in open source integration and messaging - http://fusesource.c

Re: Overhead of component creation to send message

2011-11-18 Thread Dejan Bosanac
Hi Jason, those operations are costly and if your component must open/close it for every message it will affect performances. In those cases it is recommended to use pool connection factory which caches those object and improve performances. See http://activemq.apache.org/jmstemplate-gotchas.html

[HELP] IllegalStateException: Not supported with Tomcat 7.0.22 and AjaxServlet

2011-11-18 Thread liny
Hi, I have a web application to test AJAX feature, and it works fine with Tomcat 6.0.20. When I put same web application to Tomcat 7.0.22, exception is below: I think it must be relative AjaxServlet or jars of /lib between Tomcat6 and Tomcat7 but have no idea what's going on. Would you please gi

Re: Java app hanging at createTemporaryQueue

2011-11-18 Thread Martin C.
Hi, are you using failover-transport? If yes, you'll need to add a "timeout" parameter to the connection URL, as the default behavior of the failover transport is to wait indefinitely for a reconnect to the broker. Please see http://activemq.apache.org/failover-transport-reference.html for further

AMQ does not respect the message priority order completely?

2011-11-18 Thread SuoNayi
Hi all, I'm not sure this is correct or not. In order to respect the message priority order more sufficiently vmcursor which keeps all messages references in memory is recommended, because messages are read from message store or cache and ordered and dispatched to consumers in batches.