[JBoss JIRA] (JBTM-1647) narayana.sh expects DB drivers to be available locally
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1647?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1647:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> narayana.sh expects DB drivers to be available locally
> ------------------------------------------------------
>
> Key: JBTM-1647
> URL: https://issues.jboss.org/browse/JBTM-1647
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M3
>
>
> From talking to Jonathan and Mike, my understanding is that narayana.sh should wget the DB drivers from albany. Instead it relies on them being available in /home/hudson/dbdrivers. The problem with this approach is that it requires setting up every time we add a new machine in the pool, or add new drivers.
> Here's what happens when you run the Oracle JDBC job on a machine with no /home/hudson/dbdrivers:
> {code}
> Started by upstream project "jbossts-EAP61-jdbcobjectstore-haverstraw-oracle" build number 1
> originally caused by:
> Started by user anonymous
> Building remotely on haverstraw in workspace /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw
> Checkout:haverstraw / /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw - hudson.remoting.Channel@4376502f:haverstraw
> Using strategy: Default
> Cloning the remote Git repository
> Cloning repository git://github.com/jbosstm/narayana.git
> git --version
> git version 1.7.1
> Fetching upstream changes from origin
> Commencing build of Revision dc53acf1f5faffeb92ecabba85a6877bc699ada0 (origin/4.17)
> Checking out Revision dc53acf1f5faffeb92ecabba85a6877bc699ada0 (origin/4.17)
> No change to record in branch origin/4.17
> [haverstraw] $ /bin/bash -xe /tmp/hudson5928481526507148318.sh
> + export ANT_HOME=/home/hudson/apache-ant-1.8.2
> + ANT_HOME=/home/hudson/apache-ant-1.8.2
> + export PATH=/home/hudson/apache-ant-1.8.2/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.7.0_09/bin:/usr/local/bin:/bin:/usr/bin
> + PATH=/home/hudson/apache-ant-1.8.2/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.7.0_09/bin:/usr/local/bin:/bin:/usr/bin
> + export MFACTOR=2
> + MFACTOR=2
> + rm -rf /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/ext/../qa/dbdrivers/
> + cd /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/
> + ant get.drivers -Ddriver.url=file:///home/hudson/dbdrivers
> Buildfile: /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/build.xml
> clean-dbdrivers:
> get.drivers:
> [mkdir] Created dir: /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/dbdrivers/oracle_10_2_0_4
> [get] Getting: file:/home/hudson/dbdrivers/ojdbc14.jar
> [get] To: /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/dbdrivers/oracle_10_2_0_4/ojdbc14.jar
> [get] Error getting file:/home/hudson/dbdrivers/ojdbc14.jar to /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/dbdrivers/oracle_10_2_0_4/ojdbc14.jar
> BUILD FAILED
> /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/build.xml:66: java.io.FileNotFoundException: /home/hudson/dbdrivers/ojdbc14.jar (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:120)
> at java.io.FileInputStream.<init>(FileInputStream.java:79)
> at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
> at org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:660)
> at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:579)
> at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:569)
> Total time: 0 seconds
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Sending e-mails to: gtrikler(a)redhat.com
> Finished: FAILURE
> {code}
--
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, 4 months
[JBoss JIRA] (JBTM-1472) Initial version of Compensations API
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1472:
--------------------------------
Remaining Estimate: 3 days (was: 1 week, 4 days, 2 hours)
> Initial version of Compensations API
> ------------------------------------
>
> Key: JBTM-1472
> URL: https://issues.jboss.org/browse/JBTM-1472
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 weeks
> Time Spent: 1 week, 6 hours
> Remaining Estimate: 3 days
>
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
> This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
> Tasks:
> # Investigate existing WS-BA APIs
> ## Try code examples if possible
> # Produce an initial list of features that should be covered by the API
> # Create a simple implementation backed by WS-BA.
> Implementation work, to complete this issue:
> # Manage lifecycle of transaction via the @Compensatable annotation
> # Allow Compensation and Completion handlers to be registered via annotations
> # Mechanism for allowing application to mark the transaction as CompensateOnly
> # Document the API
> # Merge into Narayana code base
> # OOTB support in WildFly
--
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, 4 months
[JBoss JIRA] (JBTM-1472) Initial version of Compensations API
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1472:
--------------------------------
Description:
We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
Tasks:
# Investigate existing WS-BA APIs
## Try code examples if possible
# Produce an initial list of features that should be covered by the API
# Create a simple implementation backed by WS-BA.
Implementation work, to complete this issue:
# Manage lifecycle of transaction via the @Compensatable annotation
# Allow Compensation and Completion handlers to be registered via annotations
# Mechanism for allowing application to mark the transaction as CompensateOnly
# Document the API
# Merge into Narayana code base
# OOTB support in WildFly
was:
We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
Tasks:
# Investigate existing WS-BA APIs
## Try code examples if possible
# Produce an initial list of features that should be covered by the API
# Create a simple implementation backed by WS-BA.
> Initial version of Compensations API
> ------------------------------------
>
> Key: JBTM-1472
> URL: https://issues.jboss.org/browse/JBTM-1472
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 weeks
> Time Spent: 1 week, 6 hours
> Remaining Estimate: 1 week, 4 days, 2 hours
>
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
> This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
> Tasks:
> # Investigate existing WS-BA APIs
> ## Try code examples if possible
> # Produce an initial list of features that should be covered by the API
> # Create a simple implementation backed by WS-BA.
> Implementation work, to complete this issue:
> # Manage lifecycle of transaction via the @Compensatable annotation
> # Allow Compensation and Completion handlers to be registered via annotations
> # Mechanism for allowing application to mark the transaction as CompensateOnly
> # Document the API
> # Merge into Narayana code base
> # OOTB support in WildFly
--
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, 4 months
[JBoss JIRA] (JBTM-1472) Initial version of Compensations API
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ]
Paul Robinson edited comment on JBTM-1472 at 5/7/13 5:57 AM:
-------------------------------------------------------------
Current working area:
https://github.com/paulrobinson/compensations
was (Author: paul.robinson):
Current working area:
https://github.com/paulrobinson/compensations
Not yet implemented:
# Integrate into Narayana+WildFly code-base
# Distribution over WS-BA.
# Enable interceptors by default (CDI 1.1 feature)
# @Transactional like behaviour
# @CompensationScoped: Align with JTA 1.2 and document
# integration with @Transactional
# Document existing API
# Durability of compensation data
# bridging to JTA
# 2PC participants
# Local-only performance optimisations
# EJB support
> Initial version of Compensations API
> ------------------------------------
>
> Key: JBTM-1472
> URL: https://issues.jboss.org/browse/JBTM-1472
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 weeks
> Time Spent: 1 week, 6 hours
> Remaining Estimate: 3 days
>
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
> This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
> Tasks:
> # Investigate existing WS-BA APIs
> ## Try code examples if possible
> # Produce an initial list of features that should be covered by the API
> # Create a simple implementation backed by WS-BA.
> Implementation work, to complete this issue:
> # Manage lifecycle of transaction via the @Compensatable annotation
> # Allow Compensation and Completion handlers to be registered via annotations
> # Mechanism for allowing application to mark the transaction as CompensateOnly
> # Document the API
> # Merge into Narayana code base
> # OOTB support in WildFly
--
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, 4 months
[JBoss JIRA] (JBTM-1660) Implement JTA 1.2 @Transactional feature
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1660?focusedWorklogId=12429121&page=... ]
Paul Robinson logged work on JBTM-1660:
---------------------------------------
Author: Paul Robinson
Created on: 07/May/13 5:49 AM
Start Date: 07/May/13 5:49 AM
Worklog Time Spent: 1 day
Issue Time Tracking
-------------------
Remaining Estimate: 3 days (was: 4 days)
Time Spent: 1 day
Worklog Id: (was: 12429121)
> Implement JTA 1.2 @Transactional feature
> ----------------------------------------
>
> Key: JBTM-1660
> URL: https://issues.jboss.org/browse/JBTM-1660
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M3
>
> Original Estimate: 4 days
> Time Spent: 1 day
> Remaining Estimate: 3 days
>
> Implement Section "3.7 Transactional Annotation" of the JTA 1.2 specification.
--
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, 4 months
[JBoss JIRA] (JBTM-1472) Initial version of Compensations API
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1472:
--------------------------------
Summary: Initial version of Compensations API (was: Initial work on Compensations API)
> Initial version of Compensations API
> ------------------------------------
>
> Key: JBTM-1472
> URL: https://issues.jboss.org/browse/JBTM-1472
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 weeks
> Time Spent: 1 week, 6 hours
> Remaining Estimate: 1 week, 4 days, 2 hours
>
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
> This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
> Tasks:
> # Investigate existing WS-BA APIs
> ## Try code examples if possible
> # Produce an initial list of features that should be covered by the API
> # Create a simple implementation backed by WS-BA.
--
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, 4 months