We are running in to an issue where connection attempts made via the
FailoverTransport in CMS 3.6 seem to leak socket descriptors.  Does anyone
have any suggestions as to where we can look to figure out what is
happening?

The problem is easy to reproduce by connecting a process using CMS to an
ActiveMQ broker and then stopping the broker.  Each connection attempt
leaves a socket descriptor around.  Restarting the broker to allow the
process to reconnect seems to cause the descriptors to clean up.

See the bottom of the list shown below for an example.

COMMAND   PID    USER   FD   TYPE  DEVICE SIZE/OFF    NODE NAME
cwd    DIR     8,7     4096 1540097 xxx
rtd    DIR     8,5     4096       2 /
txt    REG     8,7   656370  999446 xxx
DEL    REG     8,6           296641 /var/run/nscd/dbavetpG
mem    REG     8,5    79536 1073594 /lib/libz.so.1.2.3
mem    REG     8,5   161288 1073641 /lib/libexpat.so.1.5.2
mem    REG     8,5    17392 1073560 /lib/libdl-2.11.3.so
mem    REG     8,5    59517 1073558 /lib/libcrypt-2.11.3.so
mem    REG     8,5    43219 1073584 /lib/librt-2.11.3.so
mem    REG     8,5  1688706 1073554 /lib/libc-2.11.3.so
mem    REG     8,5   497580  721057 /usr/local/lib/libgcc_s.so.1
mem    REG     8,5   186910 1073562 /lib/libm-2.11.3.so
mem    REG     8,5  5021355  721064 /usr/local/lib/libstdc++.so.6.0.17
mem    REG     8,5   323928 1207278 /usr/lib/libssl.so.0.9.8
mem    REG     8,5  1589896 1206823 /usr/lib/libcrypto.so.0.9.8
mem    REG     8,5   832384  721066 /usr/local/lib/libaprutil-1.so.0.3.10
mem    REG     8,5  1708634  721065 /usr/local/lib/libapr-1.so.0.4.2
mem    REG     8,5 55818407  721060 /usr/local/lib/libactivemq-cpp.so.16.0.0
mem    REG     8,5   124908 1073580 /lib/libpthread-2.11.3.so
mem    REG     8,5   143955 1074072 /lib/ld-2.11.3.so
0u   CHR   136,2      0t0       5 /dev/pts/2
1u   CHR   136,2      0t0       5 /dev/pts/2
2u   CHR   136,2      0t0       5 /dev/pts/2
3r   CHR     1,9      0t0    1399 /dev/urandom
4u  sock     0,7      0t0 2132112 can't identify protocol
5u  sock     0,7      0t0 2131180 can't identify protocol
6u  sock     0,7      0t0 2131692 can't identify protocol
20u  IPv4 2131990      0t0     TCP localhost:56236->localhost:61618
(CLOSE_WAIT)




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/CMS-3-6-Socket-Descriptor-Leak-With-Failover-tp4667966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to