The reason that this message displays is because all of
the clones in the clients' application server group are marked as
unavailable. There are several possible reasons why the clones are marked
unavailable. Refer to the Common culprit section below for a list
of the possible reasons.
When this message is reported, WLM attempts to contact the
administrative server to get updated server group information. If WLM is
unable to contact the administrative server, it uses a different
administrative server from the server group (as long as administrative
server failover is not disabled). If the last administrative server
is unavailable, the WLM code displays this message again, but this time
for the administrative server group information. WLM then continues to
attempt to contact an administrative server until it is either successful,
or the client application stops. If it is unsuccessful, the message is
logged over and over again until success or until the client application
ends.
After the WLM code contacts the administrative server, it gets updated
server group information for the client application server group. After it
has the updated client application server group information, it either
routes the method request to an available clone, or if no clones are
available, returns an exception to the client application.
View this as a Warning message, not an Error message. It is a warning
message because it is an indicator that something is causing clones to be
marked as unavailable that might not actually be unavailable. The client
application can run normally, although routing of client requests might
not be optimal or reflective of a Round Robin behavior if that routing
policy is selected. If the client receives an exception back from WLM in
regards to this warning, the customer must determine why client-to-server
communications are being interrupted.
|