[JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1099:
-------------------------------------
I've started a design discussion here: https://community.jboss.org/thread/220541
> WS-BA to 2xJTA bridge
> ---------------------
>
> Key: JBTM-1099
> URL: https://issues.jboss.org/browse/JBTM-1099
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Labels: assign
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
> There may be other windows in Compensate and Close. This needs investigating.
> The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
> This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
--
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, 3 months
[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1369:
--------------------------------
Priority: Major (was: Minor)
> 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
> Fix For: 5.0.0.M2
>
>
> 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
11 years, 3 months
[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1369:
--------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.0.Final)
> 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.M2
>
>
> 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
11 years, 3 months
[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1446?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1446:
--------------------------------
Component/s: Demonstrator
> Prepare Quickstarts for Release
> -------------------------------
>
> Key: JBTM-1446
> URL: https://issues.jboss.org/browse/JBTM-1446
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> * The tag should reference the latest release, rather than a snapshot
> * Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
> * General check over looking for things that won't work with a tagged/released AS7+Narayana.
--
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, 3 months
[JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1099:
--------------------------------
Description:
It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
There may be other windows in Compensate and Close. This needs investigating.
The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
was:
It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when if a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
There may be other windows in Compensate and Close. This needs investigating.
The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
> WS-BA to 2xJTA bridge
> ---------------------
>
> Key: JBTM-1099
> URL: https://issues.jboss.org/browse/JBTM-1099
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Labels: assign
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated.
> There may be other windows in Compensate and Close. This needs investigating.
> The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
> This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.
--
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, 3 months
[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1407:
-------------------------------------
It should be trivial to do that *today* for JDK orb with profiles as you can activate a profile by the presence of a file, e.g. JAVA_HOME/lib/orb.idl. However, JacORB would be in the classpath unless you specifically disabled it with a different profile so its presence would be guaranteed. Now, in the future when AS7-5582 is implemented, the "JDK" orb will be a maven dependency (same as JacORB), i.e. it will be available by default in the classpath.
Lets say we made the change today as a convenience until AS7-5582 is available, the question is do we really want to have unpredictable results in the build. Lets say the user attempts this new default, detection based build but does still expect both a JDK orb and JacORB version but we as can't locate orb.idl (say they are on pi) and just build the JacORB version - what would you expect then, log a warning?
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Time Spent: 2 days, 5 hours, 50 minutes
> Remaining Estimate: 2 hours
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
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, 3 months
[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1407:
-----------------------------------
Having the profile option is a minimum requirement, but it would also be nice if the build system could auto-detect the presence of one or both of the ORBs and build accordingly.
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Time Spent: 2 days, 5 hours, 50 minutes
> Remaining Estimate: 2 hours
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
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, 3 months
[JBoss JIRA] (JBTM-1405) idlj issue when building on Raspberry Pi
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1405?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1405:
-----------------------------------
I think this issue can be closed once we have a way to build without the jdk orb.
> idlj issue when building on Raspberry Pi
> ----------------------------------------
>
> Key: JBTM-1405
> URL: https://issues.jboss.org/browse/JBTM-1405
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Environment: Raspberry Pi with stock distribution installed and openjdk 6.
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> Early in the build we get ...
> [INFO] Processing 3 grammar files to /home/pi/narayana/ArjunaJTS/idl/idlj/target/generated-sources/idl
> [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [INFO] [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> [ERROR] /home/pi/narayana/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl (line 35): java.io.FileNotFoundException: orb.idl
> #include <orb.idl>
> ^
> And eventually this results in ...
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4:03:24.556s
> [INFO] Finished at: Sat Dec 22 20:32:47 UTC 2012
> [INFO] Final Memory: 38M/105M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test (surefire-idlj) on project jts: Execution surefire-idlj of goal org.apache.maven.plugins:maven-surefire-plugin:2.9:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null: org/omg/CosTransactions/ResourceOperations: org.omg.CosTransactions.ResourceOperations -> [Help 1]
> It would also be good if there was a build-time switch to disable using idlj. Building with the idlj option at the start (as mentioned in the README) would imply that this is the way to go and that building just using jts therefore only uses jacorb, but it seems that the jts rule builds with both orbs.
--
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, 3 months
[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris logged work on JBTM-1407:
-----------------------------------------
Author: Gytis Trikleris
Created on: 24/Jan/13 12:32 PM
Start Date: 24/Jan/13 11:31 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Time Spent: 2 days, 5 hours, 50 minutes (was: 2 days, 4 hours, 50 minutes)
Worklog Id: (was: 12428504)
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Time Spent: 2 days, 5 hours, 50 minutes
> Remaining Estimate: 2 hours
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
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, 3 months