Error codes of com.WebServicesEngine

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

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

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

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

Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

There is a communication issue with application server or client. Check with FGLWSDEBUG.

The URL of the operation requested is unknown. Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

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

You need to debug your application.

Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

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

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

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

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

You need to debug your application. Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

You need to debug your application. Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

You need to debug your application. Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

You need to debug your application. Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

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

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

Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

This error code is reserved for future use.

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

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

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

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

Check that the HTTP request contains a valid cookie.

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

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.

Check the message with FGLWSDEBUG or display sqlca.sqlerrm.

The Web service does not implement the XML-binary Optimized Packaging (XOP) packaging specification for serializing binary data.

Handing of XML-Binary Optimized Packaging failed, check the error with FGLWSDEBUG

Check the URL of the resource and the REST web service function parameters.

Check that the number and type of input and return parameters match the service function.

Generation of Web Application Description Language (WADL) failed, check error with FGLWSDEBUG.

Generation of OpenAPI specification failed, check error with FGLWSDEBUG.

Runtime Content-Type set via WSContext does not match the WSMedia of the REST operation, check WSMedia and WSContext values.

Service is secured, and a user token is required to authenticate access. Check that you are providing a scope.

A client attempted to access a version of the OpenAPI documentation that does not exist.

The regular expression (regex) defined for the WSAttachment attribute in the REST operation is invalid, or the received file does not match the regex pattern for a valid file name. Check the WSAttachment attribute value.