Error codes of com.WebServicesEngine

Error codes returned by com.WebServiceEngine methods.

Table 1. com.WebServiceEngine error codes
Number Description
-1 Timeout

com.WebServiceEngine.ProcessServices(x) timeout is reached. No requests to process during x seconds.

-2 AsCloseCommand

GAS tells the DVM to shutdown. You must exit your application.

-3 ConnectionBroken

Client has closed the connection in standalone GWS (without GAS).

-4 ConnectionInterrupted

Ctrl-C received. Interruption received by DVM. You must exit your application.

-5 BadHTTPHeader

Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-6 MalformedSOAPEnvelope

Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-7 MalformedXMLDocument

Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-8 InternalHTTPError

Communication issue with application server or client.

-9 Unsupported operation

The URL of the operation requested is unknown. Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-10 UnknownError

This is an internal error, contact the support team. You must exit your application.

-11 WSDL generation failed

You need to debug your application.

-12 WSDL Service not found

Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-13 Reserved

No need to exit the application. A new request might not have the issue.

-14 Incoming request overflow

You exceed the data maximum length allowed by com.WebServiceEngine.SetOption(maximumresponselength).

-15 Server was not started

Call to com.WebServiceEngine.Start() failed. You must exit your application.

-16 Request still in progress

With RESTful service, you are currently processing a request and has not yet send the response and try to process another request. You need to debug your application. It depends, you might not need to stop your application.

-17 Stax response error

You need to debug your application. Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-18 Input request handler error

You need to debug your application. Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-19 Output request handler error

You need to debug your application. Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-20 WSDL handler error

You need to debug your application. Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-21 SOAP Version mismatch

Your client SOAP version does not match your server SOAP version, amend either your client or your server code.

-22 SOAP header not understood

Modify your server code to handled the mustUnderstand attribute. Use the incoming request handler.

-23 Deserialization error

Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.

-24 Reserved error code -24

This error code is reserved for future use.

-25 Web Services Addressing action is mandatory

Check that the WSA action is specified in the SOAP message.

-26 Web Services Addressing message header is invalid

Check that the WSA header is correct in the SOAP message.

-27 Web Services Addressing message header is mandatory

Check that the WSA header is specified in the SOAP message.

-28 Web Services Addressing message protocol does not match

Check that the WSA message uses the protocol version of the client matches the version expected by the server.

-29 Cookie error

Check that the HTTP request contains a valid cookie.

-30 No active web operation

The method was called outside the context of a web operation processing.

-31 Web Operation was flushed

This code is returned by the ProcessServices() or the HandlerRequest() method, to indicated that the Flush() method was called during the last web operation execution.

-32 Serialization error

Check the message with FGLWSDEBUG or display SQLCA.SQLERRM.