2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2011

jbossts-issues@lists.jboss.org

1 participants
177 discussions

Start a nNew thread

[JBoss JIRA] Created: (JBTM-837) Transaction deadlock when NoSuchElementException is thrown from AsyncStore.doWork()

by Tom Waterhouse (JIRA)

Transaction deadlock when NoSuchElementException is thrown from AsyncStore.doWork() ----------------------------------------------------------------------------------- Key: JBTM-837 URL: https://issues.jboss.org/browse/JBTM-837 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.14.0 Environment: Ubuntu 64-bit Linux/JBoss JTA 4.14.0/Hibernate 3.6.1/Infinispan 3.4.0.CR2/Spring 3.0.5/MySQL 5.1 Reporter: Tom Waterhouse Attachments: arjuna-deadlock-trace.txt, default-jbossts-properties.xml Our product has a scheduled job that runs every 30 minutes. Callable instances are added to an ExecutorService instance which is currently configured for 16 threads. Our JBoss JTA implementation is using CacheStore as the object store (default-jbossts-properties.xml attached). After some time a NoSuchElementException is thrown from AsyncStore.doWork(). That exception is somehow blocking other transaction thread's execution. The Java thread dump is attached as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

5
20
0 / 0

[JBoss JIRA] Created: (JBTM-884) No download link to JBOSSTS_4_15_3_Final release on download page

by Paul Robinson (JIRA)

No download link to JBOSSTS_4_15_3_Final release on download page ----------------------------------------------------------------- Key: JBTM-884 URL: https://issues.jboss.org/browse/JBTM-884 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson See: http://www.jboss.org/jbosstm/downloads Latest download release is 4.15.1.final This is important as 4.15.3.final is the release that goes into JBoss_AS_7.0.1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
5
0 / 0

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

by Paul Robinson (Created) (JIRA)

Update the XTS WSTX11 interop tests to use Arquillian ----------------------------------------------------- Key: JBTM-955 URL: https://issues.jboss.org/browse/JBTM-955 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Amos Feng Fix For: 5.0.0.M2 Currently the XTS unit tests deploy a servlet that is invoked by an ant script. By using Arquillian we should be able to remove the ant script and servlet 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

11 years, 6 months

4
6
0 / 0

[JBoss JIRA] (JBTM-954) Update the XTS unit tests to use Arquillian

by Paul Robinson (Created) (JIRA)

Update the XTS unit tests to use Arquillian ------------------------------------------- Key: JBTM-954 URL: https://issues.jboss.org/browse/JBTM-954 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Amos Feng Fix For: 5.0.0.M2 Currently the XTS unit tests deploy a servlet that is invoked by an ant script. By using Arquillian we should be able to remove the ant script and servlet 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

11 years, 6 months

6
8
0 / 0

[JBoss JIRA] (JBTM-946) XTS always advertises localhost:8080 as RegistrationService address in CoordinationContext

by Paul Robinson (Created) (JIRA)

XTS always advertises localhost:8080 as RegistrationService address in CoordinationContext ------------------------------------------------------------------------------------------ Key: JBTM-946 URL: https://issues.jboss.org/browse/JBTM-946 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.15.4, 5.0.0.M2 If no URL is provided the coordinator address is located via localhost:8080 (or localhost:8443 if an https scheme is employed). Similarly, the deployed web services are assumed to have localhost:8080 addresses. The XTS extension ought to depend on JBoss web and use the bind address and ports (non-secure and secure) JBoss web employs. -- 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

11 years, 6 months

4
4
0 / 0

[JBoss JIRA] (JBTM-942) XTS Demo: ClassNotFoundException: com.sun.org.apache.xerces.internal.dom.DocumentImpl

by Paul Robinson (Created) (JIRA)

XTS Demo: ClassNotFoundException: com.sun.org.apache.xerces.internal.dom.DocumentImpl ------------------------------------------------------------------------------------- Key: JBTM-942 URL: https://issues.jboss.org/browse/JBTM-942 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson The following stacktrace appears when clicking "Submit Booking Request" on the XTS demo built from today's JBossTS 4.15.0 running on today's JBossAS 7 master: {code} 17:11:47,459 WARN [org.jboss.modules] (http-localhost-127.0.0.1-8080-7) Failed to define class com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl in Module "com.sun.xml.messaging.saaj:main" from local module loader @23394894 (roots: /home/paul/dev/jboss-as.2/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/modules): java.lang.LinkageError: Failed to link com/sun/xml/messaging/saaj/soap/SOAPDocumentImpl (Module "com.sun.xml.messaging.saaj:main" from local module loader @23394894 (roots: /home/paul/dev/jboss-as.2/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/modules)) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:416) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) at org.jboss.modules.Module.loadModuleClass(Module.java:500) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:485) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:444) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:421) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:143) at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:119) at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.<init>(SOAPPart1_1Impl.java:89) at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.getSOAPPart(Message1_1Impl.java:109) at org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:185) [cxf-rt-bindings-soap-2.4.2.jar:2.4.2] at org.apache.cxf.jaxws.handler.soap.SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:78) [cxf-rt-frontend-jaxws-2.4.2.jar:2.4.2] at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.createProtocolMessageContext(SOAPHandlerInterceptor.java:256) [cxf-rt-frontend-jaxws-2.4.2.jar:2.4.2] at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessageInternal(SOAPHandlerInterceptor.java:160) [cxf-rt-frontend-jaxws-2.4.2.jar:2.4.2] at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:123) [cxf-rt-frontend-jaxws-2.4.2.jar:2.4.2] at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:70) [cxf-rt-frontend-jaxws-2.4.2.jar:2.4.2] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.2.jar:2.4.2] at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-rt-core-2.4.2.jar:2.4.2] at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:206) [cxf-rt-transports-http-2.4.2.jar:2.4.2] at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91) at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:174) 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.2.jar:2.4.2] at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107) [cxf-rt-transports-http-2.4.2.jar:2.4.2] 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:140) 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) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:670) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: java.lang.NoClassDefFoundError: com/sun/org/apache/xerces/internal/dom/DocumentImpl at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_27] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [:1.6.0_27] at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [:1.6.0_27] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [:1.6.0_27] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:330) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:411) ... 41 more Caused by: java.lang.ClassNotFoundException: com.sun.org.apache.xerces.internal.dom.DocumentImpl from [Module "com.sun.xml.messaging.saaj:main" from local module loader @23394894 (roots: /home/paul/dev/jboss-as.2/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:485) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:444) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:444) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:421) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:143) ... 47 more {code} -- 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

11 years, 6 months

6
11
0 / 0

[JBoss JIRA] (JBTM-943) Update XTS Interop tests to use Maven

by Paul Robinson (Created) (JIRA)

Update XTS Interop tests to use Maven ------------------------------------- Key: JBTM-943 URL: https://issues.jboss.org/browse/JBTM-943 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Amos Feng Fix For: 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

11 years, 6 months

5
12
0 / 0

[JBoss JIRA] (JBTM-944) Update XTS Crash Recovery tests to use Maven

by Paul Robinson (Created) (JIRA)

Update XTS Crash Recovery tests to use Maven -------------------------------------------- Key: JBTM-944 URL: https://issues.jboss.org/browse/JBTM-944 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Amos Feng -- 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

11 years, 6 months

4
8
0 / 0

[JBoss JIRA] (JBTM-945) Update XTS unit tests to use Maven

by Paul Robinson (Created) (JIRA)

Update XTS unit tests to use Maven ---------------------------------- Key: JBTM-945 URL: https://issues.jboss.org/browse/JBTM-945 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Paul Robinson Priority: Minor Fix For: 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

11 years, 6 months

5
8
0 / 0

[JBoss JIRA] (JBTM-926) Byteman scripts in Crash Recovery tests have wrong expected output

by Paul Robinson (Created) (JIRA)

Byteman scripts in Crash Recovery tests have wrong expected output ------------------------------------------------------------------ Key: JBTM-926 URL: https://issues.jboss.org/browse/JBTM-926 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1, 4.15.3, 4.6.1.CP12 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.6.1.CP13, 4.15.4, 5.0.0.M2 The output text produced during a run of these tests has changed, but the documentation has not been updated to reflect this. -- 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

11 years, 6 months

3
3
0 / 0

← Newer
1
...
4
5
6
7
8
9
10
...
18
Older →

Jump to page: