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

APIs not found #708

Closed
margaretha opened this issue Nov 17, 2023 · 2 comments
Closed

APIs not found #708

margaretha opened this issue Nov 17, 2023 · 2 comments
Milestone

Comments

@margaretha
Copy link
Contributor

margaretha commented Nov 17, 2023

The web-services cannot be found after upgrading to Jersey 3. The server doesn't run properly, although the test suite run well.

@margaretha margaretha added this to the 0.72 milestone Nov 17, 2023
@margaretha
Copy link
Contributor Author

The problem was caused by Shutdownhandler trying to shutdown any running instances at start. Setting the parameter sendShutdownAtStart fixes the problem. However, we may get rid of this handler since it is not really used and necessary.

Besides, there are some errors regarding jakarta validation that require additional libraries: hibernate-validator and jakarta.el. Strangely, the errors didn't occur when running the test suite.

@margaretha
Copy link
Contributor Author

margaretha commented Nov 27, 2023

The problem is also related to multi-release jar, see #706 . Maven-shade-plugin unpack dependency jars and repacks them, but it doesn't use the correct java version for Jersey-Spring ext so Spring dependency injection doesn't work. Without specifying <Multi-Release>true</Multi-Release>, it gets Java 11 from a multi-release jar.

@margaretha margaretha reopened this Nov 27, 2023
idsgerrit pushed a commit that referenced this issue Dec 22, 2023
Change-Id: I97d70dde790a3838962f0ffe270b9b1d8595a489
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

No branches or pull requests

1 participant