Re: java.io.IOException: Too many open files (v5.4.2)

2012-05-18 Thread johneboyer
Yes. After further research yesterday, we did http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/ increase the number of files parameter to *10240*. We have hundreds of open STOMP connections and expect this number to continue to grow in the coming months. /So, I guess the ques

Re: java.io.IOException: Too many open files (v5.4.2)

2012-05-18 Thread metatech
wrote > > /java.io.IOException: Too many open/ files error. > Hi, Have you tried adding "ulimit -n 2048" in the "~/.profile" of the user running ActiveMQ ? Can you show the output of "ulimit -a" ? metatech -- View this message in context: http://activemq.2283324.n4.nabble.com/java-io-IOE

Re: Questions on upgrading to 5.6.0

2012-05-18 Thread Geoffrey Arnold
Awesome Gary, this was exactly what I was looking for. Thanks again! On May 18, 2012, at 10:29 AM, Gary Tully wrote: > it is totally dependent on your disk size, when a limit is reached, > the next add will block. > The defaults from[1] are: > systemUsage.getMemoryUsage().setLimit(1024 * 1024

Re: JMSXUserID propagation not working

2012-05-18 Thread Timothy Bish
On Fri, 2012-05-18 at 08:59 -0700, gauche wrote: > Hmmm, I assume it is an AMQ issue rather than an NMS one. I just stepped > through the NMS code and can see that it is not modifying the headers at > all. If I explicitly set JMSXUserID then it gets sent, if I don't then it > doesn't. Guess I'm th

Re: JMSXUserID propagation not working

2012-05-18 Thread gauche
Hmmm, I assume it is an AMQ issue rather than an NMS one. I just stepped through the NMS code and can see that it is not modifying the headers at all. If I explicitly set JMSXUserID then it gets sent, if I don't then it doesn't. Guess I'm thinking it is AMQ's responsibility to use the connection us

Re: JMSXUserID propagation not working

2012-05-18 Thread Timothy Bish
On Fri, 2012-05-18 at 08:26 -0700, gauche wrote: > Hi, > > I am trying to get JMSXUserID to pass from producer (client) to consumer > (server) but am having no luck. > > My client is a .NET app using NMS V1.5.0.2194, with STOMP V1.5.2.2508. My > server is a Java app using (indirectly via an inte

JMSXUserID propagation not working

2012-05-18 Thread gauche
Hi, I am trying to get JMSXUserID to pass from producer (client) to consumer (server) but am having no luck. My client is a .NET app using NMS V1.5.0.2194, with STOMP V1.5.2.2508. My server is a Java app using (indirectly via an internal framework) activemq-core-5.3.0. My understanding was that

Re: ActiveMQ-CPP 3.4.2 memory leaks?

2012-05-18 Thread Ivan Pechorin
2012/5/14 > > I'm wondering whether or not you've been able to find out anything using > BoundsChecker or when you might have time to test it? I have access to > another tool which is not as good as what you have; it will probably take > me a couple of days before I have something I'm comfortabl

Re: Questions on upgrading to 5.6.0

2012-05-18 Thread Gary Tully
it is totally dependent on your disk size, when a limit is reached, the next add will block. The defaults from[1] are: systemUsage.getMemoryUsage().setLimit(1024 * 1024 * 64); // Default 64Meg systemUsage.getTempUsage().setLimit(1024L * 1024 * 1000 * 50); // 50 Gb systemUsage.getStoreUsage

Re: Questions on upgrading to 5.6.0

2012-05-18 Thread Geoffrey Arnold
Many thanks Gary! Do you have recommendations for the storeUsage and tempUsage limits given that our max journal file size is 32mb? How did this work in 5.4.0? On May 18, 2012, at 9:19 AM, Gary Tully wrote: > inline > > On 18 May 2012 05:24, Geoffrey Arnold wrote: >> We are upgrading from A

Re: Questions on upgrading to 5.6.0

2012-05-18 Thread Gary Tully
inline On 18 May 2012 05:24, Geoffrey Arnold wrote: > We are upgrading from AMQ 5.4.0 to 5.6.0, and noticed two issues right off > the bat: > > - The "activemq-all-5.6.0.jar" library is now bundled with the SLF4J Log4J > binding, trumping the JDK 1.4 binding already in our classpath.  As a > w

Re: TempQueue advisory flood

2012-05-18 Thread Gary Tully
Maybe some more logging will help identify the root cause. Enable TRACE level logging for the following packages: org.apache.activemq.broker.region org.apache.activemq.network org.apache.activemq.command and open a ticket and attach the log if you can still reproduce. On 17 May 2012 23:32, Chris