This information might help you diagnose the trouble if you are having a workload distribution problem.
If Java exceptions appear in the log files, try to determine the actual subcomponent that is directly involved in the problem by examining the trace stack and looking for a WebSphere Application Server-related class near the top of the stack (names beginning with com.ibm.websphere or com.ibm.ws) that created the exception. If appropriate, review the steps for troubleshooting the appropriate subcomponent under the Troubleshooting WebSphere applications section of the Information Center.
For example, if the exception appears to have been thrown by a class in the com.ibm.websphere.naming package, review the "Naming Services Component troubleshooting tips" topic.
Workload management in WebSphere Application Server is based on a weighted proportional scheme to spray requests among the servers. This results in balance being determined by numbers of requests rather than by any other measure. A true balance problem is determined by comparing the number of requests processed by each member of the cluster with the weights that have been set for each of those members. This is done by following the steps in the topic "Troubleshooting the Workload Management component".
[10/11/04 13:11:10:233 CDT] 00000036 SelectionMana A WWLM0061W: An error was encountered sending a request to cluster member {MEMBERNAME=FlorenceEJBServer1, NODENAME=fwwsaix1Node01} and that member has been marked unusable for future requests to the cluster "", because of exception: org.omg.CORBA.COMM_FAILURE: CONNECT_FAILURE_ON_SSL_CLIENT_SOCKET - JSSL0130E: java.io.IOException: Signals that an I/O exception of some sort has occurred. Reason: Connection refused vmcid: 0x49421000 minor code: 70 completed: No"