June 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1176) XTS demo hang due to not launching firefox sometimes

by Amos Feng (JIRA)

Amos Feng created JBTM-1176: ------------------------------- Summary: XTS demo hang due to not launching firefox sometimes Key: JBTM-1176 URL: https://issues.jboss.org/browse/JBTM-1176 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1 Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.0.Final currently the XTS demo can not launch firefox sometimes and it looks like it hang in handling the selenium script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
6
0 / 0

[JBoss JIRA] (JBTM-956) Update the XTS WSTFSC07 interop tests to use Arquillian

by Paul Robinson (Created) (JIRA)

Update the XTS WSTFSC07 interop tests to use Arquillian ------------------------------------------------------- Key: JBTM-956 URL: https://issues.jboss.org/browse/JBTM-956 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Amos Feng Priority: Minor Fix For: 5.0.0.M2 These tests are built with ant. They are ran by deploying them as a war to a single JBoss instance which deploys the services needed by the test. This war also exposes a web interface that on request runs the tests and relays the results in the http response. This process is automated by using ant to deploy the war and then making the http request and validating the response. See here in code for scripts: "XTS/localjunit/run-interop-tests.xml" By using Arquillian we should be able to remove the ant script servlet, and web page then have Arquillian deploy the services and run the tests directly in the container. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (JBTM-868) Full support to use transaction manager and XA pools under tomcat and spring framework

by Magnus Magnus (JIRA)

Full support to use transaction manager and XA pools under tomcat and spring framework -------------------------------------------------------------------------------------- Key: JBTM-868 URL: https://issues.jboss.org/browse/JBTM-868 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Magnus Magnus Priority: Critical Fix For: 4.6.1.CP13, 4.15.4, 5.0.0.M1, 5.0.0.M2 Full support to use transaction manager and XA pools under tomcat and spring framework. Transaction manager should be able to use with full functionality under apache tomcat and springframework. Tomcat should be a fully tested platform with JBoss Transaction Manager. It should provide everything to use under tomcat included XA pools as well. See atomikos solution. http://www.atomikos.com/Main/TransactionsEssentials -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
6
0 / 0

[JBoss JIRA] (JBTM-1193) XTS unit tests: IllegalStateException: testSetStarting called twice

by Paul Robinson (JIRA)

12 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-905) XTS interop tests failed due to org.apache.cxf.interceptor.Fault on AS7

by Ivo Studensky (JIRA)

XTS interop tests failed due to org.apache.cxf.interceptor.Fault on AS7 ----------------------------------------------------------------------- Key: JBTM-905 URL: https://issues.jboss.org/browse/JBTM-905 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, XTS Affects Versions: 4.15.3 Reporter: Ivo Studensky XTS interop tests fail due to org.apache.cxf.interceptor.Fault on the latest AS7, see the server log snippets below. It was tested on the latest AS7 cloned from github master (last commit 262685f241be2b9d265f44e6051b17fc74600cf9). The interop tests was run from the web page GUI with parameter 'http://localhost:8080/interop11/ATParticipantService' as a Service URI for 'All AT tests' target. *server log snippets*: {noformat} 22:41:39,166 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-thinkpax.localdomain-127.0.0.1-8080-2) Interceptor for {http://fabrikam123.com}ParticipantService has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Message part {http://schemas.xmlsoap.org/soap/envelope/}Fault was not recognized. (Does it exist in service WSDL?) at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:197) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.1.jar:2.4.1] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:208) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91) at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:164) at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:138) [jbossws-spi-2.0.0.Beta9.jar:2.0.0.Beta9] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {noformat} and {noformat} 22:42:39,205 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-thinkpax.localdomain-127.0.0.1-8080-2) Interceptor for {http://fabrikam123.com}ParticipantService has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.1.jar:2.4.1] at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:104) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:323) [cxf-api-2.4.1.jar:2.4.1] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:208) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91) at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:164) at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:138) [jbossws-spi-2.0.0.Beta9.jar:2.0.0.Beta9] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.1.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/interop11/proxy/C1/http_--localhost_8080-interop11/...: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_26] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_26] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_26] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1404) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1389) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) [cxf-rt-core-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:623) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) [cxf-rt-core-2.4.1.jar:2.4.1] ... 28 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) [:1.6.0_26] at java.net.SocketInputStream.read(SocketInputStream.java:129) [:1.6.0_26] at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) [:1.6.0_26] at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) [:1.6.0_26] at java.io.BufferedInputStream.read(BufferedInputStream.java:317) [:1.6.0_26] at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687) [:1.6.0_26] at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) [:1.6.0_26] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195) [:1.6.0_26] at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) [:1.6.0_26] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1509) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1467) [cxf-rt-transports-http-2.4.1.jar:2.4.1] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1375) [cxf-rt-transports-http-2.4.1.jar:2.4.1] ... 31 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
8
0 / 0

[JBoss JIRA] (JBTM-990) com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction catches and throws a NullPointerException instead of checking if it is null first

by Stuart Douglas (Created) (JIRA)

com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction catches and throws a NullPointerException instead of checking if it is null first --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-990 URL: https://issues.jboss.org/browse/JBTM-990 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.15.3 Reporter: Stuart Douglas com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction has the following: try { return theTransaction.getStatus(); } catch (NullPointerException ex) { return javax.transaction.Status.STATUS_NO_TRANSACTION; } This mean's that anyone trying to debug a NPE with an exception breakpoint will constantly hit this, as well as being much slower than a simple null check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
5
0 / 0

[JBoss JIRA] (JBTM-1117) Remove RHQ plugin

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1117: ----------------------------------- Summary: Remove RHQ plugin Key: JBTM-1117 URL: https://issues.jboss.org/browse/JBTM-1117 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.16.4, 5.0.0.M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
3
0 / 0

[JBoss JIRA] (JBTM-1140) Update Arquillian version in TxBridge tests, TxBridge demo tests and XTS demo tests

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1140: ----------------------------------- Summary: Update Arquillian version in TxBridge tests, TxBridge demo tests and XTS demo tests Key: JBTM-1140 URL: https://issues.jboss.org/browse/JBTM-1140 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Testing, TxBridge, XTS Affects Versions: 4.16.3 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.16.4 Arquillian version used in pom.xml's at txbridge tests, txbridge demo tests and xts demo tests are out of date. Please update them to the latest stable ones. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBTM-900) Some of XTS unit test EARs contain no longer supported namespace in META-INF/jboss-beans.xml

by Ivo Studensky (JIRA)

Some of XTS unit test EARs contain no longer supported namespace in META-INF/jboss-beans.xml -------------------------------------------------------------------------------------------- Key: JBTM-900 URL: https://issues.jboss.org/browse/JBTM-900 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, XTS Affects Versions: 4.15.3 Reporter: Ivo Studensky Some of the XTS unit test EARs contain no longer supported namespace in META-INF/jboss-beans.xml and so they cannot be deployed to AS7. See [1] for the current namespace used in XTS unit test EARs and [2] for the valid namespace that should be used in AS7. A bit weird is that those EARs can be successfully deployed by command line copy and by web admin console, but only deploying by Arquillian uncovered the issue. I've already filed a jira for that - AS7-1927. Please could you take a look at that and fix the namespace? Here is a list of the affected EARs: ws-c-tests.ear ws-t-tests.ear wstx-tests.ear [1] <deployment xmlns="urn:jboss:bean-deployer:2.0"> [2] <deployment xmlns="urn:jboss:pojo:7.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:pojo:7.0 jboss-pojo_7_0.xsd"> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
6
0 / 0

[JBoss JIRA] (JBTM-1015) Reduce recoveryPeriod to 10secs for all XTS crash recovery tests

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1015: ----------------------------------- Summary: Reduce recoveryPeriod to 10secs for all XTS crash recovery tests Key: JBTM-1015 URL: https://issues.jboss.org/browse/JBTM-1015 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.16.1, 5.0.0.M2 This reduces how long the tests take to run. Any lower than 10secs could result in unwanted behaviour -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2012