Cannot release updated Job Templates in JS7 2.8.2

I've updated an already released job template and clicked "Release" then, but the only result I get is a NullPointerException.
In the joc.log, I can see:

REQUEST: ./inventory/release
PARAMS: {"includeLate":false,"update":[{"path":"/repo/my-template","objectType":"JOBTEMPLATE"}],"auditLog":{}}
USER: Foo Bar
2026-01-05T13:33:07,486 ERROR qtp1967892594-21929  c.s.j.c.JOCDefaultResponse                   - java.lang.NullPointerException
java.lang.NullPointerException: null
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197) ~[?:?]
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625) ~[?:?]
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) ~[?:?]
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) ~[?:?]
        at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150) ~[?:?]
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173) ~[?:?]
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?]
        at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596) ~[?:?]
        at com.sos.joc.inventory.dependencies.util.DependencyUtils.resolveReferences(DependencyUtils.java:45) ~[sos-webservices-joc-2.8.2.jar:?]
        at com.sos.joc.inventory.impl.ReleaseResourceImpl.checkDependencies(ReleaseResourceImpl.java:1002) ~[sos-webservices-joc-2.8.2.jar:?]
        at com.sos.joc.inventory.impl.ReleaseResourceImpl.release(ReleaseResourceImpl.java:136) ~[sos-webservices-joc-2.8.2.jar:?]
        at com.sos.joc.inventory.impl.ReleaseResourceImpl.getReleaseResponse(ReleaseResourceImpl.java:112) ~[sos-webservices-joc-2.8.2.jar:?]
        at com.sos.joc.inventory.impl.ReleaseResourceImpl.release(ReleaseResourceImpl.java:103) ~[sos-webservices-joc-2.8.2.jar:?]
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
....

This was not an issue with 2.8.1.

UPDATE: Just noticed that also other elements cannot be released: Calendars, Schedules, ... (Workflow deployment still works)

Hello Daniel,
thank you for the information.

I have created a Jira Issue for this which you can track here:
https://change.sos-berlin.com/browse/JOC-2161

With https://change.sos-berlin.com/browse/JOC-2136 we have optimized the proccesing of dependencies dramatically (performance and stability). Unfortunately, dependencies that have been determined before the change in 2.8.2 sometimes do not contain references which leads to the NPE you experienced.

• Workaround 1:
• As described also in the Jira Issue you can deactivate the processing of dependencies on release. Set the "Include Dependencies" Radio Button in the Release Window to "none" and you should be able to re-release your JobTemplate.
• Workaround 2:
• The issue occurs most probably because you have some dependencies in your database that have been determined with an older version of JOC (before 2.8.2). To update those dependencies you can call "Update Dependencies" from the context menu of the tree on root level (only). This will take some time as it depends on the number of objects you have in your environment. It will update all determined dependencies asynchronously in the background. After that you should be able to re-release any objects without errors.

Best Regards
Santiago

Hello Santiago,

Thank you for your response. Unfortunately, this did not help:

• I've faced the same problem when using the "None" option.
• I've also tried "Update Dependencies" - no effect.
• I've tried it with a completely new object (a script include without any dependencies) - same result.

Any other hints how to determine the reason?

Best regards,
Daniel

Hello Santiago,
can you recommend some logging options to get more insights with logging options? I've already tried some settings but the results did not help a lot.
Or, what would you need so you are able to reproduce it?

Best regards,
Daniel

Hello Daniel,
I can now confirm that the problem is definitely related to dependencies determined with a 2.7.x version after upgrading to 2.8.2.
We have revisited the workaround 2 : "Update Dependencies" and found that while all still existing items are properly updated, other entries, e.g. dependencies related to already removed items haven´t been cleaned up properly, still linger in the dependencies table of the database and block the process for all other items, too.

I can also confirm now an adjusted and working workaround, so that you don´t need to wait any longer for the upcoming release to get rid of the problem.
It works as follow:

• Step 1: Enter your database and truncate the table INV_DEPENDENCIES.
• Step 2: In JOC call "Update Dependencies" from the context menu of the tree on root level

Best Regards
Santiago

Hello Santiago,
thank you for the hint - I was now able to release objects again in our upgraded 2.8.2 instance.
Best regards
Daniel