I really don't know the amount of network saturation, but I suppose there could be some underlying issues with the network and microsoft server 2003. I'll check with our tech guy and search a little online for any issues involving activemq and ms server 2003.
As far as the version I've tried both 3.0 and 3.2.1 - both have similar effects. Thanks for the reply. Any other insights would be appreciated. Mark -----Original Message----- From: Hiram Chirino [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 10:40 AM To: [email protected] Subject: Re: Question about connection pooling 20 seconds sounds like a long time for me too. For me, new connections are established in under a second. Is there much load on the sever/network? What version of ActiveMQ are you using? Regards, Hiram On Jan 5, 2006, at 4:47 PM, DeSantis, MJ Mark @ IS (7179) wrote: > Hello all, > > I'm pretty new to ActiveMq so forgive my naiveté. > > I have a project I'm working on which, though Jms, spawns new JVMs > on remote > machines. Threads in those new JVMs then register with the Jms > server to > listen for jms messages themselves. The problem I'm facing is that > it seems > there is about a 20 second delay for those threads to connect to > the server > - that is too slow. I was wondering if there was some sort of > connection > pooling that activemq can be configured to implement. I though > perhaps if > activemq could have a pool of open connections perhaps my threads > could > connect to jms faster. > > Thanks > > Mark
