March 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBTM-40) Set up common.jar as a separate project

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-40?page=com.atlassian.jira.plugin... ] Mark Little closed JBTM-40. --------------------------- Resolution: Out of Date This may happen as part of TAG work on common logging, but we may go in another direction. > Set up common.jar as a separate project > --------------------------------------- > > Key: JBTM-40 > URL: https://jira.jboss.org/jira/browse/JBTM-40 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Mark Little > Assignee: Mark Little > Fix For: future > > > Common.jar (and associated build environment) contains the I18N/L10N capabilities that TS requires. However, other projects and products within JBoss may find this useful. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-498) Rename jbosscore.jar

by Mark Little (JIRA)

Rename jbosscore.jar -------------------- Key: JBTM-498 URL: https://jira.jboss.org/jira/browse/JBTM-498 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Priority: Minor When building the core engine the resultant jar is called jbosscore.jar, which is a little misleading. Maybe jbossts-core.jar? -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-642) Complete RecordType and ObjectStoreType factories

by Mark Little (JIRA)

Complete RecordType and ObjectStoreType factories ------------------------------------------------- Key: JBTM-642 URL: https://jira.jboss.org/jira/browse/JBTM-642 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.9.0 -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-732) XA transaction not propagating to IONA Orbix

by jzendle (JIRA)

XA transaction not propagating to IONA Orbix -------------------------------------------- Key: JBTM-732 URL: https://jira.jboss.org/jira/browse/JBTM-732 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.10.0 Environment: windows xp Jboss TS 4.10, IONA Orbix 6.4.3 Reporter: jzendle 1) We have a stateless EJB running on server A JBoss 6.0 w/ JBossTS 4.10. 2) when invoked the bean starts a transaction using OTS (TransactionCurrent) then makes a 'client' call to an Iona CORBA server running on server B. 3) The method we are calling on B is defined as REQUIRES (via standard transactional POA policy symantics) 4) the remote corba method inserts a record into a table using oracle XA driver and returns the id of the newly inserted record to A 5) A receives the id and attempts to, within the same global transaction, read the newly inserted record to do further work. 6) the transaction is then committed What I am seeing is that before the OTS transaction is committed the new record is *not* visible to A. After the transaction is comitted it is visible to 'A'. I would expect to see: 1) 'A' would be able to read the record since it is within the same global transaction before the transaction is committed. 2) If the Bean on A is coded as 'transaction required', I would think that I would not need to explicitly create an OTS transaction. The transaction created by the container would implicitly propagate to the corba call to server B. I've attached the bean code, server log, datasource definition. Our environment is: 1) Hand built nightly of JBossTS 4.10. We build the JTS and run it on windows xp. 2) we copied the jbossjts.jar and jbossjts-integration.jar from the jbossts build into the ./client and ./common/lib directories of jboss6.M2 3) in docs/examples/transactions we run ant to install the jts into the 'all' configuration 4) the IONA orbix641.jar client file is placed into the ./all/lib directory to be accessible to our .ear. Any help and recommendations is greatly appreciated. Note: before fix for JBTM-670 we were not even able to call the iona orb. We would get corba TRANSACTION_REQUIRED exceptions - so this is good progress. Thanks in advance. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-709) Improve test coverage for txoj

by Mark Little (JIRA)

Improve test coverage for txoj ------------------------------ Key: JBTM-709 URL: https://jira.jboss.org/jira/browse/JBTM-709 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.10.0 -- 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, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBTM-725) add recovery scanning to BridgeWrapper

by Jonathan Halliday (JIRA)

add recovery scanning to BridgeWrapper -------------------------------------- Key: JBTM-725 URL: https://jira.jboss.org/jira/browse/JBTM-725 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery, XTS Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Andrew Dinn Fix For: 4.11.0 The BridgeWrapper for managing subordinate XTS transactions allows for recovery where the id of the tx is known i.e. a log exists in the parent tx. "BridgeWrapper.recreate(String id)". However, it is also necessary to be able to scan for outstanding BridgeWrappers in recovery situations where no parent log exists and the id(s) are therefore unavailable. Furthermore, multiple applications may use the BridgeWrapper and must be able to distinguish which of the recovered instances they are responsible for. As they currently have no control over the structure of the id this is not feasible. Change BridgeWrapper API to include e.g. create(String prefix) // each app uses its own prefix so it can filter returned instances by id at recovery time. recreate(String id) // unchanged recoveryScan(String prefix) // return all in-doubt instances with matching prefix. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-729) Remove idl generated code from emma statistics

by Mark Little (JIRA)

Remove idl generated code from emma statistics ---------------------------------------------- Key: JBTM-729 URL: https://jira.jboss.org/jira/browse/JBTM-729 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.11.0 Emma gives data about code coverage for CosTransactions and ArjunaOTS. Many of the methods we'd never call or be able to call as they are the domain of the ORB or POA. Can we remove these from emma's view somehow? -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-705) update db2, sybase test server cfg

by Jonathan Halliday (JIRA)

update db2, sybase test server cfg ---------------------------------- Key: JBTM-705 URL: https://jira.jboss.org/jira/browse/JBTM-705 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.9.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.10.0 Update the qa test config to use current versions of db2 and sybase instead of obsolete ones. see also JBQA-2860 -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-684) Byteman overriding injection bug is causing unit tests to fail

by Andrew Dinn (JIRA)

Byteman overriding injection bug is causing unit tests to fail -------------------------------------------------------------- Key: JBTM-684 URL: https://jira.jboss.org/jira/browse/JBTM-684 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.9.0 Reporter: Andrew Dinn Assignee: Andrew Dinn The 1.2.1 byteman jar installed in the ext directory suffers from bug https://jira.jboss.org/jira/browse/BYTEMAN-80. This is causing some of the reaper unit tests to fail. In the absence of a fix to the Byteman bug the best way to bypass this is to disable overriding injection by setting property org.jboss.byteman.skip.override.rules in the ant macro run.tests.macro. This means that overriding injection cannot be used when scripting unit tests but as it is currently inherently flaky this is no bad thing. -- 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, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2010