[JBoss JIRA] (JBTM-1289) XTS participant completion tests should use a rendezvous to delay close until participant has completed
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1289:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/jbosstm/narayana/pull/166, https://github.com/jbosstm/narayana/pull/167
> XTS participant completion tests should use a rendezvous to delay close until participant has completed
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1289
> URL: https://issues.jboss.org/browse/JBTM-1289
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 4.16.7, 4.17.4, 5.0.0.M2
>
>
> The problem is that the participant's notification of completion (sent to the coord) is asynchronous. This can be overtaken by the client's "close" message, resulting in the coordinator cancelling the activity, due to not all participants being completed.
> The hack is to add a delay before the client calls 'close'. We have that on the tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as it's embarrassing and likely to be rejected ;-)
> This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous. Alternatively there may be some XTS feature that we can use to poll the coordinator. Or maybe we can add it, as the client API is not standardized.
> This issue is not urgent for the TS tests as the hack seems to be holding out at present. However, we do occasionally see this issue on the XTS AS integration testsuite, which increases the priority.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1369:
--------------------------------------
Summary: Benchmark performance difference between JacORB and JDK ORB
Key: JBTM-1369
URL: https://issues.jboss.org/browse/JBTM-1369
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JTS, Testing
Affects Versions: 4.17.0
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.Final
JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBTM-1299) Narayana artifacts are difficult to find after a build
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1299:
--------------------------------------
Summary: Narayana artifacts are difficult to find after a build
Key: JBTM-1299
URL: https://issues.jboss.org/browse/JBTM-1299
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: 4.17.0
Reporter: Michael Musgrove
Assignee: Tom Jenkinson
Fix For: 5.0.0.M2
The new build system leaves the installable jars in their respective module target directories. It is not obvious which jars are which so it would be nice if we can provide, near the top of the top level README, a brief description of the purpose and location of each target produced by the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1313:
--------------------------------------
Summary: Performance related work that involves other products should be in a separate repository
Key: JBTM-1313
URL: https://issues.jboss.org/browse/JBTM-1313
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Demonstrator
Affects Versions: 5.0.0.M1
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.M2
Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes:
- some changes to the jts quickstart
- the performance harness in qa/tests/product
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years