The TIME_WAIT state is a normal part of connection teardown when the connection is closed. If you are seeing lots of connections in TIMED_WAIT state then you can combat that by caching the connection on the client side (i.e. opening a connection for every message you send would result in lots of sockets in TIMED_WAIT. Also using springs DMLC without caching can produce the same affect). Perhaps your IBM MQ config is caching the connection and thats why you don't see it.
Hope this helps, /Dave On Thu, Jun 4, 2009 at 11:13 AM, Websphere and ActiveMQ < derrick...@hotmail.com> wrote: > > Hi, > > Right Now I had the following problem/question, please help me, > > When I use Pure Java client to send/receive message to/from ActiveMQ, I use > "Watch 'netstat -lpan|grep 61616" command to monitor tcp connections, I > found there is always time_wait or close_wait socket after jms client > closed > connection. and these waits will be disappeared after several seconds or > longer. > > However, when I used IBM MQ, there isn't this problem. > > tcp 0 0 :::61616 :::* > LISTEN > tcp 0 0 ::ffff:127.0.0.1:61616 ::ffff:127.0.0.1:32979 > ESTABLISHED > tcp 0 0 ::ffff:127.0.0.1:32979 ::ffff:127.0.0.1:61616 > ESTABLISHED > tcp 0 0 ::ffff:127.0.0.1:33223 ::ffff:127.0.0.1:61616 > TIME_WAIT > tcp 0 0 ::ffff:127.0.0.1:33225 ::ffff:127.0.0.1:61616 > TIME_WAIT > tcp 0 0 ::ffff:172.30.16.232:33191 ::ffff:172.30.16.232:61616 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:33190 ::ffff:172.30.16.232:61616 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:33193 ::ffff:172.30.16.232:61616 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:33192 ::ffff:172.30.16.232:61616 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:61616 ::ffff:172.30.16.232:33190 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:61616 ::ffff:172.30.16.232:33191 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:61616 ::ffff:172.30.16.232:33192 > ESTABLISHED > tcp 0 0 ::ffff:172.30.16.232:61616 ::ffff:172.30.16.232:33193 > ESTABLISHED > > could somebody tell me why it is and how to configure activeMQ about it. > Thanks > -- > View this message in context: > http://www.nabble.com/About-Socket-close-questions%2C-tp23871978p23871978.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >