WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


WSWS

WSWS5001E: {0} is null.
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.
WSWS5002E: Input parameter {0} was passed in as null, but {1} was not called.
Explanation If a null argument is going to be passed in, then call the specified method 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.
WSWS5003E: Error {0} occurred while retrieving method {1} from class {2}: {3}
Explanation The specified exception occurred while attempting to retrieve the specified method from the specified class.
Action Make sure that the enterprise bean class contains the appropriate methods.
WSWS5004E: Error {0} occurred while invoking method {1} on class {2}: {3}
Explanation The specified exception occurred while attempting to invoke the specified method from the specified class.
Action Make sure that the enterprise bean class contains the appropriate methods.
WSWS5005E: {0} is not an interface.
Explanation The specified parameter is an interface, not a class.
Action Make sure that the parameter is passed in as an interface.
WSWS5006E: Class {0} is not an instance of EJBHome or EJBLocalHome.
Explanation The specified class name refers to a valid class, but the class is not an instance of EJBHome or EJBLocalHome.
Action Pass in a class name that refers to either a valid EJBHome or a EJBLocalHome class.
WSWS5007E: Error {0} occurred while attempting to locate the following JNDI name: {1}
{2}
Explanation An error occurred 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.
WSWS5008E: An error occurred while trying to obtain an InitialContext object: {0}.
Explanation The specified exception occurred while trying to create an InitialContext object to use for performing JNDI lookup operations.
Action Use the exception details to determine how to resolve the problem.
WSWS5009E: Error {0} occurred while attempting to create a protocol-specific Call object: {1}
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/.
WSWS5010E: Error: Cannot find port: {0}
Explanation The specified port cannot be found by the Service.getPort method.
Action Correct the invocation of Service.getPort.
WSWS5011E: Method {0} is not supported in a managed environment.
Explanation 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.
Action Make sure that you do not call these methods when the client application is running within the J2EE-managed environment.
WSWS5012E: An error occurred while loading a generated Stub class {0}: {1}
Explanation The specified exception occurred while a generated Stub class was being loaded.
Action Make sure that the specified Stub class exists and is available to load.
WSWS5013E: No constructor with the signature {0} was found for generated Stub class {1}: {2}
Explanation The specified generated Stub class requires a constructor with the specified signature.
Action Make sure that the proper Stub class is used.
WSWS5014E: An error occurred instantiating the generated Stub class {0}: {1}
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.
WSWS5015E: No WSDL definition was found at URI: {0}
Explanation The ServiceFactory.createService method cannot find a WSDL definition at the specified location.
Action Make sure that the WSDL document is available and that the WSDL location is correct.
WSWS5016E: The WSDL definition located at URI {0} did not contain Service {1}.
Explanation The specified WSDL definition was located, 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.
WSWS5017E: An error occurred while reading the WSDL definition that is located at URI: {0}
Explanation The specified WSDL document was either not found, or contains an error.
Action Make sure that the WSDL document exists and that it is correct.
WSWS5018E: Error {0} occurred while trying to invoke method {1} from class {2}: {3}
Explanation An exception occurred while attempting to invoke a method from the specified class.
Action Make sure that the specified enterprise bean class contains the appropriate methods.
WSWS5019E: An error occurred obtaining Service for port {0}: {1}
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/.
WSWS5020E: An error occurred obtaining Stub class {0}: {1}
Explanation The specified exception occurred during an attempt to obtain an instance of the generated Stub class.
Action Make sure that the generated Stub class is available to load.
WSWS5021E: An error occurred obtaining port {0}: {1}
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.
WSWS5022E: An error occurred while trying to create an extension for parent type {0} and element type {1}.
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/.
WSWS5023E: The protocol used in endpoint location URI {0} is not valid.
Explanation The specified endpoint location URI contains an incorrect protocol.
Action Correct the endpoint location URI.
WSWS5024E: Missing an equals sign (=) in the query string within the endpoint location URI: {0}
Explanation An error occurred while parsing the specified endpoint location URI.
Action Correct the endpoint location URI.
WSWS5025E: The attribute name {0} is not valid.
Explanation The caller tried to set or get the value for the specified attribute from an ExtensibilityElement, but the attribute name is not valid.
Action Make sure to use a valid attribute.
WSWS5026E: Internal error: Duplicate shadow registry.
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/.
WSWS5027E: The property name for Call object {0} is not valid.
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.
WSWS5028E: Error {0} occurred while trying to close a transport: {1}
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/.
WSWS5029E: Error {0} occurred while processing a method invocation: {1}
Explanation An exception occurred during the processing of a method request.
Action Use the detailed information from the error message to determine the cause of the error.
WSWS5030E: Method {0} is not valid.
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/.
WSWS5031E: The service endpoint interface {0} is not valid. No WSDL definition is available.
Explanation When calling the Service.getPort(Class) method, the WSDL definition is required, but is not available.
Action Make sure that the WSDL definition is available.
WSWS5032E: The service endpoint interface {0} is not valid. No default port is available.
Explanation When calling the Service.getPort(Class) method, a default port is required, but is not available.
Action Make sure that a default port exists for the service endpoint interface.
WSWS5033E: Cannot create a dynamic proxy without a WSDL definition.
Explanation If a generated Stub class is not found, then a dynamic proxy is created, but the WSDL definition is required.
Action Make sure that the WSDL definition is available.
WSWS5034E: Cannot create a dynamic proxy without a port QName.
Explanation If a generated Stub class is not found, then a dynamic proxy is created, but a non-null port name is required.
Action Make sure that a non-null port name is passed in.
WSWS5035E: Port {0} does not exist.
Explanation The specified port is not a valid port for the service.
Action Correct the port name.
WSWS5036E: No WSDL definition is available.
Explanation The Service.getPorts method cannot return the list of ports unless the WSDL definition is available.
Action Make sure that the WSDL definition is available.
WSWS5037E: The {0} is not supported by the {1} class.
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/.
WSWS5038I: not used
Explanation None.
Action None.
WSWS5039I: not used
Explanation None.
Action None.
WSWS5040I: not used
Explanation None.
Action None.
WSWS5041E: An error occurred while getting the protocol from endpoint location URI: {0}
Explanation An error occurred while trying to obtain the protocol of the specified endpoint location URI.
Action Make sure that the endpoint location URI is correct.
WSWS5042E: The protocol that is found in the WSDL endpoint location URI is not valid. Expected {0}, but found {1}.
Explanation An unexpected protocol value was found in the endpoint location URI.
Action None.
WSWS5043E: The Service class {0} does not implement the {1} interface.
Explanation 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.
Action Make sure that your Web service application is properly deployed with the wsdeploy tool.
WSWS5044E: The required constructor was not found for the generated Service class: {0}
Explanation A required constructor is missing.
Action Make sure that your Web service application is properly deployed with the wsdeploy tool.
WSWS5045E: {0}: An empty port name was found in the WSDL port names array.
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/.
WSWS5046E: Error {0} occurred getting an enterprise bean class name from endpoint location URI {1}: {2}
Explanation The EJB class name cannot be obtained from the specified endpoint location URI.
Action Correct the endpoint location URI.
WSWS5047E: Error {0} occurred getting properties from endpoint location URI {1}: {2}
Explanation An error occurred while parsing the properties that are contained in the specified endpoint location URI.
Action Correct the endpoint location URI.
WSWS5048E: The {0} property is missing from endpoint location URI {1}.
Explanation A required property was missing from the endpoint location URI.
Action Correct the endpoint location URI.
WSWS5049E: An error occurred while trying to instantiate a target object of class {0}: {1}
Explanation An instance of the specified implementation class cannot be instantiated.
Action Refer to the exception in the original error message to determine how to resolve the problem.
WSWS5050E: Error {0} occurred while trying to initialize target object of class {1}: {2}
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.
WSWS5051E: Error {0} occurred while trying to load target object class {1}: {2}
Explanation Unable to load the specified implementation class.
Action Make sure that the implementation class is available to load.
WSWS5052E: Error {0} occurred while getting the implementation class name from endpoint location URI {1}: {2}
Explanation Unable to obtain the implementation class name from the endpoint location URI.
Action Correct the endpoint location URI.
WSWS5053E: Error {0} occurred while trying to get method {1} on target class {2}: {3}
Explanation Unable to find the specified method on the specified implementation class.
Action Make sure that the correct implementation class is used.
WSWS5054E: Error {0} occurred while trying to invoke method {1} on target class {2}: {3}
Explanation An exception occurred while invoking the specified method.
Action Refer to the exception in the original error message to determine how to resolve the problem.
WSWS5055E: Cannot find a Service for namespace {0}.
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/.
WSWS5056E: A dynamic proxy cannot be created due to exception: {0}
Explanation A JAX-RPC dynamic proxy Stub cannot be created for the specified port and service endpoint interface.
Action Check that the specified service endpoint interface is valid.
WSWS5057E: No PortType exists in the WSDL defintion for the specified service endpoint interface: {0}.
Explanation The service endpoint interface name that is 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 that is defined in the WSDL.
WSWS5058E: The service endpoint interface {0} is not a valid interface.
Explanation When calling the Service.getPort(Class) method, the service endpoint interface must specify an interface.
Action Make sure that the service endpoint interface specifies an interface, not a class.
WSWS5059E: Parameter of type {0} could not be serialized while trying to invoke method {1} on target class {2}
Explanation An exception occurred while invoking the specified method as the parameter class does not extend java.io.Serializable
Action Change the parameter class to implement java.io.Serializable in both client and server
Reference topic    

Terms of Use | Feedback

Last updated: Feb 18, 2011 4:35:06 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.multiprotocol.resources.mpMessages.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)