Last updated on FEBRUARY 27, 2014
Applies to:Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.
JavaCAPS 6.3 environment consists of domains (Glassfish Appservers) running inside a firewall and the EM (Enterprise Manager) is running outside of the firewall.
The keep-alive timeout setting for the GlassFish App Server has been disabled by setting the server.http-service.keep-alive.timout-in-seconds to -1. (asadmin> set server.http-service.keep-alive.timout-in-seconds=-1).
The time out for the firewall is set to two hours.
When there is not activity within two hours; stopping or starting a component in EM does not generate an alert in EM. No subsequent alerts are sent after the timeout occurs.
Bouncing the domain seems to reset things, but after two hours of inactivity the aberrant behavior reoccurs.
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