November 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-810) Set the default configuration to use socketless communication betweeen the transaction manager and recovery manager for JTA

by Tom Jenkinson (JIRA)

Set the default configuration to use socketless communication betweeen the transaction manager and recovery manager for JTA --------------------------------------------------------------------------------------------------------------------------- Key: JBTM-810 URL: https://jira.jboss.org/browse/JBTM-810 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.15.0 -- 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

4
12
0 / 0

[JBoss JIRA] Created: (JBTM-883) Missing wsdl resources in WS-C and WS-T jars in maven build

by Jakub Wierkowski (JIRA)

Missing wsdl resources in WS-C and WS-T jars in maven build ----------------------------------------------------------- Key: JBTM-883 URL: https://issues.jboss.org/browse/JBTM-883 Project: JBoss Transaction Manager Issue Type: Patch Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1 Reporter: Jakub Wierkowski Priority: Minor Attachments: xts_wsdl.patch Maven build of WS-C and WS-T modules does not copy wsdl resources into: org\oasis_open\docs\ws_tx\wscoor\_2006\_06\wsdl org\oasis_open\docs\ws_tx\wsat\_2006\_06\wsdl org\oasis_open\docs\ws_tx\wsba\_2006\_06\wsdl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

7
19
0 / 0

[JBoss JIRA] Created: (JBTM-878) The online docs have malformed author names.

by Paul Robinson (JIRA)

The online docs have malformed author names. -------------------------------------------- Key: JBTM-878 URL: https://issues.jboss.org/browse/JBTM-878 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Tom Jenkinson For example, see: http://docs.jboss.org/jbosstm/5.0.0.M1/guides/development_guide/index.html observe: {code} by Mark Red Hat Little, Jonathan Red Hat Halliday, Andrew Red Hat Dinn, and Kevin Red Hat Connor {code} The same problem seems to be occurring in the other docs, but I have not checked every one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
8
0 / 0

[JBoss JIRA] (JBTM-968) Review the project structure of XTS

by Paul Robinson (Created) (JIRA)

Review the project structure of XTS ----------------------------------- Key: JBTM-968 URL: https://issues.jboss.org/browse/JBTM-968 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M3 The structure of the XTS project needs reviewing. Things to look out for: # Check for ant build scripts and delete/mavenize as appropriate # Ensure all source directories follow the default maven structure # Move unit tests into the sub component that they test # Ensure consistent with the rest of the Narayana project # Ensure all readme files are up-to-date # Search for version numbers and check they are up-to-date. For example, some readme files state compatibility with certain (old) version of JBoss AS. # General review -- 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
9
0 / 0

[JBoss JIRA] (JBTM-966) XTS service fails to start when there is no internet connection

by Paul Robinson (Created) (JIRA)

XTS service fails to start when there is no internet connection --------------------------------------------------------------- Key: JBTM-966 URL: https://issues.jboss.org/browse/JBTM-966 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1, 4.15.3 Reporter: Paul Robinson Assignee: Amos Feng Priority: Critical Fix For: 4.15.4, 5.0.0.M2 Steps to reproduce: # Take latest JBossAS 7 from git hub # Build JBossAS # Disconnect from the internet # start the AS: sh bin/standalone.sh --server-config=standalone-xts.xml # observe: {code} 10:45:36,534 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.ws.endpoint-publish.ws-c11: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-c11: javax.xml.ws.WebServiceException: org.apache.ws.commons.schema.XmlSchemaException: Unable to locate imported document at 'http://www.w3.org/2006/03/addressing/ws-addr.xsd', relative to 'schema1.xsd'. at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:89) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: javax.xml.ws.WebServiceException: org.apache.ws.commons.schema.XmlSchemaException: Unable to locate imported document at 'http://www.w3.org/2006/03/addressing/ws-addr.xsd', relative to 'schema1.xsd'. at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:350) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:88) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:239) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:509) at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:116) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:109) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:132) at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:132) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:81) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:76) at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:87) ... 5 more Caused by: org.apache.ws.commons.schema.XmlSchemaException: Unable to locate imported document at 'http://www.w3.org/2006/03/addressing/ws-addr.xsd', relative to 'schema1.xsd'. at org.apache.cxf.catalog.CatalogXmlSchemaURIResolver.resolveEntity(CatalogXmlSchemaURIResolver.java:76) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:684) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:538) at org.apache.ws.commons.schema.SchemaBuilder.handleSchemaElementChild(SchemaBuilder.java:1513) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:659) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:157) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:398) at org.apache.cxf.common.xmlschema.SchemaCollection.read(SchemaCollection.java:130) at org.apache.cxf.databinding.AbstractDataBinding.addSchemaDocument(AbstractDataBinding.java:177) at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:344) at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86) at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:438) at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:682) at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:501) at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:241) at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:202) at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101) at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:157) at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:202) at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:433) at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:322) ... 16 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

5
6
0 / 0

[JBoss JIRA] (JBTM-962) Check the licence type of CXF

by Paul Robinson (Created) (JIRA)

Check the licence type of CXF ----------------------------- Key: JBTM-962 URL: https://issues.jboss.org/browse/JBTM-962 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Priority: Minor Fix For: 5.0.0.M2 We need to make sure we can ship it with standalone XTS. If it's not ASL, we should email rfontana(a)redhat.com and check what we are allowed to do with it. Once we know it's ok, we should include CXF in the standalone XTS distribution. -- 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] 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

4
10
0 / 0

[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

4
11
0 / 0

[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

4
10
0 / 0

[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

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2011