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

PR raised for JBTM-3122 and JBTM-3132 #278

Closed
wants to merge 3 commits into from
Closed

PR raised for JBTM-3122 and JBTM-3132 #278

wants to merge 3 commits into from

Conversation

mayankkunwar
Copy link
Contributor

https://issues.redhat.com/browse/JBTM-3132
https://issues.redhat.com/browse/JBTM-3122

This PR changes includes a common profiles (one of such profile is Arquillian JDK9+ which defines JVM arguments needed for smooth run of tests, see https://issues.jboss.org/projects/JBTM/issues/JBTM-3122)

Refactoring of quickstarts to have the common parent

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

Copy link
Contributor

@ochaloup ochaloup left a comment

Choose a reason for hiding this comment

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

There is currently the trouble of the JDK11 execution with job being stuck at

20-Apr-2020 16:35:11.413 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
20-Apr-2020 16:35:11.421 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
20-Apr-2020 16:35:11.424 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 2095 ms
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     020-Apr-2020 16:35:18.737 INFO [http-nio-8080-exec-1] org.hibernate.jpa.internal.util.LogHelper.logPersistenceUnitInformation HHH000204: Processing PersistenceUnitInfo [
	name: quickstart-persistence-unit
	...]

100     5    0     0  100     5      0     49 --:--:-- --:--:-- --:--:--    49
curl: (22) The requested URL returned error: 500 

http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-quickstart-matrix/jdk=jdk11.latest,label=linux/4/console
Are you able to reproduce the failure on your local machine or is it only the CI trouble?

@mayankkunwar
Copy link
Contributor Author

There is currently the trouble of the JDK11 execution with job being stuck at

20-Apr-2020 16:35:11.413 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
20-Apr-2020 16:35:11.421 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
20-Apr-2020 16:35:11.424 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 2095 ms
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     020-Apr-2020 16:35:18.737 INFO [http-nio-8080-exec-1] org.hibernate.jpa.internal.util.LogHelper.logPersistenceUnitInformation HHH000204: Processing PersistenceUnitInfo [
	name: quickstart-persistence-unit
	...]

100     5    0     0  100     5      0     49 --:--:-- --:--:-- --:--:--    49
curl: (22) The requested URL returned error: 500 

http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-quickstart-matrix/jdk=jdk11.latest,label=linux/4/console
Are you able to reproduce the failure on your local machine or is it only the CI trouble?

Yes I am facing this problem locally as well. Is there any solution for this issue. I was unable to resolve this

@ochaloup
Copy link
Contributor

@mayankkunwar hm... that's a question, I'm not sure. It sounds like some jdk11 issue of not stopping the tomcat. Have you tried to investigate the tomcat log (maybe it would be good to find a way how to get some more tracing for that)? Could you try to investigate the tomcate threaddump at time when the test stuck? (is it in some shutdown process or something?) Could you try to check if there is some information what tomcat version is supported on jdk11? (Maybe we just use an old version and we need to update of the tomcat version or just skipping the test for the jdk11 - btw. you could try to start only the tomcat in the version with the simple bash command and check if you are able to stop it with the expected way on jdk11. and you could try on a newer version the same and compare if the results are the same as for tests and the version update helps)

@mayankkunwar
Copy link
Contributor Author

@mayankkunwar hm... that's a question, I'm not sure. It sounds like some jdk11 issue of not stopping the tomcat. Have you tried to investigate the tomcat log (maybe it would be good to find a way how to get some more tracing for that)? Could you try to investigate the tomcate threaddump at time when the test stuck? (is it in some shutdown process or something?) Could you try to check if there is some information what tomcat version is supported on jdk11? (Maybe we just use an old version and we need to update of the tomcat version or just skipping the test for the jdk11 - btw. you could try to start only the tomcat in the version with the simple bash command and check if you are able to stop it with the expected way on jdk11. and you could try on a newer version the same and compare if the results are the same as for tests and the version update helps)

Okay I will try it, Thanks

@mayankkunwar
Copy link
Contributor Author

@mayankkunwar hm... that's a question, I'm not sure. It sounds like some jdk11 issue of not stopping the tomcat. Have you tried to investigate the tomcat log (maybe it would be good to find a way how to get some more tracing for that)? Could you try to investigate the tomcate threaddump at time when the test stuck? (is it in some shutdown process or something?) Could you try to check if there is some information what tomcat version is supported on jdk11? (Maybe we just use an old version and we need to update of the tomcat version or just skipping the test for the jdk11 - btw. you could try to start only the tomcat in the version with the simple bash command and check if you are able to stop it with the expected way on jdk11. and you could try on a newer version the same and compare if the results are the same as for tests and the version update helps)

Okay I will try it, Thanks

@ochaloup I tried to run JDK11 with some different tomcat versions like, it is already running with 9.0.7, I tried it with 9.0.14, 9.0.33 and 9.0.34, but still point of failure is same.

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@mayankkunwar
Copy link
Contributor Author

Closing this PR due to rebase issue.

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.

3 participants