'Oc4jselectmethod roundrobin:weighted' Results in HTTP-500 Errors When An OC4J Instance is Down

(Doc ID 731531.1)

Last updated on APRIL 13, 2016

Applies to:

Oracle HTTP Server - Version: to - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
Checked for relevance on 13-May-2009


Oc4jSelectMethod roundrobin:weighted
Oc4jRoutingWeight <host1> 1
Oc4jRoutingWeight <host2> 1
Oc4jSelectMethod random:weighted
Oc4jRoutingWeight <host1> 2
Oc4jRoutingWeight <host2> 3
           and the test is repeated, once the active OC4J instance is shut down, mod_oc4j fails to recognise the non-availability of the active OC4J instance, and attempts to route the next request to it.
[error] [client] [ecid:1213958400:,0] mod_oc4j: request to OC4J hostname1.uk.oracle.com:12504 failed:
Connect failed (errno=111)
[error] [client] [ecid:
1213958515:,0] mod_oc4j: There is no oc4j process (for destination:
application://test) available to service request.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms