Explanation | An exception occurred during Object Request Broker (ORB) initialization. See the description of the exception for more information. |
Action | Ensure that the IIOP transport channel is configured correctly. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The oneway GIOP request targets an object that requires further locate-forward addressing; however the server cannot send a locate-forward GIOP reply message because the client is not expecting a response. The server allows the oneway GIOP request to be dispatched; however the request may encounter errors as it might not carry the appropriate context. |
Action | If the oneway GIOP request encounters errors, then it may be necessary to change the client-side code to either fully locate the target object before sending the oneway request, or invoke the request as a normal two-way GIOP request instead of a oneway so the client can handle the locate-forward GIOP reply. The CWZGB0005I message can be disabled by setting the property com.ibm.ws.iiop.channel.disableOnewayLocateRequiredMessage=true. |