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

Enable vertx-websocket extension to handle Quarkus TLS Registry configuration #6420

Conversation

jamesnetherton
Copy link
Contributor

Relates to #6393.

@jamesnetherton jamesnetherton force-pushed the vertx-websocket-tls-registry-support branch from 991ed53 to 372852a Compare September 4, 2024 08:49
@zhfeng
Copy link
Contributor

zhfeng commented Sep 4, 2024

Well done!

@jamesnetherton
Copy link
Contributor Author

One of the example projects uncovers an issue that I need to fix (strange it does not happen in the main project test suite).

Caused by: jakarta.enterprise.inject.CreationException: Error creating synthetic bean [DBlwsZyrCioOGVZEX1uhn5gHUe0]: jakarta.enterprise.inject.CreationException: Synthetic bean instance for io.quarkus.tls.TlsConfigurationRegistry not initialized yet: io_quarkus_tls_TlsConfigurationRegistry_c3690e7f4866a79befda78c4c24a5b11fe6d5e3a
	- a synthetic bean initialized during RUNTIME_INIT must not be accessed during STATIC_INIT
	- RUNTIME_INIT build steps that require access to synthetic beans initialized during RUNTIME_INIT should consume the SyntheticBeansRuntimeInitBuildItem
	at io.quarkus.tls.TlsConfigurationRegistry_DBlwsZyrCioOGVZEX1uhn5gHUe0_Synthetic_Bean.doCreate(Unknown Source)
	at io.quarkus.tls.TlsConfigurationRegistry_DBlwsZyrCioOGVZEX1uhn5gHUe0_Synthetic_Bean.create(Unknown Source)
	at io.quarkus.tls.TlsConfigurationRegistry_DBlwsZyrCioOGVZEX1uhn5gHUe0_Synthetic_Bean.create(Unknown Source)
	at io.quarkus.arc.impl.AbstractSharedContext.createInstanceHandle(AbstractSharedContext.java:119)
	at io.quarkus.arc.impl.AbstractSharedContext$1.get(AbstractSharedContext.java:38)
	at io.quarkus.arc.impl.AbstractSharedContext$1.get(AbstractSharedContext.java:35)
	at io.quarkus.arc.impl.LazyValue.get(LazyValue.java:32)
	at io.quarkus.arc.impl.ComputingCache.computeIfAbsent(ComputingCache.java:69)
	at io.quarkus.arc.impl.ComputingCacheContextInstances.computeIfAbsent(ComputingCacheContextInstances.java:19)
	at io.quarkus.arc.impl.AbstractSharedContext.get(AbstractSharedContext.java:35)
	at io.quarkus.tls.TlsConfigurationRegistry_DBlwsZyrCioOGVZEX1uhn5gHUe0_Synthetic_Bean.get(Unknown Source)
	at io.quarkus.tls.TlsConfigurationRegistry_DBlwsZyrCioOGVZEX1uhn5gHUe0_Synthetic_Bean.get(Unknown Source)
	at io.quarkus.arc.impl.InstanceImpl.getBeanInstance(InstanceImpl.java:325)
	at io.quarkus.arc.impl.InstanceImpl.getInternal(InstanceImpl.java:309)
	at io.quarkus.arc.impl.InstanceImpl.get(InstanceImpl.java:190)
	at io.quarkus.arc.InjectableInstance.orElse(InjectableInstance.java:71)
	at io.quarkus.arc.InjectableInstance.orNull(InjectableInstance.java:82)
	at org.apache.camel.quarkus.component.vertx.websocket.VertxWebsocketRecorder.httpServerTlsRegistryConfigurationExists(VertxWebsocketRecorder.java:79)

@jamesnetherton jamesnetherton force-pushed the vertx-websocket-tls-registry-support branch from 372852a to 2f6fbb6 Compare September 4, 2024 11:43
@jamesnetherton
Copy link
Contributor Author

Issues should be fixed in the latest commit.

@jamesnetherton jamesnetherton merged commit a9bee1b into apache:main Sep 4, 2024
24 checks passed
@jamesnetherton jamesnetherton deleted the vertx-websocket-tls-registry-support branch September 4, 2024 13:08

@TestCertificates(certificates = {
@Certificate(name = "vertx-websocket", formats = {
Format.PKCS12, Format.PEM }, password = "changeit") })
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we use the PKCS12 format somewhere? I see just the PEM one being used below.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

4 participants