[JBoss JIRA] (JBTM-1807) Participant's terminator resource cannot be found in TXF REST-AT tests
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1807?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1807:
---------------------------------------
http://172.17.131.2/job/btny-pulls-narayana/788
> Participant's terminator resource cannot be found in TXF REST-AT tests
> ----------------------------------------------------------------------
>
> Key: JBTM-1807
> URL: https://issues.jboss.org/browse/JBTM-1807
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Critical
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> http://172.17.131.2/job/btny-pulls-narayana/781
> http://172.17.131.2/job/btny-pulls-narayana/784
> {code}
> [0m[33m13:17:34,469 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-7) failed to execute: javax.ws.rs.NotFoundException: Could not find resource for full path: http://localhost:8080/test/2/0_ffffac118307_1f9721a3_51cadbd7_19/1/termin...
> at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:111) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.1.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:138) [undertow-websockets-jsr-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:115) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:131) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:118) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:94) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:629) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka resolved JBTM-1778.
------------------------------------
Resolution: Done
It is supposed that the issue was solved. Problem was solved with adjusting test configuration.
As Tom mentioned the problem was caused by the fact that the reaper was timing out and destroying transactions.
The problematic tests were run and redefinition of test configuration (via sed) was done in job here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui...
The main change was to redefine timeouts via jvm_param under individual test runs. It was added in way like this:
{code}
<start_task>
...
<jvm_param>-Dcom.arjuna.ats.arjuna.coordinator.defaultTimeout=360</jvm_param>
<jvm_param>-Dcom.arjuna.ats.jts.defaultTimeout=360</jvm_param></start_task>
{code}
But the minor problem remained for OTS server test where the timeout was not sufficient for smooth run and the number of coordinators had to be changed anyway.
> JBossTS qa testsuite fails on HP-UX
> -----------------------------------
>
> Key: JBTM-1778
> URL: https://issues.jboss.org/browse/JBTM-1778
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.6.1.CP13
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Attachments: jstack-3091
>
>
> Hi Michael,
> as part of the EAP5.2.0 certification tests running on HP-UX 11v3 machines.
> I've hit problems with several testcases in the ts testsuite.
> We are testing on machines under this tag: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/hpux11v3/
> As I think that you know the testsuite the most I'm assigning this issue to you. If I've mistaken, please, reassign it.
> Those are:
> - jbossts-qa-currenttests01 number 20 stays stuck forever. It stays on current.resume call. I'm adding the jstack output, that I've got from the call, as attachment here.
> - jbossts-qa-jtatests01 number 005 fails with error message:
> java.lang.Exception: Test failed! JTATests01_Test005 got 1 fewer task passes than expected
> - jbossts-qa-otsserver number 010, 011, 012 and 017 fail with the error
> got 1 fewer task passes than expected
> I've tried to get some closer knowledge about the problem but I wasn't able much.
> Others tests from testsuite pass fine without error. Just their run time is longer in comparison with testsuite running on RHEL.
> We are running tests on jdk6 and jdk7 on 32bits and 64bits. These particular results belong to jdk6 and 32b.
> The jenkins run could be found at:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui...
> Would you have some suggestion about this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1763) Consider running the QA tests in parrallel
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1763?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1763:
-------------------------------------
This is just one possible solution to the problem of the long test duration. We should wait for JBTM-1808 before deciding what to do with this issue.
> Consider running the QA tests in parrallel
> ------------------------------------------
>
> Key: JBTM-1763
> URL: https://issues.jboss.org/browse/JBTM-1763
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Paul Robinson
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> The QA tests currently take 5hrs to run per orb. This constitutes 83% of our CI run time.
> My understanding is that the time is mostly taken up in Thread.sleep. The test times range from 1 to 99seconds. So there are no major hotspots. The problem is that there are so many tests.
> I suspect we could run these tests in parallel to make better utilisation of resources.
> The tests don't run in an AS, but they do acquire ports. There may be other restrictions that make running them in parallel hard or impossible.
> It would be easier to simply carve up the tests into, say 5 parts per orb and have CI do the parallelism. However, this will consume more CI nodes than if we ran them in parallel on a single node.
> I think it would be worth investigating if we can run the tests in n batches (say n=10 initially, but should be configurable). Where each batch runs with a different port configuration. This may prove too disruptive to the tests,
> and also more bother than it is worth. Maybe we could do an initial investigation to see if this has legs?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1808) Investigate why QA tests take 5hrs to run per ORB
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1808:
-----------------------------------
Summary: Investigate why QA tests take 5hrs to run per ORB
Key: JBTM-1808
URL: https://issues.jboss.org/browse/JBTM-1808
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System, Testing
Reporter: Paul Robinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.M4
Our full build and test suite takes 12hrs to run. This is causing severe strain on our CI resources.
Out of this 12hrs, 10hrs is consumed by the QA test suite (5hrs per orb). It would be good to understand where this time is spent so that we can hopefully bring the test time down.
If there is no reasonable way to bring the timing down, we could chop the tests up into 5 groups (per orb) taking 1hr each. This would make better use of our CI cluster during quiet periods, but will not eleviate the load during busy periods. It is also likely to be a poor usage of resources as I suspect the CPU utilisation of each job will be low.
I suspect the problem is that we have a lot of Thread.sleeps in the tests. Therefore we are likely to see long tests with low resource (CPU) utilisation. However, further investigation is required to understand where the time is spent.
As an initial investigation, it would be good to profile the CPU utilisation on one of the CI nodes (take it offline) whilst running these tests. Also, it would be handy to find out how much time is spent in a Thread.sleep call (assuming that is where the time is spent).
My understanding is that Thread.sleep is used to wait for certain background tasks to complete. It's likely that Byteman could be used to replace the sleeps. However, due to the number of tests this may not be feasible. Alternatively, we may discover that there is a common set of Byteman rules that could be applied to the majority of tests, which may prove "good enough".
Also, we may be able to run these tests in parallel. This could drive up CPU utilisation, but would probably also interfere with the timings of the tests meaning that the current thread.sleeps are no longer adequate.
To summarise, this is a general task to investigate why the tests take so long and to also come up with some candidate solutions to bring the total test duration down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1808) Investigate why QA tests take 5hrs to run per ORB
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1808?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1808:
-------------------------------------
Tom,
I was thinking that this would be good for Amos to investigate. Can you add any ideas you may have to the above text and then assign accordingly?
> Investigate why QA tests take 5hrs to run per ORB
> -------------------------------------------------
>
> Key: JBTM-1808
> URL: https://issues.jboss.org/browse/JBTM-1808
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Paul Robinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> Our full build and test suite takes 12hrs to run. This is causing severe strain on our CI resources.
> Out of this 12hrs, 10hrs is consumed by the QA test suite (5hrs per orb). It would be good to understand where this time is spent so that we can hopefully bring the test time down.
> If there is no reasonable way to bring the timing down, we could chop the tests up into 5 groups (per orb) taking 1hr each. This would make better use of our CI cluster during quiet periods, but will not eleviate the load during busy periods. It is also likely to be a poor usage of resources as I suspect the CPU utilisation of each job will be low.
> I suspect the problem is that we have a lot of Thread.sleeps in the tests. Therefore we are likely to see long tests with low resource (CPU) utilisation. However, further investigation is required to understand where the time is spent.
> As an initial investigation, it would be good to profile the CPU utilisation on one of the CI nodes (take it offline) whilst running these tests. Also, it would be handy to find out how much time is spent in a Thread.sleep call (assuming that is where the time is spent).
> My understanding is that Thread.sleep is used to wait for certain background tasks to complete. It's likely that Byteman could be used to replace the sleeps. However, due to the number of tests this may not be feasible. Alternatively, we may discover that there is a common set of Byteman rules that could be applied to the majority of tests, which may prove "good enough".
> Also, we may be able to run these tests in parallel. This could drive up CPU utilisation, but would probably also interfere with the timings of the tests meaning that the current thread.sleeps are no longer adequate.
> To summarise, this is a general task to investigate why the tests take so long and to also come up with some candidate solutions to bring the total test duration down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1807) Participant's terminator resource cannot be found in TXF REST-AT tests
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1807?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1807:
----------------------------------
Description:
http://172.17.131.2/job/btny-pulls-narayana/781
http://172.17.131.2/job/btny-pulls-narayana/784
{code}
[0m[33m13:17:34,469 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-7) failed to execute: javax.ws.rs.NotFoundException: Could not find resource for full path: http://localhost:8080/test/2/0_ffffac118307_1f9721a3_51cadbd7_19/1/termin...
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:111) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.1.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:138) [undertow-websockets-jsr-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:115) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:131) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:118) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:94) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:629) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
{code}
was:
http://172.17.131.2/job/btny-pulls-narayana/784/artifact/txframework/targ...
{code}
[0m[33m13:17:34,469 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-7) failed to execute: javax.ws.rs.NotFoundException: Could not find resource for full path: http://localhost:8080/test/2/0_ffffac118307_1f9721a3_51cadbd7_19/1/termin...
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:111) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.1.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:138) [undertow-websockets-jsr-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:115) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:131) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:118) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:94) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:629) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
{code}
> Participant's terminator resource cannot be found in TXF REST-AT tests
> ----------------------------------------------------------------------
>
> Key: JBTM-1807
> URL: https://issues.jboss.org/browse/JBTM-1807
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Critical
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> http://172.17.131.2/job/btny-pulls-narayana/781
> http://172.17.131.2/job/btny-pulls-narayana/784
> {code}
> [0m[33m13:17:34,469 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-7) failed to execute: javax.ws.rs.NotFoundException: Could not find resource for full path: http://localhost:8080/test/2/0_ffffac118307_1f9721a3_51cadbd7_19/1/termin...
> at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:111) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.1.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:138) [undertow-websockets-jsr-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:115) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:131) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:118) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:94) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:629) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1807) Participant's terminator resource cannot be found in TXF REST-AT tests
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1807?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1807:
---------------------------------------
http://172.17.131.2/job/btny-pulls-narayana/778
> Participant's terminator resource cannot be found in TXF REST-AT tests
> ----------------------------------------------------------------------
>
> Key: JBTM-1807
> URL: https://issues.jboss.org/browse/JBTM-1807
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Critical
> Fix For: 5.0.0.M4
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> http://172.17.131.2/job/btny-pulls-narayana/781
> http://172.17.131.2/job/btny-pulls-narayana/784
> {code}
> [0m[33m13:17:34,469 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-7) failed to execute: javax.ws.rs.NotFoundException: Could not find resource for full path: http://localhost:8080/test/2/0_ffffac118307_1f9721a3_51cadbd7_19/1/termin...
> at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:111) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.1.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:138) [undertow-websockets-jsr-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:115) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:131) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:118) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:94) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:629) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1807) Participant's terminator resource cannot be found in TXF REST-AT tests
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1807:
-------------------------------------
Summary: Participant's terminator resource cannot be found in TXF REST-AT tests
Key: JBTM-1807
URL: https://issues.jboss.org/browse/JBTM-1807
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Priority: Critical
Fix For: 5.0.0.M4
http://172.17.131.2/job/btny-pulls-narayana/784/artifact/txframework/targ...
{code}
[0m[33m13:17:34,469 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-7) failed to execute: javax.ws.rs.NotFoundException: Could not find resource for full path: http://localhost:8080/test/2/0_ffffac118307_1f9721a3_51cadbd7_19/1/termin...
at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:111) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.1.Final.jar:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.1.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:138) [undertow-websockets-jsr-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:56) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:115) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at org.wildfly.extension.undertow.security.SecurityContextCreationHandler.handleRequest(SecurityContextCreationHandler.java:54)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:131) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:118) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:47) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:94) [undertow-servlet-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:629) [undertow-core-1.0.0.Alpha22.jar:1.0.0.Alpha22]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1749:
-------------------------------------
Amos,
Can you take a look at this at some point. It seems like it is reproducible on Linux, so it no longer has to be resolved by a Mac user.
I've set it as a low priority as Mark documented the workaround in the release notes.
> Failure building Javadoc when JAVA_HOME is empty
> ------------------------------------------------
>
> Key: JBTM-1749
> URL: https://issues.jboss.org/browse/JBTM-1749
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Environment: Mac OSX
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> To reproduce:
> # export JAVA_HOME=
> # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml
> It also happens if you use the maven version in tools/maven (also version 3.0.5).
> This doesn't fail:
> # export JAVA_HOME=
> # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml
> Currently only seen this on a Mac. Would be good if a linux user could try to reproduce.
> Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1749:
--------------------------------
Environment: See discussion (was: Mac OSX)
> Failure building Javadoc when JAVA_HOME is empty
> ------------------------------------------------
>
> Key: JBTM-1749
> URL: https://issues.jboss.org/browse/JBTM-1749
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Environment: See discussion
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> To reproduce:
> # export JAVA_HOME=
> # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml
> It also happens if you use the maven version in tools/maven (also version 3.0.5).
> This doesn't fail:
> # export JAVA_HOME=
> # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml
> Currently only seen this on a Mac. Would be good if a linux user could try to reproduce.
> Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months