Skip to content

PLOSSYS Output Engine 6.1.1

New Features

  • Analog to the log messages of seal-checkout and seal-bodyscanner, the services seal-controller, seal-ghost and seal-copier log the end of input stream if all documents of a job have arrived. (PLS-2059)

  • PDF Tools have been updated to version 3.7.1. (PLS-2062)

  • The new environment key NO_RESPONSE_CHECK_INTERVAL specifies the intervall at which data streams are checked to see if they are still active. The key has a default value of 10m. (PLS-2072)

Bug-Fixes

  • The quality issue has been fixed when printing files with transparencies under Linux. (PLS-1987)

  • The bug has been fixed that caused the browser to freeze when copying entries from PLOSSYS Administrator. (PLS-2005)

  • The bug has been fixed, where seal-ghost service started a new Ghostscript process when attempting to print anew and the printer was not reachable, leading to a large amount of parallel running Ghostscript services. (PLS-2017)

  • The bug has been fixed that caused seal-checkout to crash saying "Cannot destructure property 'writableEnded'". (PLS-2072)

  • The bug has been fixed that caused seal-copier to crash saying "Unhandled rejection occurred" after seal-checkout returned an error status. (PLS-2073)

Known Issues

  • When changing the seal-island-checkout on a Windows client using the Repair option, default values will be written into the registry instead of the changed data. To prevent that issue, uninstall the current client first, then install anew. (PLS-1927)

  • When a key has been entered into Consul with leading or trailing spaces it can override the correct version of the key. (PLS-1985)

  • When updating from PLOSSYS 5 to PLOSSYS Output Engine 6.0.0 or higher under Linux, the directories for the old services seal-plossys-accounting and seal-plossys-message-relay will not be deleted. (PLS-1990)

  • The new job status added has no icon in PLOSSYS Administrator. (PLS-2000)

  • If a job fails because of errors in the printer language, the resulting error messages are missing in Elastic. (PLS-2014)

  • If a job name contains the word error, the job will always set to status error by seal-pjl-checkout service. (PLS-2015)

  • In very rare cases, if error events between streaming services get lost because of network issues and the other involved services do not close their streams, it can cause the job being stuck in the "… still waiting for response from follow up services" stage for a long time. Please cancel the job manually in such a case. (PLS-2050)

Back to top