-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
payara-3696-acc-executor-service #3936
payara-3696-acc-executor-service #3936
Conversation
Signed-off-by: arjantijms <[email protected]>
Signed-off-by: arjantijms <[email protected]>
Jenkins test please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm afraid this may lead to null pointer exceptions down the road at other places.
What about if the service hosted its own default config when attempts to inject it fail?
I think we'd seen those already then, as initialisation was already skipped, just with an NPE before. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Are there tests planned to make sure this runs without exceptions?
Signed-off-by: arjantijms <[email protected]>
Jenkins test please |
TimeUnit.valueOf(payaraExecutorServiceConfiguration.getThreadPoolExecutorKeepAliveTimeUnit()), | ||
new LinkedBlockingQueue<>(threadPoolExecutorQueueSize), | ||
(Runnable r) -> new Thread(r, "payara-executor-service-task")); | ||
0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to move the configured properties to local variables and override them if isAcc passes?
fixes for Eclipse Jenkins environment (adaptopenjdk, shell etc)
Payara-3696 Don't init executor service when in ACC
Hint for reviewers; review per individual commit. The first commit is adding a debug option to the ACC start, since it's otherwise quite difficult to debug the agent code for the ACC.
The second commit fixes the exception during startup of the ACC by not initialising the executor service on the client-side.