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


WSWS

WSWS5001E: {0} is null.
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.
WSWS5002E: Input parameter {0} was passed in as null, but {1} has not been called.
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.
WSWS5003E: Caught {0} while retrieving method ''{1}'' from class ''{2}'': {3}
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.
WSWS5004E: Caught {0} while invoking method ''{1}'' on class ''{2}'': {3}
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.
WSWS5005E: {0} is not an interface.
Explanation The specified parameter should be 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 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.
WSWS5007E: Caught {0} while attempting to locate the following JNDI name: {1}
{2}
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.
WSWS5008E: Caught {0} while trying to obtain an InitialContext object.
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.
WSWS5009E: Caught {0} while attempting to create 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 could not be found by Service.getPort.
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 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.
WSWS5012E: Error loading generated Stub class ''{0}'': {1}
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.
WSWS5013E: No constructor with the signature {0} was found for generated Stub class ''{1}'': {2}
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.
WSWS5014E: Error instantiating generated Stub class ''{0}'': {1}
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.
WSWS5015E: No WSDL definition was found at URI: {0}
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.
WSWS5016E: The WSDL definition located at URI ''{0}'' did not contain Service ''{1}''.
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.
WSWS5017E: Error reading WSDL definition located at URI: {0}
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.
WSWS5018E: Caught {0} while trying to invoke method ''{1}'' from class ''{2}'': {3}
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.
WSWS5019E: Error 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: Error obtaining Stub class ''{0}'': {1}
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.
WSWS5021E: Error 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: Error while trying to create 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: Invalid protocol in endpoint location URI: {0}
Explanation The specified endpoint location URI contains an incorrect protocol.
Action Correct the endpoint location URI.
WSWS5024E: Missing '=' in query string within endpoint location URI: {0}
Explanation An error was found while parsing the specified endpoint location URI.
Action Correct the endpoint location URI.
WSWS5025E: Invalid attribute name: {0}
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.
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: Invalid property name for Call object: ''{0}''
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: Caught {0} 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: Caught {0} while processing a method invocation: {1}
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.
WSWS5030E: Invalid method: {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/.
WSWS5031E: Invalid Service Endpoint Interface: ''{0}''. No WSDL definition available.
Explanation When calling Service.getPort(Class), the WSDL definition is required but was not available.
Action Make sure the WSDL definition is available.
WSWS5032E: Invalid Service Endpoint Interface: ''{0}''. No default port 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.
WSWS5033E: Cannot create a dynamic proxy without a WSDL definition.
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.
WSWS5034E: Cannot create a dynamic proxy without a port QName.
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.
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 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: Error getting 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 the endpoint location URI is correct.
WSWS5042E: Invalid protocol found in WSDL endpoint location URI. 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 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.
WSWS5044E: The required constructor was not found for the generated Service class: ''{0}''
Explanation See error message.
Action Make sure that your Web service application has been properly deployed with the 'wsdeploy' tool.
WSWS5045E: {0}: empty port name found in 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: Caught {0} getting EJB class name from endpoint location URI ''{1}'': {2}
Explanation The EJB class name could not be obtained from the specified endpoint location URI.
Action Correct the endpoint location URI.
WSWS5047E: Caught {0} getting properties from endpoint location URI ''{1}'': {2}
Explanation An error occurred while parsing the properties 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: Caught an unexpected exception while trying to instantiate a target object of class ''{0}'': {1}
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.
WSWS5050E: Caught {0} 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: Caught {0} 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 be loaded.
WSWS5052E: Caught {0} getting 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: Caught {0} 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 being used.
WSWS5054E: Caught {0} while trying to invoke method ''{1}'' on target class ''{2}'': {3}
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.
WSWS5055E: Could not 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: Cannot create a dynamic proxy due to exception: {0}
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.
WSWS5057E: There is no PortType in the WSDL defintion for the specified service endpoint interface: ''{0}''.
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.
WSWS5058E: Invalid Service Endpoint Interface: ''{0}'' is not an interface.
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.
Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 5:37:33 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/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)