Explanation | A null value was passed for the specified parameter, and this value is not valid for this operation. |
Action | Make sure that a non-null value is passed in for the specified parameter. |
Explanation | If you need to pass a null argument, then call the specified method to set the type for 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 Web services runtime cannot retrieve the specified method from thespecified class. |
Action | Make sure that the enterprise bean class contains the appropriate methods. |
Explanation | The Web services runtime cannot invoke the specified method from thespecified class. |
Action | Make sure that the enterprise bean class contains the appropriate methods. |
Explanation | The specified parameter is a class and not an interface. |
Action | Make sure that the parameter is passed in as an interface. |
Explanation | The specified class name refers to a valid class, but the class is not an instance of the EJBHome or EJBLocalHome class. |
Action | Pass in a class name that refers to either a valid EJBHome or a EJBLocalHome class. |
Explanation | The Web services runtime cannot complete a JNDI lookup of the specifiedJNDI name. |
Action | Make sure that the correct JNDI lookup name is specified within the endpoint location URI. |
Explanation | The Web services runtime cannot create an InitialContext object to usefor performing 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, 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 Service.getPort method cannot find the specified port. |
Action | Correct the invocation of the Service.getPort method. |
Explanation | Within the managed Java 2 Platform, Enterprise Edition (Java EE) environment, the Service.getTypeMappingRegistry and the Service.getHandlerRegistry methods are not supported. These methods can be called within the unmanaged JSR-101 client environment only. |
Action | Make sure that you do not call these methods when the client application is running within the Java EE managed environment. |
Explanation | The Web services runtime cannot load the generated stub class. |
Action | Make sure that the specified Stub class exists and is available to load. |
Explanation | The specified generated Stub class requires a constructor with the specified signature. |
Action | Make sure that the proper Stub class is used. |
Explanation | The specified exception occurred when a new instance of the generated Stub class was created. |
Action | Make sure that the proper generated Stub class is used. |
Explanation | The ServiceFactory.createService method cannot find a Web Services Description Langauge (WSDL) definition at the specified location. |
Action | Make sure that the WSDL document is available and that the WSDL location is correct. |
Explanation | The Web services runtime located the specified Web Services DescriptionLanguage (WSDL) definition, but it does 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 Web services runtime cannot find the specified Web ServicesDescription Language (WSDL) document or the document contains an error. |
Action | Make sure that the WSDL document exists and that it is correct. |
Explanation | The Web services runtime cannot invoke a method from the specified class. |
Action | Make sure that the specified enterprise bean class contains the appropriate methods. |
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 Web services runtime cannot obtain an instance of the generated stub class. |
Action | Make sure that the generated Stub class is available to load. |
Explanation | The Web services runtime cannot 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, 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 specified endpoint location URI contains an incorrect protocol. |
Action | Correct the endpoint location URI. |
Explanation | The Web services runtime cannot parse 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 element, but the attribute name is not valid. |
Action | Make sure to use a valid attribute. |
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 Web services client attempted 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, 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 Web services runtime cannot process the 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, 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 | When the Web Service client calls the Service.getPort(Class) method, the Web Services Definition Language (WSDL) definition is required, but is not available. |
Action | Make sure that the WSDL definition is available. |
Explanation | When the Web Service client calls the Service.getPort(Class) method, a default port is required, but it is not available. |
Action | Make sure that a default port exists for the service endpoint interface. |
Explanation | If the Web services runtime does not find a generated stub class, then a dynamic proxy is created, but the Web Services Description Language (WSDL)definition is required. |
Action | Make sure that the WSDL definition is available. |
Explanation | If the Web services runtime does not find a generated stub class, then a dynamic proxy is created, but a non-null port name is required. |
Action | ake sure that a non-null port name is passed into the configuration. |
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 Web Services Definition Langauge (WSDL) definition is available. |
Action | Make sure that the WSDL definition is available. |
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 | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | None. |
Action | None. |
Explanation | The Web services runtime cannot obtain the protocol of the specified endpointlocation URI. |
Action | Make sure that the endpoint location URI is correct. |
Explanation | The Web services runtime encountered an unexpected protocol value in theendpoint location URI. |
Action | Correct the protocol value in the endpoint location URI. |
Explanation | A JAX-RPC service class must implement the specified interface to conform tothe 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. |
Action | Make sure that your Web service application is properly deployed with the wsdeploy tool. |
Explanation | A required constructor is missing. |
Action | Make sure that your Web service application is properly deployed with the wsdeploy tool. |
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 Web services runtime cannot obtain the Enterprise JavaBeans (EJB) class namefrom the specified endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | The Web services runtime cannot parse the properties that exist in the specifiedendpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | A required property is missing from the endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | The Web services runtime cannot instantiate an instance of the specifiedimplementation class. |
Action | Refer to the exception in the original error message to determine how to resolve the problem. |
Explanation | The Web services runtime cannot initialize an instance of the specifiedimplementation class. |
Action | Refer to the exception in the original error message to determine how to resolve the problem. |
Explanation | The Web services runtime cannot load the specified implementation class. |
Action | Make sure that the implementation class is available to load. |
Explanation | The Web services runtime cannot obtain the implementation class name from the endpoint location URI. |
Action | Correct the endpoint location URI. |
Explanation | The Web services runtime cannot locate the specified method on the specifiedimplementation class. |
Action | Make sure that the correct implementation class is used. |
Explanation | The Web services runtime cannot invoke 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, 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 Web services runtime cannot create a JAX-RPC dynamic proxy stub for the specified port and service endpoint interface. |
Action | Check that the specified service endpoint interface is valid. |
Explanation | The service endpoint interface name that is passed to the getPort method must match a PortType value in the Web Services Description Language (WSDL) documentfor this Service. |
Action | Make sure that the service endpoint interface matches the PortType value that is definedin the WSDL document. |
Explanation | When the Web services runtime calls the Service.getPort(Class) method, the serviceendpoint interface must specify an interface. |
Action | Make sure that the service endpoint interface specifies an interface, not a class. |
Explanation | The Web services runtime cannot invoke the specified method as the parameter classdoes not extend the java.io.Serializable interface. |
Action | Change the parameter class to implement the java.io.Serializable in both client and server |