Explanation | A null value was passed for the specified parameter, and this is not valid for this particular operation. |
Action | Make sure that a non-null value is passed in for the specified parameter. |
Explanation | If a null argument is going to be passed in, then the specified method should be called to set the type of each argument. |
Action | Make sure that you first call the appropriate method to set the argument types, or make sure that you do not pass a null argument to the 'invoke' method. |
Explanation | The specified exception was caught while attempting to retrieve the specified method from the specified class. |
Action | Make sure that the specified EJB class contains the appropriate methods. |
Explanation | The specified exception was caught while attempting to invoke the specified method from the specified class. |
Action | Make sure that the specified EJB class contains the appropriate methods. |
Explanation | The specified parameter should be an interface, not a class. |
Action | Make sure that the parameter is passed in as an interface. |
Explanation | The specified class name should refer to a valid EJBHome class, but the class is not an instance of EJBHome or EJBLocalHome. |
Action | A class name which refers to a valid EJBHome or EJBLocalHome class should be passed in. |
Explanation | An error was encountered while attempting to do a JNDI lookup of the specified JNDI name. |
Action | Make sure that the correct JNDI lookup name is specified within the endpoint location URI. |
Explanation | The specified exception was caught while trying to create an InitialContext object which would be used to perform JNDI lookup operations. |
Action | Use the exception details to determine how to resolve the problem. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified port could not be found by Service.getPort. |
Action | Correct the invocation of Service.getPort. |
Explanation | Within the managed J2EE environment, the Service.getTypeMappingRegistry and Service.getHandlerRegistry methods are not supported. They may only be called within the unmanaged JSR-101 client environment. |
Action | Make sure that you do not call these methods when the client application is running within the J2EE managed environment. |
Explanation | The specified exception was thrown while a generated Stub class was being loaded. |
Action | Make sure that the specified Stub class exists and is available to be loaded. |
Explanation | The specified generated Stub class should have a constructor with the specified signature. |
Action | Make sure that the proper Stub class is being used. |
Explanation | The specified exception was thrown when a new instance of the generated Stub class was being created. |
Action | Make sure that the proper generated Stub class is being used. |
Explanation | The ServiceFactory.createService method was unable to find a WSDL definition at the specified location. |
Action | Make sure that the WSDL document is available and that the WSDL location is correct. |
Explanation | The specified WSDL definition was located, but it did not contain the specified Service. |
Action | Make sure that the WSDL document contains the correct Service and that you are using the correct Service name. |
Explanation | The specified WSDL document was either not found, or contained an error. |
Action | Make sure that the WSDL document exists and that it is correct. |
Explanation | An exception was thrown while attempting to invoke a method from the specified class. |
Action | Make sure that the specified EJB class contains the appropriate methods. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified exception was thrown while an attempt was made to obtain an instance of the generated Stub class. |
Action | Make sure that the generated Stub class is available to be loaded. |
Explanation | An error occurred while trying to obtain the Stub for the specified port. |
Action | Make sure that the generated Stub object exists and that the port name is correct. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified endpoint location URI contains an incorrect protocol. |
Action | Correct the endpoint location URI. |
Explanation | An error was found while parsing the specified endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | The caller tried to set or get the value for the specified attribute from an ExtensibilityElement, but the attribute name is not a valid name. |
Action | Make sure that a valid attribute is used. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to set or get the specified property on a Call object, but the property name is not valid. |
Action | Make sure that you are using a valid property name. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An exception was thrown during the processing of a method request. |
Action | Use the detailed information from the error message to determine the cause of the error. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | When calling Service.getPort(Class), the WSDL definition is required but was not available. |
Action | Make sure the WSDL definition is available. |
Explanation | When calling Service.getPort(Class), a default port is required but was not available. |
Action | Make sure that a default port exists for the Service Endpoint Interface. |
Explanation | If a generated Stub class is not found, then a dynamic proxy will be created, but the WSDL definition is required. |
Action | Make sure the WSDL definition is available. |
Explanation | If a generated Stub class is not found, then a dynamic proxy will be created, but a non-null port name is required. |
Action | Make sure that a non-null port name is passed in. |
Explanation | The specified port is not a valid port for the service. |
Action | Correct the port name. |
Explanation | The Service.getPorts() method cannot return the list of ports unless the WSDL definition is available. |
Action | Make sure the WSDL definition is available. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | An error occurred while trying to obtain the protocol of the specified endpoint location URI. |
Action | Make sure the endpoint location URI is correct. |
Explanation | An unexpected protocol value was found in the endpoint location URI. |
Action | None. |
Explanation | A JAX-RPC Service class must implement the specified interface in order to conform to the JAX-RPC specification. In this situation, the Web services runtime loaded a class assumed to be a valid Service class, but it does not implement the expected interface. |
Action | Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool. |
Explanation | See error message. |
Action | Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The EJB class name could not be obtained from the specified endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | An error occurred while parsing the properties contained in the specified endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | A required property was missing from the endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | Unable create an instance of the specified implementation class. |
Action | Refer to the exception in the original error message to determine how to resolve the problem. |
Explanation | Unable to initialize an instance of the specified implementation class. |
Action | Refer to the exception in the original error message to determine how to resolve the problem. |
Explanation | Unable to load the specified implementation class. |
Action | Make sure that the implementation class is available to be loaded. |
Explanation | Unable to obtain the implementation class name from the endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | Unable to find the specified method on the specified implementation class. |
Action | Make sure that the correct implementation class is being used. |
Explanation | An exception was thrown while invoking the specified method. |
Action | Refer to the exception in the original error message to determine how to resolve the problem. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A JAXRPC dynamic proxy Stub could not be created for the specified port and service endpoint interface. |
Action | Check that the specified service endpoint interface is valid. |
Explanation | The service endpoint interface name passed to the getPort method must match a PortType in the WSDL for this Service. |
Action | Make sure that the service endpoint interface matches a PortType defined in the WSDL. |
Explanation | When calling Service.getPort(Class), the service endpoint interface must specify an Interface. |
Action | Make sure that the Service Endpoint Interface specifies an interface, not a class. |