Problem | A null value was passed for the specified parameter, and this value is not valid for this operation. |
User response | Make sure that a non-null value is passed in for the specified parameter. |
Problem | If a null argument is going to be passed in, then call the specified method to set the type of each argument. |
User response | 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. |
Problem | The specified exception occurred while attempting to retrieve the specified method from the specified class. |
User response | Make sure that the enterprise bean class contains the appropriate methods. |
Problem | The specified exception occurred while attempting to invoke the specified method from the specified class. |
User response | Make sure that the enterprise bean class contains the appropriate methods. |
Problem | The specified parameter is an interface, not a class. |
User response | Make sure that the parameter is passed in as an interface. |
Problem | The specified class name refers to a valid class, but the class is not an instance of EJBHome or EJBLocalHome. |
User response | Pass in a class name that refers to either a valid EJBHome or a EJBLocalHome class. |
Problem | An error occurred while attempting to do a JNDI lookup of the specified JNDI name. |
User response | Make sure that the correct JNDI lookup name is specified within the endpoint location URI. |
Problem | The specified exception occurred while trying to create an InitialContext object to use for performing JNDI lookup operations. |
User response | Use the exception details to determine how to resolve the problem. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The specified port cannot be found by the Service.getPort method. |
User response | Correct the invocation of Service.getPort. |
Problem | Within the managed J2EE environment, the Service.getTypeMappingRegistry and the Service.getHandlerRegistry methods are not supported. They can be called only within the unmanaged JSR-101 client environment. |
User response | Make sure that you do not call these methods when the client application is running within the J2EE-managed environment. |
Problem | The specified exception occurred while a generated Stub class was being loaded. |
User response | Make sure that the specified Stub class exists and is available to load. |
Problem | The specified generated Stub class requires a constructor with the specified signature. |
User response | Make sure that the proper Stub class is used. |
Problem | The specified exception occurred when a new instance of the generated Stub class was created. |
User response | Make sure that the proper generated Stub class is used. |
Problem | The ServiceFactory.createService method cannot find a WSDL definition at the specified location. |
User response | Make sure that the WSDL document is available and that the WSDL location is correct. |
Problem | The specified WSDL definition was located, but it does not contain the specified Service. |
User response | Make sure that the WSDL document contains the correct Service and that you are using the correct Service name. |
Problem | The specified WSDL document was either not found, or contains an error. |
User response | Make sure that the WSDL document exists and that it is correct. |
Problem | An exception occurred while attempting to invoke a method from the specified class. |
User response | Make sure that the specified enterprise bean class contains the appropriate methods. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The specified exception occurred during an attempt to obtain an instance of the generated Stub class. |
User response | Make sure that the generated Stub class is available to load. |
Problem | An error occurred while trying to obtain the Stub for the specified port. |
User response | Make sure that the generated Stub object exists and that the port name is correct. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The specified endpoint location URI contains an incorrect protocol. |
User response | Correct the endpoint location URI. |
Problem | An error occurred while parsing the specified endpoint location URI. |
User response | Correct the endpoint location URI. |
Problem | The caller tried to set or get the value for the specified attribute from an ExtensibilityElement, but the attribute name is not valid. |
User response | Make sure to use a valid attribute. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | An attempt was made to set or get the specified property on a Call object, but the property name is not valid. |
User response | Make sure that you are using a valid property name. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | An exception occurred during the processing of a method request. |
User response | Use the detailed information from the error message to determine the cause of the error. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | When calling the Service.getPort(Class) method, the WSDL definition is required, but is not available. |
User response | Make sure that the WSDL definition is available. |
Problem | When calling the Service.getPort(Class) method, a default port is required, but is not available. |
User response | Make sure that a default port exists for the service endpoint interface. |
Problem | If a generated Stub class is not found, then a dynamic proxy is created, but the WSDL definition is required. |
User response | Make sure that the WSDL definition is available. |
Problem | If a generated Stub class is not found, then a dynamic proxy is created, but a non-null port name is required. |
User response | Make sure that a non-null port name is passed in. |
Problem | The specified port is not a valid port for the service. |
User response | Correct the port name. |
Problem | The Service.getPorts method cannot return the list of ports unless the WSDL definition is available. |
User response | Make sure that the WSDL definition is available. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | None. |
User response | None. |
Problem | An error occurred while trying to obtain the protocol of the specified endpoint location URI. |
User response | Make sure that the endpoint location URI is correct. |
Problem | An unexpected protocol value was found in the endpoint location URI. |
User response | None. |
Problem | A JAX-RPC Service class must implement the specified interface to conform to the JAX-RPC specification. In this situation, the Web services runtime loaded a class that is assumed to be a valid Service class, but it does not implement the expected interface. |
User response | Make sure that your Web service application is properly deployed with the wsdeploy tool. |
Problem | A required constructor is missing. |
User response | Make sure that your Web service application is properly deployed with the wsdeploy tool. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The EJB class name cannot be obtained from the specified endpoint location URI. |
User response | Correct the endpoint location URI. |
Problem | An error occurred while parsing the properties that are contained in the specified endpoint location URI. |
User response | Correct the endpoint location URI. |
Problem | A required property was missing from the endpoint location URI. |
User response | Correct the endpoint location URI. |
Problem | An instance of the specified implementation class cannot be instantiated. |
User response | Refer to the exception in the original error message to determine how to resolve the problem. |
Problem | Unable to initialize an instance of the specified implementation class. |
User response | Refer to the exception in the original error message to determine how to resolve the problem. |
Problem | Unable to load the specified implementation class. |
User response | Make sure that the implementation class is available to load. |
Problem | Unable to obtain the implementation class name from the endpoint location URI. |
User response | Correct the endpoint location URI. |
Problem | Unable to find the specified method on the specified implementation class. |
User response | Make sure that the correct implementation class is used. |
Problem | An exception occurred while invoking the specified method. |
User response | Refer to the exception in the original error message to determine how to resolve the problem. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | A JAX-RPC dynamic proxy Stub cannot be created for the specified port and service endpoint interface. |
User response | Check that the specified service endpoint interface is valid. |
Problem | The service endpoint interface name that is passed to the getPort method must match a PortType in the WSDL for this Service. |
User response | Make sure that the service endpoint interface matches a PortType that is defined in the WSDL. |
Problem | When calling the Service.getPort(Class) method, the service endpoint interface must specify an interface. |
User response | Make sure that the service endpoint interface specifies an interface, not a class. |
Problem | An exception occurred while invoking the specified method as the parameter class does not extend java.io.Serializable |
User response | Change the parameter class to implement java.io.Serializable in both client and server |