I don't know much about the IBM stack, but with Apache's AJP connector, you have the option to define keep alives (see socket_keepalive and ping_mode ): http://tomcat.apache.org/connectors-doc/reference/workers.html
If the IBM HTTP server is talking HTTP to the WebSphere server, the firewall should not interfere with the communications since each HTTP request/response can negotiate the session information (it is basically stateless between request/response pairs). Since the firewall is interfering, I can only assume that some other protocol is in use. Axton Grams On Wed, Apr 11, 2012 at 12:04 PM, Dee <ddus...@aim.com> wrote: > Thanks Axton, > > I posed the question to your websphere admins, > > We use http server in this case is IBM HTTP Server - 6.1.0.25, j2ee server > - > IBM WebSphere Application Server - ND - 6.1.0.25. > > > > > -- > View this message in context: > http://ars-action-request-system.1093659.n2.nabble.com/Java-API-connection-pool-question-tp7454090p7456744.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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
