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

Docker Image Build Failure in Micro Gateway Toolkit 73 Update Due to Jersey Library Update #3522

Closed
maneeshaheshan opened this issue Jan 13, 2025 · 0 comments
Labels

Comments

@maneeshaheshan
Copy link

maneeshaheshan commented Jan 13, 2025

Description

Hi Team,

The Docker image build is failing with the following error stack trace when attempting to build a Micro Gateway project using the 73 updated (latest version) Micro Gateway Toolkit:

./micro-gw build my-test --docker-image wso2microgw:wso2mgw-mocky-3.2.10.1 --docker-base-image docker.wso2.com/wso2micro-gw:3.2.10.1
JAVA_HOME: /Users/Test1/JDK/zulu17.46.19-ca-jdk17.0.9-macosx_aarch64/zulu-17.jdk/Contents/Home
Generating sources...[DONE]
Compiling source
	wso2/my-test:3.2.0

Creating balos
	target/balo/my-test-2020r1-java8-3.2.0.balo

Running Tests
	wso2/my-test:3.2.0
	No tests found

Generating executables
	target/bin/my-test.jar

Generating docker artifacts...
Exception in thread "docker-java-stream-1307272143" java.lang.NoSuchMethodError: 'void org.glassfish.jersey.client.ClientExecutorProvidersConfigurator.registerExecutors(org.glassfish.jersey.internal.inject.InjectionManager, org.glassfish.jersey.model.internal.ComponentBag, org.glassfish.jersey.spi.ExecutorServiceProvider, org.glassfish.jersey.spi.ScheduledExecutorServiceProvider)'
	at org.glassfish.jersey.client.ClientExecutorProvidersConfigurator.init(ClientExecutorProvidersConfigurator.java:139)
	at org.glassfish.jersey.client.ClientConfig$State.initRuntime(ClientConfig.java:447)
	at org.glassfish.jersey.internal.util.collection.Values$LazyValueImpl.get(Values.java:317)
	at org.glassfish.jersey.client.ClientConfig.getRuntime(ClientConfig.java:807)
	at org.glassfish.jersey.client.ClientRequest.getClientRuntime(ClientRequest.java:219)
	at org.glassfish.jersey.client.ClientRequest.getInjectionManager(ClientRequest.java:610)
	at org.glassfish.jersey.client.JerseyWebTarget.onBuilder(JerseyWebTarget.java:364)
	at org.glassfish.jersey.client.JerseyWebTarget.request(JerseyWebTarget.java:192)
	at org.glassfish.jersey.client.JerseyWebTarget.request(JerseyWebTarget.java:36)
	at com.github.dockerjava.jaxrs.JerseyDockerHttpClient.execute(JerseyDockerHttpClient.java:295)
	at com.github.dockerjava.core.DefaultInvocationBuilder.execute(DefaultInvocationBuilder.java:228)
	at com.github.dockerjava.core.DefaultInvocationBuilder.lambda$executeAndStream$1(DefaultInvocationBuilder.java:269)
	at java.base/java.lang.Thread.run(Thread.java:840)

Based on the error trace, the issue appears to be related to the org.glassfish.jersey package. Upon investigation, we identified that the version update applied to this library was introduced in update 73 on 2024-11-21.

When we attempted to build the Docker image using the 72 updated Micro Gateway Toolkit, the issue was not observed. This suggests the problem is directly caused by the version update of the Jersey library.

Steps to Reproduce

.

Version

wso2am-micro-gw-3.2.0

Environment Details (with versions)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant