FAQs (EN): What does the error code -72 in the socket server logfile mean?

FAQs (EN)

32. What does the error code -72 in the socket server logfile mean?

Under unixoid operating systems it can happen that error codes are output shifted by a multiple of 256.

Example: The return value 440 is thus output as 184 or even as -72.

The following list gives an overview of possible error returns by the socket server. The error numbers have the following meaning:

Return value	Description of the return values
401	Xerces reported error in input xml or during output xml generation
402	Function not implemented.
403	Internal error
404	At least one step failed, because the executed command failed.
405	The specified input file is empty.
406	The specified contents of a job or step are invalid.
407	Properties incompatible, for example InMemoryProcessing=1 and InputFilename=xxx.rtf im FormatStep
408	the job or step is still processed (used for intermediate results)
409	No input filename specified
410	Java exception occurred
411	A step was not executed, because one of his predecessors failed
412	A step reached its configured timeout and was not executed completely.
413	During execution of a step, the job timeout was reached. The step was not executed completely.
414	During execution of a job, a step timeout or the job timeout was reched, and the processing was stopped.
433	The SocketServer hangs due to a general resource problem (e.g. maximum memory of the operating system exceeded).
434	No response from the socket server after the time specified in the SocketTimeout property has passed. This return code is no longer used as of version 1.15.8. The return code 439 is delivered.
435	Java: Exitcode of natives could not be read (NOEXITCODE)
436	Java: DocumentServer: no asynchronous job result available after several tries (ASYNCRESULTMISSING)
437	Java: General exception (GENERALEXCEPTION)
441	SocketServer: Too few or no arguments
442	SocketServer: Not allowed port number
443	SocketServer: CIB Job Library not available
444	SocketServer: Invalid Content Type
445	SocketServer: General error with description
446	SocketServer: General error
447	SocketServer: The url in the http header is invalid. Allowed are /job and /terminates
448	SocketServer: Idle Timeout reached
449	reserved for future use
450	ServerManager has received termination signal
451	ServerManager: Too few or no arguments
452	ServerManager: Wrong argument
453	ServerManager: Non-permitted port number
454	SocketServer: Maximum memory reached. See de.cib.docserv.socket.MaxMemory.
455	SocketServer: General error with description
456	SocketServer: General error
457	SocketServer should be (re)configured
458	SocketServer: Maximum memory reached. Error during allocation ("malloc()"). See en.cib.docserv.socket.MaxMemory.
459	SocketServer: Maximum working memory reached. Error during allocation ("new"). See de.cib.docserv.socket.MaxMemory.

The error code -72 always occurs when the number of jobs specified with de.cib.docserv.MaxJobCountPerProcess has been processed and thus the socket server processes are restarted. The log files of CIB job and CIB docgen are restarted and can be limited in size in this way.