June 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-906) stub new jdbc methods for build on jdk7

by Jonathan Halliday (JIRA)

stub new jdbc methods for build on jdk7 --------------------------------------- Key: JBTM-906 URL: https://issues.jboss.org/browse/JBTM-906 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1, 4.15.3 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.15.4, 5.0.0.M2 The JDBC classes in Java 7 have some new methods. These need stubbing out in our transactional driver and test harness so we can build on jdk7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-770) incorrect cleanup registration causes memory leak

by Jonathan Halliday (JIRA)

incorrect cleanup registration causes memory leak ------------------------------------------------- Key: JBTM-770 URL: https://jira.jboss.org/browse/JBTM-770 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1.CP06, 4.12.0 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.13.0, 4.6.1.CP08 jts.TransactionImple constructors attempt to optimize the cleanup callback needed to remove entries from _transactions, bypassing the ORB for interposition scenarios: theTx = (TwoPhaseCoordinator) BasicAction.Current(); if (theTx != null) { theTx.addSynchronization(new LocalCleanupSynchronization(this)); } else { registerSynchronization(new CleanupSynchronization(this)); } Unfortunately this does not work and leads to memory leaks on _transactions in certain cases. Specifically, where theTx is a ServerTransaction (i.e. extends ArjunaTransactionImple, which extends TwoPhaseCoordinator), the callbacks run (by ArjunaTransactionImple.do[Before|After]Completion()) are those in ArjunaTransactionImple._syncs, not the masked ones in TwoPhaseCoordinator._syncs. Thus using TwoPhaseCoordinator.addSynchronization registers a callback which is never invoked. -- 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, 2 months

9
15
0 / 0

[JBoss JIRA] Created: (JBTM-852) Setting SettingVolatile store still creates an ObjectStore directory on the disk

by Mircea Markus (JIRA)

Setting SettingVolatile store still creates an ObjectStore directory on the disk --------------------------------------------------------------------------------- Key: JBTM-852 URL: https://issues.jboss.org/browse/JBTM-852 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.15.0 Reporter: Mircea Markus Priority: Minor Even when configuring {code:java} arjPropertyManager.getObjectStoreEnvironmentBean().setObjectStoreType(VolatileStore.class.getName()) {code} an "ObjectStore" directory is created on the disk. After discussing with JTM team this doesn't cause any real problem in the sense that nothing is written to the disk, but this is annoying and might create confusion between the users. A workaround would be to add the following configuration together with the previously mentioned one: {code:java} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "communicationStore").setObjectStoreType(VolatileStore.class.getName()) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
21
0 / 0

[JBoss JIRA] Created: (JBTM-847) Look into how AssumedComplete works for ArjunaJTA (and jtax)

by Mark Little (JIRA)

Look into how AssumedComplete works for ArjunaJTA (and jtax) ------------------------------------------------------------ Key: JBTM-847 URL: https://issues.jboss.org/browse/JBTM-847 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Reporter: Mark Little Assignee: Tom Jenkinson When a transaction cannot be completed over a long period of time, a scanner is supposed to kick in and move the log elsewhere. Those scanners exist in ArjunaCore and ArjunaJTS, but do not appear to be there in ArjunaJTA. It should be straightforward to add them by using the base class in ArjunaCore, but investigate whether they are present already and just not obvious. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
8
0 / 0

[JBoss JIRA] (JBTM-1112) update narayana.sh to build jboss-as from git:/jbosstm/jboss-as

by Amos Feng (JIRA)

Amos Feng created JBTM-1112: ------------------------------- Summary: update narayana.sh to build jboss-as from git:/jbosstm/jboss-as Key: JBTM-1112 URL: https://issues.jboss.org/browse/JBTM-1112 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 5.0.0.M1 Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.1.Final currently we use jboss-as-7.1.1.Final which will always contain JBossTS 4.16.2. Therefore the tests will always run against 4.16.2 of JBossTS and not the new version of the code that this script intends to test. so it need to build jboss-as. #make sure you have built narayana and have a SNAPSHOT (which you currently are) git clone git://github.com/jbosstm/jboss-as.git git checkout 5_BRANCH (for github master, for backporting you will need to use 4_16_BRANCH) build jboss-as -- 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] 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, 2 months

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, 2 months

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, 2 months

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, 2 months

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, 2 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2012