Skip to content
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

Unsatisfied dependency for type io.vertx.db2client.DB2Pool and qualifiers with Quarkus master, works with 1.8.0.Final #12043

Closed
rsvoboda opened this issue Sep 11, 2020 · 5 comments · Fixed by #12051
Assignees
Labels
area/persistence OBSOLETE, DO NOT USE kind/bug Something isn't working
Milestone

Comments

@rsvoboda
Copy link
Member

I see Unsatisfied dependency for type io.vertx.db2client.DB2Pool and qualifiers with Quarkus master (6588419) when running daily GH CI check on https://github.com/quarkus-qe/beefy-scenarios. Works well with 1.8.0.Final.

java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.arc.deployment.ArcProcessor#validate threw an exception: javax.enterprise.inject.spi.DeploymentException: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type io.vertx.db2client.DB2Pool and qualifiers [@Default]
	- java member: io.quarkus.reactive.db2.client.runtime.DB2PoolProducer#db2Pool
	- declared on CLASS bean [types=[java.lang.Object, io.quarkus.reactive.db2.client.runtime.DB2PoolProducer], qualifiers=[@Default, @Any], target=io.quarkus.reactive.db2.client.runtime.DB2PoolProducer]
	at io.quarkus.arc.processor.BeanDeployment.processErrors(BeanDeployment.java:1018)
	at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:238)
	at io.quarkus.arc.processor.BeanProcessor.initialize(BeanProcessor.java:122)
	at io.quarkus.arc.deployment.ArcProcessor.validate(ArcProcessor.java:393)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at io.quarkus.deployment.ExtensionLoader$2.execute(ExtensionLoader.java:936)
	at io.quarkus.builder.BuildContext.run(BuildContext.java:277)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:2046)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1578)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1452)
	at java.base/java.lang.Thread.run(Thread.java:834)
	at org.jboss.threads.JBossThread.run(JBossThread.java:479)
Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: Unsatisfied dependency for type io.vertx.db2client.DB2Pool and qualifiers [@Default]
	- java member: io.quarkus.reactive.db2.client.runtime.DB2PoolProducer#db2Pool
	- declared on CLASS bean [types=[java.lang.Object, io.quarkus.reactive.db2.client.runtime.DB2PoolProducer], qualifiers=[@Default, @Any], target=io.quarkus.reactive.db2.client.runtime.DB2PoolProducer]
	at io.quarkus.arc.processor.Beans.resolveInjectionPoint(Beans.java:504)
	at io.quarkus.arc.processor.BeanInfo.init(BeanInfo.java:363)
	at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:230)
	... 14 more

Reproducer (expecting Quarkus master was built beforehand):

git clone https://github.com/quarkus-qe/beefy-scenarios.git
cd beefy-scenarios
mvn clean verify -pl 002-quarkus-all-extensions  

Running with Quarkus 1.8.0.Final works fine (mvn clean verify -pl 002-quarkus-all-extensions/ -Dquarkus.platform.version=1.8.0.Final -Dquarkus-plugin.version=1.8.0.Final).

@rsvoboda rsvoboda added the kind/bug Something isn't working label Sep 11, 2020
@quarkusbot
Copy link

/cc @aguibert

@quarkusbot quarkusbot added the area/persistence OBSOLETE, DO NOT USE label Sep 11, 2020
@geoand
Copy link
Contributor

geoand commented Sep 11, 2020

@gsmet could this be because of the config change?

@gsmet
Copy link
Member

gsmet commented Sep 11, 2020

Yeah, it's related to that.

I fixed some other unrelated issue but this one I need to understand what's going on.

@gsmet
Copy link
Member

gsmet commented Sep 11, 2020

Yeah, so the reactive extensions have a bug that was hidden before that. I will fix it.

@geoand
Copy link
Contributor

geoand commented Sep 11, 2020

Cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/persistence OBSOLETE, DO NOT USE kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants