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.

Sign up for GitHub

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

Jump to bottom

Tyrus doesn't install #865

Open
ddyer0 opened this issue Nov 9, 2023 · 10 comments
Open

Tyrus doesn't install #865

ddyer0 opened this issue Nov 9, 2023 · 10 comments

Comments

@ddyer0
Copy link

ddyer0 commented Nov 9, 2023

Following the recommentation, "mvn clean install" on version 2.1.4 fails in the "glassfish test" phase.
[INFO] Tyrus Servlet Basic Tests .......................... SUCCESS [ 13.477 s]
[INFO] Tyrus Servlet Tests on Glassfish ................... FAILURE [ 12.022 s]
[INFO] Tyrus Servlet Dynamic Deploy Test .................. SKIPPED

I followed a few breadcrumbs which led me to this error message
http://www.w3.org/2001/XMLSchema-instance

which apparently decodes to "don't do this"

my platform is windows 11 java 16
@jansupol
Copy link
Contributor

jansupol commented Nov 9, 2023

I have not experienced this issue. Could you share more details?

With Glassfish, there could be some issue that is not visible directly with the maven run and the Glassfish server log needs to be examined. The log would be located in ${target}/glassfish7/glassfish/domains/domain1/logs.

Regarding the issue topic, Tyrus should be installed, no matter the failed tests. If the goal was to install Tyrus, I believe you should have it in your local m2 repository.

I do not follow the error message http://www.w3.org/2001/XMLSchema-instance, can you elaborate?

@jansupol
Copy link
Contributor

jansupol commented Nov 9, 2023

It looks like the Tyrus build can also be affected by various maven versions, we use rather older versions. I will try newer ones to see some differences.

@ddyer0
Copy link
Author

ddyer0 commented Nov 9, 2023 via email

@jansupol
Copy link
Contributor

There is nothing to be seen in the maven log. More information could either be in the target\failsafe-reports or the Glassfish server log.

@ddyer0
Copy link
Author

ddyer0 commented Nov 10, 2023

there is no target\failsafe-reports
where would I find the glassfish log?

@jansupol
Copy link
Contributor

With Glassfish, there could be some issue that is not visible directly with the maven run and the Glassfish server log needs to be examined. The log would be located in ${target}/glassfish7/glassfish/domains/domain1/logs.

@ddyer0
Copy link
Author

ddyer0 commented Nov 10, 2023 via email

@ddyer0
Copy link
Author

ddyer0 commented Nov 10, 2023 via email

@ddyer0
Copy link
Author

ddyer0 commented Nov 10, 2023

I killed the process using port 8080 and the install got a lot further. It still failed with this complaint:
INFO: Stopped listener bound to [0.0.0.0:8025]
Nov 10, 2023 1:37:41 PM org.glassfish.tyrus.server.Server stop
INFO: Websocket Server stopped.
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.142 s -- in org.glassfish.tyrus.test.standard_config.userproperties.UserPropertiesTest
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] HeartbeatTest.testSessionTimeout:160
[INFO]
[ERROR] Tests run: 189, Failures: 1, Errors: 0, Skipped: 6
[INFO]

@jansupol
Copy link
Contributor

HeartBeatTest is a bit flaky, sometimes it fails with a timeout, as the test did not finish in time. That happens especially on a busy machine where another process takes a lot of CPU. In that case, the test just needs to be run again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ddyer0 @jansupol