search

carodriguez18 / jca-sockets

Automatically exported from code.google.com/p/jca-sockets
0 stars 0 forks source link

Fix the pooling with Glassfish #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Steps to reproduce:
   * Deploy to glassfish 2.1
   * Execute a number of client calls
Runs for a time but we run out of resources and it stops.

Linked to
http://code.google.com/p/jca-sockets/issues/detail?id=4

Original issue reported on code.google.com by mark.r.j...@gmail.com on 17 Apr 2009 at 6:04

GoogleCodeExporter commented 9 years ago 
May be an issue with creating and dropping connections in quick succession 
(which was the stress test that 
was being performed). Connections are left in TIME_WAIT and we run out of 
sockets (on windows the default 
is quite small but can be increased with a registry setting). 
It might therefore not be a server problem at all: to be investigated. 
The use case of one request/response per connection is not a good one anyway as 
it is pretty inefficient.

Original comment by mark.r.j...@gmail.com on 5 Jun 2010 at 3:39

GoogleCodeExporter commented 9 years ago 
Proved to be a problem with the settings on windows.

Original comment by mark.r.j...@gmail.com on 25 Jun 2010 at 8:50