users@glassfish.java.net

Re: HTTP listeners stop responding

From: <forums_at_java.net>
Date: Fri, 30 Nov 2012 02:37:19 -0600 (CST)

This issue occurred again today. When I ran netstat, using grep to only show
the connections to the database server, (via the command netstat | grep
"50-16-"), I got tcp 1 0 domU-12-31-39-06-25-C:47149
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 1 0 domU-12-31-39-06-25-C:47613
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 1 0 domU-12-31-39-06-25-C:47854
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 1 0 domU-12-31-39-06-25-C:47861
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 1 0 domU-12-31-39-06-25-C:48039
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 1 0 domU-12-31-39-06-25-C:48057
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 1 0 domU-12-31-39-06-25-C:40936
ec2-50-16-218-250.com:50001 CLOSE_WAIT tcp 0 0 domU-12-31-39-06-25-C:51361
ec2-50-16-218-250.com:50001 TIME_WAIT tcp 650 0 domU-12-31-39-06-25-C:https
ec2-50-16-218-250.com:59268 ESTABLISHED tcp 651 0 domU-12-31-39-06-25-C:https
ec2-50-16-218-250.com:59260 CLOSE_WAIT That is, there were not many
connections open to the billing service (but there was a very long list of
connections to unfamiliar addresses). Similarly, the list of connections as
reported by DB2 contained only a few entries for the Glassfish server. On DB2
I forced all the connections from Glassfish and ran netstat | grep "50-16-"
again, receiving the following output: tcp 0 425 domU-12-31-39-06-25-C:47149
ec2-50-16-218-250.com:50001 LAST_ACK tcp 1 1 domU-12-31-39-06-25-C:47613
ec2-50-16-218-250.com:50001 LAST_ACK tcp 1 1 domU-12-31-39-06-25-C:47854
ec2-50-16-218-250.com:50001 LAST_ACK tcp 1 1 domU-12-31-39-06-25-C:47861
ec2-50-16-218-250.com:50001 LAST_ACK tcp 1 1 domU-12-31-39-06-25-C:48039
ec2-50-16-218-250.com:50001 LAST_ACK tcp 1 1 domU-12-31-39-06-25-C:48057
ec2-50-16-218-250.com:50001 LAST_ACK tcp 1 1 domU-12-31-39-06-25-C:40936
ec2-50-16-218-250.com:50001 LAST_ACK Glassfish was still unresponsive.
Finally, I restarted Glassfish and everything returned back to normal.
netstat reported a much shorter list of connections. Any ideas?

--
[Message sent by forum member 'bernhardhaeussermann']
View Post: http://forums.java.net/node/892788