April 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-247) Update (if necessary) the new integration layer SPIs

by Mark Little (JIRA)

Update (if necessary) the new integration layer SPIs ---------------------------------------------------- Key: JBTM-247 URL: http://jira.jboss.com/jira/browse/JBTM-247 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Jonathan Halliday http://anonsvn.jboss.org/repos/jbossas/projects/integration/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-892) Document the usage of the shipped maven installation in the build instructions

by Tom Jenkinson (JIRA)

Document the usage of the shipped maven installation in the build instructions ------------------------------------------------------------------------------ Key: JBTM-892 URL: https://issues.jboss.org/browse/JBTM-892 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M2 Include info such as txmvn -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
12
0 / 0

[JBoss JIRA] (JBTM-1124) jbosstm/jboss-as merge failed from the upstream

by Amos Feng (JIRA)

Amos Feng created JBTM-1124: ------------------------------- Summary: jbosstm/jboss-as merge failed from the upstream Key: JBTM-1124 URL: https://issues.jboss.org/browse/JBTM-1124 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Amos Feng Assignee: Tom Jenkinson Fix For: 5.0.0.M2 the following error when doing 'git pull --rebase upstream master' on jbosstm/jboss-as(BRANCH_5). ... Auto-merging pom.xml Auto-merging jacorb/pom.xml CONFLICT (content): Merge conflict in jacorb/pom.xml Auto-merging build/pom.xml Auto-merging build/build.xml Failed to merge in the changes. Patch failed at 0001 5.0.0.M2-SNAPSHOT version of TS ... jacorb/pom.xm ... <dependency> <<<<<<< HEAD <groupId>org.jboss.as</groupId> <artifactId>jboss-as-network</artifactId> </dependency> <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjts</artifactId> ======= <groupId>org.jboss.narayana.jts</groupId> <artifactId>narayana-jts</artifactId> >>>>>>> 5.0.0.M2-SNAPSHOT version of TS </dependency> see https://github.com/jbossas/jboss-as/commit/d3fb1ce3f1688a654e19c0e56b7f98... -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-520) Include distribution information in MANIFEST.MF

by Jesper Pedersen (JIRA)

Include distribution information in MANIFEST.MF ----------------------------------------------- Key: JBTM-520 URL: https://jira.jboss.org/jira/browse/JBTM-520 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6.0 Reporter: Jesper Pedersen Priority: Minor It would be nice if the jar files contain information inside the MANIFEST.MF files - like Implementation-Title Implementation-Vendor Implementation-Vendor-Id Implementation-Version -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
14
0 / 0

[JBoss JIRA] (JBTM-1113) artifacts id different between narayana and jbossts when building jboss-as

by Amos Feng (JIRA)

Amos Feng created JBTM-1113: ------------------------------- Summary: artifacts id different between narayana and jbossts when building jboss-as Key: JBTM-1113 URL: https://issues.jboss.org/browse/JBTM-1113 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Amos Feng Assignee: Tom Jenkinson checkout 5_BRANCH on jboss-as and build fail. It looks like we should change groupId from "org.jboss.jbossts" to "org.jboss.narayana" and different artifact id between them: 1. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjts</artifactId> </dependency> 2. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossxts</artifactId> </dependency> 3. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossxts-api</artifactId> </dependency> 4. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbosstxbridge</artifactId> </dependency> 5. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjts-integration</artifactId> </dependency> -- 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, 1 month

2
6
0 / 0

[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

12 years, 1 month

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

12 years, 1 month

7
19
0 / 0

[JBoss JIRA] (JBTM-1070) Separate documentation into its own repo

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1070: ----------------------------------- Summary: Separate documentation into its own repo Key: JBTM-1070 URL: https://issues.jboss.org/browse/JBTM-1070 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson 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

12 years, 1 month

1
4
0 / 0

[JBoss JIRA] (JBTM-1065) The coordinator does not flush its cache of transactions as they timeout eventually resulting in OOM

by Radesh Rao (JIRA)

Radesh Rao created JBTM-1065: -------------------------------- Summary: The coordinator does not flush its cache of transactions as they timeout eventually resulting in OOM Key: JBTM-1065 URL: https://issues.jboss.org/browse/JBTM-1065 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M1 Reporter: Radesh Rao Assignee: Michael Musgrove When transactions timeout (when the client abandons them or errors out) the org.jboss.jbossts.star.service.Coordinator holds references to the org.jboss.jbossts.star.resource.Transaction in the transactions Map. So eventually the Coordinator goes OOM. -- 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, 1 month

3
4
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

12 years, 1 month

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2012