[JBoss JIRA] (JBTM-1511) Dynamic 1PC optimisation
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1511?page=com.atlassian.jira.plugin.... ]
Mark Little reopened JBTM-1511:
-------------------------------
Appears to break some QA tests. Will look into these.
> Dynamic 1PC optimisation
> ------------------------
>
> Key: JBTM-1511
> URL: https://issues.jboss.org/browse/JBTM-1511
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Mark Little
> Fix For: 5.0.0.M2
>
>
> If the first N-1 participants in the intentions list return read-only, then we can call commitOnePhase on the last resource, bypassing prepare and writing of the log.
> Note: this has been on the todo list for years. Time to do it.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1016?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1016:
----------------------------
Original Estimate: 1 week
Remaining Estimate: 1 week
Labels: (was: assign)
> Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code
> -------------------------------------------------------------------------------------
>
> Key: JBTM-1016
> URL: https://issues.jboss.org/browse/JBTM-1016
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Fix For: 5.0.0.M3
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> I've found many bugs in the XTS crash recovery tests that where due to changes being made to the XTS code without updating the byteman scripts. The problem is that these inconsistencies often go unnoticed when the tests run, until you notice a failure in the test.
> Can we run bmcheck as part of the maven build and make the build fail if it detects errors? Needs to be integrated into the poms, perhaps by an exec in an antrun plugin
> NOTE: Before raising the pull req it will be necessary to resolve any the discovered errors.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1479?focusedWorklogId=12428740&page=... ]
Gytis Trikleris logged work on JBTM-1479:
-----------------------------------------
Author: Gytis Trikleris
Created on: 05/Mar/13 12:28 PM
Start Date: 05/Mar/13 12:28 PM
Worklog Time Spent: 5 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 day, 5 hours (was: 2 days, 2 hours)
Time Spent: 1 day, 3 hours (was: 6 hours)
Worklog Id: (was: 12428740)
> Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
> -------------------------------------------------------------------------
>
> Key: JBTM-1479
> URL: https://issues.jboss.org/browse/JBTM-1479
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M3
>
> Attachments: test-ds.xml, transaction.xml
>
> Original Estimate: 3 days
> Time Spent: 1 day, 3 hours
> Remaining Estimate: 1 day, 5 hours
>
> See JBTM-809 for the algorithm
> You might want to put the startup in the context listener:
> public class MyServletContextListener implements ServletContextListener {
> public void contextInitialized(ServletContextEvent sce) {
> // Initialize RecoveryManager
> // Initialize TransactionManager
> // Initialize IronJacamar
> }
>
> @Override
> public void contextDestroyed(ServletContextEvent sce) {
> // Clean IronJacamar
> // Clean TransactionManager
> // Clean RecoveryManager
> }
> }
> Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1515) Investigate the overhead of bridging JTA to WS-AT when not needed
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1515:
-----------------------------------
Summary: Investigate the overhead of bridging JTA to WS-AT when not needed
Key: JBTM-1515
URL: https://issues.jboss.org/browse/JBTM-1515
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: TXFramework, XTS
Reporter: Paul Robinson
Fix For: 5.0.0.Final
When using default context propagation, a subordinate WS-AT transaction will be created for Web service calls made within a JTA transaction. This is wasteful if the target service does not enlist any participants in this transaction.
We should measure the overhead that this imposes and take steps to reduce/remove it.
--
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
11 years, 9 months