Axton, >From our network admins, these points where made, in response to your post.
The connections from the midtier (Websphere) server to the ARserver are persistent TCP connections. These connections are not stateless. Our firewall is doing stateful inspection on these connections. The firewall security policy allows all of these connections to be started. Connections are flushed from the firewall state tables after 1 hour of INACTIVITY. Not active connections are ever flushed. After an inactive connection has been flushed, any further packets (in either direction) are dropped by the firewall. No RST packets are sent to the session endpoints at the time of the flush or at the time of the packet drops. A firewall log entry is created for each of these "out-of-state" packet drops. After attempting to re-use one of the inactive/flushed connections, the application's session endpoint make take several minutes doing TCP retries of their dropped packets before they give up and start a new connection. We want to know how we can configure the AR product to either: 1) keep these connections active by implementing the keepalive protocol or 2) close the connections when the immediate unit of work is finished. -- View this message in context: http://ars-action-request-system.1093659.n2.nabble.com/Java-API-connection-pool-question-tp7454090p7459721.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
