Websphere crashing

[Udaya Raj]

The workload is being shared by two websphere 5.2.0.6 servers and they crash very often and the entries in logs are:

javax.naming.NamingException: Error during resolve. Root exception is org.omg.CORBA.NO_IMPLEMENT: minor code: 49421040 completed: No
at com.ibm.ws.wlm.client.WLMClientLegacyImpl.handleRemoteException(WLMClientLegacyImpl.java:412)
at com.ibm.ws.wlm.client.WLMClient.handleRemoteException(WLMClient.java:231)
at com.ibm.rmi.corba.ClientDelegate._createRequest_WLM(ClientDelegate.java:2060)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1233)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1168)
at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:1830)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:245)

What is the reason for it and where can I look for the meanings of the minor codes given in the exceptions

[Albert Maurucier]

For WAS 4, this exception means that the workload management service has attempted repeatedly to contact the application servers without success. Workload management resumes when application servers become available again.
WLM becomes available after
Quotes from Ibm websphere infocenter:

"The WebSphere Application Server client can catch these exceptions and then implement its own strategies to handle the situation; for example, it can display an error message if no servers are available"

Regards
Albert