[JBoss JIRA] Created: (JBTM-759) Errors in the Failure Recovery Guide
by Mauro Molinari (JIRA)
Errors in the Failure Recovery Guide
------------------------------------
Key: JBTM-759
URL: https://jira.jboss.org/browse/JBTM-759
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Mauro Molinari
Priority: Minor
While reading the Failure Recovery Guide I found some errors:
- page 7: line 3 seems to be victim of an erroneous copy-and-paste
- page 11: line 3 of the pseudo code for the first pass of AtomicAction is not clear, since the vector has been just created and transactions are added to it within the same loop body...
- page 24: the chapter is named "Chapter 1", while it should be "Chapter 2"
- page 30: I think "Configuration options" should be "Chapter 3"; moreover, there's no warning about the fact that the table is deprecated (because it shows the configuration options with the old names).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] Created: (JBTM-761) Errors in JBossTS JTA documentation
by Mauro Molinari (JIRA)
Errors in JBossTS JTA documentation
-----------------------------------
Key: JBTM-761
URL: https://jira.jboss.org/browse/JBTM-761
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.11.0
Reporter: Mauro Molinari
Priority: Minor
While reading the JBossTS JTA documentation, I found the following problems:
Administration Guide:
- page 7: in the "ArjunaTA runtime information" chapter there's a typographic error ("<name>EnvironmentBean classes")
- page 8: in the "Configuring the Recovery Manager" chapter I think that "arjuna.properties" should rather be "jbossts-properties.xml"
Programmers Guide:
- page 8: in the last paragraph there's a repetition: "and contains also contains a mapping of the X/Open XA protocol"
- page 12: in the "Resource enlistment" chapter, second paragraph, there: "See [? missing reference?] for details on how the implementation of the XAResource can affect recovery..."
Moreover, all the chapters are numbered as "Chapter 1".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] Created: (JBTM-758) Errors in documentation: Transaction Core Programmers Guide
by Mauro Molinari (JIRA)
Errors in documentation: Transaction Core Programmers Guide
-----------------------------------------------------------
Key: JBTM-758
URL: https://jira.jboss.org/browse/JBTM-758
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.11.0
Reporter: Mauro Molinari
Priority: Minor
I'm going to highlight some errors I found during the reading of the Transaction Core Programmers Guide (TX-PG-5/11/10):
- page 31: when describing LogManager: "The *shared* parameter only has meaning if *ot* is RECOVERABLE"; actually the two parameters are named *objectModel* and *ObjectType* respectively in the caption of the paragraph
- page 36: in the example, I think the line with "A.add(new ShutdownRecord(...)" is not pertinent
- page 64: the last sentence says that the issues described in that paragraph will be addressed in the next section, but the next section is about configuration
- page 65: the second paragraph has some typographic problem (<module>propertyManager, <name>EnvironmentBean)
- page 69: in the second paragraph: "All of the implementations are derived from the ObjectStore interface"; actually, ObjectStore is a class to extend, not an interface to implement
Lastly, an observation about the depiction of finalizers as "destructors": in this guide, the finalize method is considered a destructor. However, in Java it is not actually. Anyway, it's not clear if calling terminate() in the finalize() is mandatory or not. If so, why isn't it called directly in com.arjuna.ats.arjuna.StateManager.finalize()? If not, I have another doubt. In all the examples of user classes (i.e. page 60) the finalize() is implemented as:
public void finalize()
{
super.terminate();
}
However, super.finalize() is not called. Isn't it risky? I mean, in this way the code in com.arjuna.ats.arjuna.StateManager.finalize() is never called... I think the documentation should be more clear on this subject.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] Created: (JBTM-902) Allow STM work to be consumed by Narayana-all
by Tom Jenkinson (JIRA)
Allow STM work to be consumed by Narayana-all
---------------------------------------------
Key: JBTM-902
URL: https://issues.jboss.org/browse/JBTM-902
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Jenkinson
Assignee: Mark Little
Priority: Minor
Fix For: 5.0.0.M2
I don't mind moving this into trunk once you comment that it is in a safe state to do so.
This would mean it was versioned with the rest of the project though.
If you want to keep it standalone, that is fine. Though in that case it would be great to mavenise it and set it up into a build so we can consume it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[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
11 years, 6 months
[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
11 years, 6 months