May 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-270) Add the performance test suite

by Mark Little (JIRA)

Add the performance test suite ------------------------------ Key: JBTM-270 URL: http://jira.jboss.com/jira/browse/JBTM-270 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Critical -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-261) Integrate WS-TX interoperability work into QA

by Mark Little (JIRA)

Integrate WS-TX interoperability work into QA --------------------------------------------- Key: JBTM-261 URL: http://jira.jboss.com/jira/browse/JBTM-261 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, WS-T Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Jonathan Halliday -- 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

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-292) For all supported databases, provide associated XAResourceRecovery plugin

by Mark Little (JIRA)

For all supported databases, provide associated XAResourceRecovery plugin ------------------------------------------------------------------------- Key: JBTM-292 URL: http://jira.jboss.com/jira/browse/JBTM-292 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Priority: Critical Fix For: 4.4 MR1 Currently we only ship with the OracleXARecovery class, a generic JDBCXARecovery implementation and an example. It's possible the generic one will work for many of the other databases, but it probably hasn't been checked in a while. -- 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

14 years, 11 months

2
6
0 / 0

[JBoss JIRA] Assigned: (JBTM-221) Improve WS-T example

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-221?page=com.atlassian.jira.plugi... ] Jonathan Halliday reassigned JBTM-221: -------------------------------------- Assignee: Andrew Dinn (was: Jonathan Halliday) > Improve WS-T example > -------------------- > > Key: JBTM-221 > URL: https://jira.jboss.org/jira/browse/JBTM-221 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, XTS > Affects Versions: 4.2.3 > Reporter: Mark Little > Assignee: Andrew Dinn > Fix For: 4.7.0 > > > It would be nice if the various windows could be displayed outside of a browser, for example. -- 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-86) Exception chaining

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-86?page=com.atlassian.jira.plugin... ] Jonathan Halliday commented on JBTM-86: --------------------------------------- There are around 3000 'throws' in the code base, not to mention various subclasses of Exception which will need their constructors refitting. I'm not prepared to halt feature work for the duration needed to do this in one pass. We'll tackle it a chunk at a time, probably by module starting with the lowest level and working up the module dependency chain. The JTS modules will need extra care - with chained exception all the elements of the chain must be present on a client JVM if the exception is thrown by a remote server, so there may be some cases in which we can't chain and still preserve the level of flexibility and interop we want. As for the rest, if there are particular throws points that are causing you trouble let me know and we'll prioritise them. > Exception chaining > ------------------ > > Key: JBTM-86 > URL: https://jira.jboss.org/jira/browse/JBTM-86 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Andrew Dinn > Priority: Optional > Fix For: future > > > Look at the feasibility of chaining exceptions in a distributed transaction to preseve error information. -- 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-260) Make sure we ship the ORB Portability manual

by Mark Little (JIRA)

Make sure we ship the ORB Portability manual -------------------------------------------- Key: JBTM-260 URL: http://jira.jboss.com/jira/browse/JBTM-260 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-419) Hardcoded "1.5" java version check in com\arjuna\ats\internal\jdbc\ConnectionManager.java won't work on Java 1.6

by Sergey Proskurnya (JIRA)

Hardcoded "1.5" java version check in com\arjuna\ats\internal\jdbc\ConnectionManager.java won't work on Java 1.6 ---------------------------------------------------------------------------------------------------------------- Key: JBTM-419 URL: https://jira.jboss.org/jira/browse/JBTM-419 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.4.0.GA Environment: Sun's J2SE DevKit 1.6u10 Reporter: Sergey Proskurnya Priority: Minor There is a hard-coded version check in com.arjuna.ats.internal.jdbc.ConnectionManager in "create (String dbUrl, Properties info)" method: -------------------------------------------------------------------------------------------------------------------------- ... line 116: if(System.getProperty("java.specification.version").equals("1.5")) { // the 1.5 (JDBC3) wrapper version is loaded dynamically because classloading // it on earlier versions of the platform is not possible. .... } -------------------------------------------------------------------------------------------------------------------------- That piece of code will not work correctly on Java 1.6, because System.getProperty("java.specification.version") returns "1.6" on Java 1.6. It is needed to parse the result of System.getProperty("java.specification.version") and compare major and minor versions separately. -- 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

14 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBTM-542) Slow memory leak / Thread lock on transaction initiated by MDB on jboss 4.2.3

by LESCARRET Vincent (JIRA)

Slow memory leak / Thread lock on transaction initiated by MDB on jboss 4.2.3 ------------------------------------------------------------------------------ Key: JBTM-542 URL: https://jira.jboss.org/jira/browse/JBTM-542 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3.SP7 Environment: Linux RH 4 , JDK 1.5.0_15 , jboss AS 4.2.3 Reporter: LESCARRET Vincent Priority: Critical This problem is already related in JIRA (https://jira.jboss.org/jira/browse/JBTM-444) . Our production server reachs UserLoad value of 100% in 3 our 4 days, and the only solution is to stop and restart the server. We intensively use JMS queue (JBOSS MQ and Oracle for persistence) and MDB which use XA transactions. What is the actual workaround for this problem ? Is the problem still in the Jboss 5 server ? log: 2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass 2009-05-04 00:07:04,640 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass 2009-05-04 00:07:14,642 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <lun., 4 mai 2009 00:07:14> -- 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

14 years, 11 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2009