Troubleshooting the Agent Plug-in › Web Service Invocation Error Messages

Web Service Invocation Error Messages

The section provides LStatus error messages related to invocation errors that appear in the Status.

nested exception is: ..org.xml.sax.SAXException: Deserializing parameter 'holdReturn': could not find deserializer for type {http://facade.espresso.cybermation.com}WebResponse

Reason:

Could not deserialize XML WebResponse response object that the invoked operation returned.

Action:

Specify the corresponding java class, for example, WebResponse, as a value for ReturnClassName. Ensure that the agent loaded corresponding class. If the class is a custom class, such as WebResponse, place it in the <agent_home>/jars/ext directory.

nested exception is: ..org.xml.sax.SAXException: Invalid element in java.lang.String - messages

Reason:

Could not deserialize XML response object that the invoked operation to java.lang.String returned.

Action:

Specify the correct java class, for example, WebResponse, as a value for ReturnClassName. Ensure that the agent loaded the corresponding class. If the class is a custom class, such as WebResponse, place it in the <agent_home>/jars/ext directory.

java.lang.NullPointerException

Reason:

Problem invoking a method. Axis library returned NullPointerException.

Action:

1. Check whether the operation returns a complex structure. If it does, specify the correct java class, for example, WebResponse, as a value for ReturnClassName.
   Ensure that the agent loaded the corresponding class. If the class is a custom class, such as WebResponse, place it in the <agent_home>/jars/ext directory.
2. Verify all your parameter types and values.

Error processing WSDL document: .java.net.ConnectException: Connection timed out: connect

Reason:

Problem connecting to the web service.

Action:

1. Verify your network connectivity.
2. Verify whether you need to connect through a proxy, and verify your proxy parameters in the agentparm.txt file.

Error processing WSDL document: .java.io.IOExc
eption: Server returned HTTP response code: 407 for URL: http://www.webservicex.com/stockquote.asmx?WSDL

Reason:

Problem connecting through a proxy. Proxy authentication required.

Action:

1. Verify whether you need to connect through a proxy, and verify your proxy parameters in the agentparm.txt file.
2. If the proxy is using NTLM authentication, ensure that the agent is logged to a domain.

Connection refused

Reason:

The host exists but is not listening for connections on that port. Alternatively, a firewall is blocking that port.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

Unknown host

Reason:

The hostname component of the URL is invalid or the client is off-line.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

404: Not Found

Reason:

A Web server exists but the URL is inactive or incorrect. Proxy servers can also generate 404 pages for unknown hosts.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

302: Moved

Reason:

The content at the end of the URL has moved, and the client application does not follow the links. The .com or .net address is invalid, or the port is explicitly -or defaulting to- port 80.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

Other 3xx response

Reason:

The content at the end of the URL has moved, and the client application does not follow the links.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

Wrong content type/MIME type

Reason:

The URL is incorrect, or the server application is not returning XML.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

XML parser error

Reason:

The content is not XML, but the client application assumes that it is.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

500: Internal Error

Reason:

SOAP uses this error as a cue that a SOAPFault has been returned, but it can also mean the server is not working through some internal fault.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

Connection Timed out/ NoRouteToHost

Reason:

The hostname can be resolved but not reached. Either the host is missing (potentially a transient fault), or network/firewall issues are preventing access. You may need to configure the client for its proxy server. This message can also appear if you are off line.

Action:

When a connectivity problem is suspected, check the URL that is at fault in your Web browser. Also check your proxy settings for the agent.

STATE FAILED Status(Invocation error) LStatus("(500)Server Error")

Reason:

Server error. A proxy is not required.

Action:

Verify the agentparm.txt file for proxy settings and comment the related proxy parameter lines.

STATE FAILED Status(Invocation error) LStatus("Error processing WSDL document: .java.net.ConnectException: Connection timed out: connect")

Reason:

The agent cannot connect to the web service.

Action:

Verify the agentparm.txt file for proxy settings and ensure that the agent is configured for the proxy server.

Invalid format, WS102: Unknown parameter type

Reason:

Problem instantiating a parameter or a response.

Action:

Check if your parameter types and your return class name are correct.

STATE FAILED Status(Invocation error)
LStatus("System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: […])

Reason:

Problem invoking the web service.

Action:

Remove the value in the Endpoint URL field of the job, and resubmit the job.

LStatus "System.Web.Services.Protocols.SoapException: Server was unable to process request."

Reason:

The WSDL URL is required in the Web Service job for Axis to construct the SOAP message properly. For example, this requirement can occur when a complex parameter is specified in the job definition.

Action:

Specify the WSDL URL in the Web Service job definition.

STATE FAILED Status(Invocation error) LStatus("No such operation 'triggerAdd'")

Reason:

Problem invoking the web service.

Action:

Remove the value in the WSDL URL field of the job.