Re: [Spam: 5.0] Memory usage increase after client power failure

2007-02-26 Thread eccrowe
nt 4.2 SVN > version > works in my environment (Linux, JDK 1.5) just fine out of the box. > > If a client is suspended on Linux with CTRL-Z > then the broker closes the connection after 30 seconds. > > I'm not sure why eccrowe has the long delay problem: > > ===qu

Re: [Spam: 5.0] Memory usage increase after client power failure

2007-02-23 Thread eccrowe
te: >> Op woensdag 21 februari 2007 21:05, schreef eccrowe: >> >> > It should also be noted that after a client power off, the remaining >> active >> > clients very quickly stop receiving their messages. Server logs still >> > appear to be sending

incorrect svn 4.1 tag checkout link

2007-02-22 Thread eccrowe
Just thought someone would like to know that the following page is referring to the wrong svn tag checkout link for release 4.1. It is still referring to the incubator. http://activemq.apache.org/activemq-410-release.html -- View this message in context: http://www.nabble.com/incorrect-svn-4.1

Re: Memory usage increase after client power failure

2007-02-21 Thread eccrowe
using 4.1.0 on your > platform/hardware? > > On 2/16/07, eccrowe <[EMAIL PROTECTED]> wrote: >> >> Greetings, >> >> We are utilizing a client/server (hub/spoke) topic implementation with >> ActiveMQ-4.0-RC2 and have noticed a repeatable memory us

Memory usage increase after client power failure

2007-02-16 Thread eccrowe
Greetings, We are utilizing a client/server (hub/spoke) topic implementation with ActiveMQ-4.0-RC2 and have noticed a repeatable memory usage increase reported by the UsageManager when a "SocketException: Broken pipe" error occurs within the AbstractConnection.Transport. This has been repeatable

ActiveMQ Topic Memory Usage Requirements

2007-02-07 Thread eccrowe
Greetings, I apologize in advance if this question has already been asked before, but my forum search has not been fruitful in regards to this question as of yet. The question I have is about the memory usage requirements with a non-persistent topic. We are running ActiveMQ 4.0-RC2 in an embedd