Skip to content

porting fix for class analyzer#6096

Closed
breakponchito wants to merge 2 commits into
eclipse-ee4j:3.1.12-BRANCHfrom
breakponchito:ClassAnalyzer-race-condition-3.x
Closed

porting fix for class analyzer#6096
breakponchito wants to merge 2 commits into
eclipse-ee4j:3.1.12-BRANCHfrom
breakponchito:ClassAnalyzer-race-condition-3.x

Conversation

@breakponchito

Copy link
Copy Markdown

This is a PR to port the fix for ClassAnalyzer issue. Here the original PR: #6049

I replicated this using glassfish 7.1.0 that is using the jersey version 3.1.11. Here the logs after reproducing the error:

[2026-06-25T19:42:11.043412-06:00] [GF 7.1.0] [WARNING] [] [org.glassfish.jersey.internal.Errors] [tid: _ThreadID=135 _ThreadName=http-listener-1(4)] [levelValue: 900] [[
  The following warnings have been detected: WARNING: HK2 failure has been detected in a code that does not run in an active Jersey Error scope.
WARNING: Unknown HK2 failure detected:
MultiException stack 1 of 1
java.lang.IllegalStateException: Could not find an implementation of ClassAnalyzer with name CdiInjecteeSkippingClassAnalyzer
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getAnalyzer(ServiceLocatorImpl.java:2500)
	at org.jvnet.hk2.internal.Utilities.getClassAnalyzer(Utilities.java:145)
	at org.jvnet.hk2.internal.Utilities.justInject(Utilities.java:971)
	at org.jvnet.hk2.internal.ServiceLocatorImpl.inject(ServiceLocatorImpl.java:1026)
	at org.glassfish.jersey.inject.hk2.AbstractHk2InjectionManager.inject(AbstractHk2InjectionManager.java:217)
	at org.glassfish.jersey.inject.hk2.ImmediateHk2InjectionManager.inject(ImmediateHk2InjectionManager.java:30)
	at org.glassfish.jersey.ext.cdi1x.internal.CdiComponentProvider$InjectionManagerInjectedCdiTarget.inject(CdiComponentProvider.java:679)
	at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:165)

I based this PR from the branch 3.1.12-BRANCH, I hope this is correct

@dmatej

dmatej commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Unfortunately it seems I closed your PR - the target branch should have been 3.x, not the release branch of 3.1.12 (which I deleted yesterday). Can you create the PR again from the same branch, or can I do that for you, just using your commits?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants