Andreas

JS7 JobScheduler LTS Release 2.8.3 available

Hi Nassem, you are most probably hit by JOC-2161: Release of any releaseable Object should work without errors Please, consider the workaround for release 2.8.2 mentioned with above issue. The fix becomes available with release 2.8.3 that ships later in the day.

Hi Marcos, thank you, log output confirms the problem that is addressed with the issue JOC-2183: Incompatible dependencies raise NullPointerException The workaround is indicated with the issue, the fix will become available with release 2.8.3. Best regards Andreas

Hello Andreas, Thank you very much for your reply. I followed the procedures you sent me, and the error has been resolved. This was a lifesaver! I am forwarding three JOC log files for your analysis. Please let me know if you need any further information or additional steps. Best regards,

NullPointerException

Hi Marcos, please, forward the log output that you received when the error occurs. We are particularly interested in the stacktrace created from the NullPointerException. As an immediate measure, proceed as follows: Shutdown JOC Cockpit and delete all records in table INV_DEPENDENCIES. Start JOC Cockpit. In the Inventory view, use the 3-dots action menu of the root folder and perform the operation "update dependencies". It might take a few minutes to re-create dependencies, time consumption is related...

You are right, the docs are wrong. We changed the docs to indicate that this is a must.

Hi John, check your Agent's <agent-data>/config/agent.conf file if it holds the entry js7.journal.cluster.node.is-backup=yes If available, remove the setting. It makes an Agent the default standby node in an Agent Cluster. When using installer scripts such as js7_install_agent.sh (Install-JS7Agent.ps1) then the related command line switch that will create the setting is --Standby. After removal delete the <agent-data>/state directory as it persists the Agent's standby role. The directory will be...