Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 2.0 and later
Information in this document applies to any platform.
***Checked for relevance on 29-Aug-2013***
Let's take the scenario that you have a web application deployed to the GlassFish Application Server instance I1 and this web application is designed to invoke a remote method of a remote Enterprise JavaBean (EJB) that is deployed on another GlassFish instance called R1. Instance R1 is on a different machine to I1 and the network between I1 and R1 has a firewall to control access. The firewall is configured to time out idle connections, that is if the network connections to R1 have no network traffic on them in some set time period, then they are terminated.
In such a scenario, if there is active firewall configured to drop idle connections, then the invocation of the business method call on the remote EJB may fail, hanging for a long time even though it normally works without issue. This failure to invoke the remote EJB is caused when the connection to the EJB has been inactive long enough for the firewall to terminate it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms