Actions
Bug #25306
closed
NuProcessHandler.onStart NPE log message
Status:
Released
Priority:
N/A
Assignee:
Category:
Architecture - Code maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
From time to time, we see a nuprocess log like that:
Cannot invoke "com.zaxxer.nuprocess.NuProcessHandler.onStart(com.zaxxer.nuprocess.NuProcess)" because "this.processHandler" is null
This is tracked in nu process in that PR: https://github.com/brettwooldridge/NuProcess/pull/158 which is corrected, but without a release for now (ie, it is merged on master and will go in the next 2.0.7 or 2.1.0 version).
I was able to locally build and test the correction, which seems to work as expected.
Updated by Vincent MEMBRÉ 3 months ago
- Target version changed from 8.1.7 to 8.1.8
Updated by François ARMAND 3 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 3 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/5907
Updated by Anonymous 3 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|0271796b2f63bc808e4c8efab8cde8b5e58b638a.
Updated by François ARMAND about 2 months ago
- Fix check changed from To do to Checked
I didn't see any new problem. I tried to add hooks which does nothing appart exit 0 (they were the ones where I saw the problem before) and no error now.
Hooks and other things using NuProcess work.
Updated by Vincent MEMBRÉ about 1 month ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.
Actions