[JBoss JIRA] (JBTM-1635) Enhance TRACE for delistResource
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBTM-1635:
-------------------------------------
Summary: Enhance TRACE for delistResource
Key: JBTM-1635
URL: https://issues.jboss.org/browse/JBTM-1635
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.17.3
Reporter: Jesper Pedersen
Assignee: Tom Jenkinson
Priority: Minor
The following
{noformat}
TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.delistResource
{noformat}
statement would benefit for logging the actual TM flag sent
--
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, 7 months
[JBoss JIRA] (JBTM-1636) Enhance TRACE for getStatus
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBTM-1636:
-------------------------------------
Summary: Enhance TRACE for getStatus
Key: JBTM-1636
URL: https://issues.jboss.org/browse/JBTM-1636
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.17.3
Reporter: Jesper Pedersen
Assignee: Tom Jenkinson
Priority: Minor
The following
{noformat}
TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.getStatus
{noformat}
statement would benefit from logging the actual return value sent to the caller
--
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, 7 months
[JBoss JIRA] (JBTM-1522) "no XTS application recovery module found" during XTS Recovery Tests
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1522?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1522:
-------------------------------------
Amos,
Can you rebase your branch, as it is currently failing due to a number of, now fixed, issues.
> "no XTS application recovery module found" during XTS Recovery Tests
> --------------------------------------------------------------------
>
> Key: JBTM-1522
> URL: https://issues.jboss.org/browse/JBTM-1522
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 4.17.4, 5.0.0.M3
>
> Attachments: 2013-04-01_jbtm-1522_outputs.zip, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit-output.txt, com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output-2.txt, com.arjuna.qa.junit.TestBACrashDuringCommit-output.txt, com.arjuna.qa.junit.TestBACrashDuringCommit.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit-output.txt, com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit.txt
>
>
> See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/211/artifact/XTS/...
> Notice the following log is displayed repeatedly until the test gives up waiting for recovery:
> {code}
> WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0
> {code}
> This error comes from org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple#recoverParticipants(). In particular:
> {code}
> if (!found) {
> // we failed to find a helper to convert a participant record so log a warning
> // but leave it in the table for next time
> RecoveryLogger.i18NLogger.warn_participant_at_XTSATRecoveryModule_4(participantRecoveryRecord.getId());
> }
> {code}
> It looks like the code is unable to restore the participant from the log due to restoreParticipant(XTSATRecoveryModule module) returning false. There is ParticipantRecoveryRecord in the log as you can see it dumped to the console in the above log. Maybe there is a problem with that log, or maybe we are missing another log entry?
> This problem is intermittent, so it's unlikely that you will see this happen when you attach a debugger. However, we could attach a debugger to see what happens in the normal case and also to inspect the log to see if anything is missing in the failing case. But I have a cunning plan...
> h4.Cunning Plan
> We need to get a copy of the failing log, before recovery is attempted. We should then be able to use that log to reproduce the issue on our own machines. Steps to take:
> # Update BaseCrashTest to copy the contents of the tx-object-store to a unique folder location (So we can retrieve it later for a failed run). Make sure you create the folder structure under target/surefire-reports so that CI archives it off. Do the copy between controller.kill and controller.start. This way we get the log before the recovery manager has had chance to tamper with it.
> # Update the "narayana-JBTM-1522" job in CI to use your branch, containing the change above.
> # Configure the job to run @hourly until it fails with this problem.
> # Take a copy of the tx-object-store from the failing test and then put it in place on your AS8 build.
> # Boot the AS and confirm that the issue is reproduced.
> # You can now keep putting the tx-object-store back in place every time you need to reproduce the issue.
> # Attach a debugger to find out what the problem 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, 7 months
[JBoss JIRA] (JBTM-1617) When testing pull requests do a rebase to the merge point
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1617?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris reopened JBTM-1617:
-----------------------------------
Move rebase code to the separate script file to allow narayana.sh rebase
> When testing pull requests do a rebase to the merge point
> ---------------------------------------------------------
>
> Key: JBTM-1617
> URL: https://issues.jboss.org/browse/JBTM-1617
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Priority: Critical
> Fix For: 4.17.4, 5.0.0.M3
>
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> These instructions can go in the pull job config rather than narayana.sh I think as they do a full clean and that would be dangerous on a dev box
> # Clean up the local repo
> git rebase --abort
> rm -rf .git/rebase-apply
> git clean -f -d -x
> # Work out the branch point
> git branch -D 4.17
> git branch 4.17 origin/4.17
> git branch -D master
> git branch master origin/master
> myRev=`git rev-parse HEAD`
> ancestor417=`git merge-base $myRev 4.17`
> ancestorMaster=`git merge-base $myRev master`
> distanceFromMaster=`git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '`
> distanceFrom417=`git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' '`
> if [ "$distanceFromMaster" -lt "$distanceFrom417" ]
> then
> export BRANCHPOINT=master
> else
> export BRANCHPOINT=4.17
> fi
> # Update the pull to head
> git pull --rebase --ff-only origin $BRANCHPOINT
> # if this fails ($? -ne 0) fail the build and tell the committer (commentOnPull) that they need to rebase
--
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, 7 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?page=com.atlassian.jira.plugin.... ]
Work on JBTM-1479 started by Gytis Trikleris.
> 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: 4 days, 6 hours, 30 minutes
> Remaining Estimate: 2 days
>
> 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, 7 months
[JBoss JIRA] (JBTM-1359) HA Recovery Manager
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1359:
-------------------------------------
I have updated the links reflect that this issue is actually the implementation of PRODMGT-405, rather than the PRODMGT-143
> HA Recovery Manager
> -------------------
>
> Key: JBTM-1359
> URL: https://issues.jboss.org/browse/JBTM-1359
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTA, JTS, Recovery, XTS
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Priority: Critical
> Fix For: 5.0.0.M3
>
> Original Estimate: 3 weeks
> Remaining Estimate: 3 weeks
>
> JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records)
--
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, 7 months
[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1634:
---------------------------------
[~mmusgrov] do you have any idea about this issue ? it happens when jboss-as uses undertow.
> TX tests failed with "Unable to start a new txn on URI"
> -------------------------------------------------------
>
> Key: JBTM-1634
> URL: https://issues.jboss.org/browse/JBTM-1634
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/246/
> http://172.17.131.2/job/blacktie-linux32/915/
> http://172.17.131.2/job/blacktie-linux64/1472/
> {code}
> 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager
> 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok
> 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1
> 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost
> 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13
> 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
> 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000
> 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096
> 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes
> 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
> Content-Length: 145
> Connection: keep-alive
> Content-Type: text/html
> Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager?
> 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found
> {code}
> It looks like restat-web.war has not regiter as /rest-tx
--
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, 7 months
[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1634:
----------------------------
Description:
http://172.17.131.2/job/blacktie-windows2008-taconic/246/
http://172.17.131.2/job/blacktie-linux32/915/
http://172.17.131.2/job/blacktie-linux64/1472/
{code}
2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager
2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok
2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1
2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost
2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13
2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000
2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096
2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes
2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
Content-Length: 145
Connection: keep-alive
Content-Type: text/html
Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager?
2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found
{code}
It looks like restat-web.war has not regiter as /rest-tx
was:
http://172.17.131.2/job/blacktie-windows2008-taconic/246/
http://172.17.131.2/job/blacktie-linux32/915/
http://172.17.131.2/job/blacktie-linux64/1472/
> TX tests failed with "Unable to start a new txn on URI"
> -------------------------------------------------------
>
> Key: JBTM-1634
> URL: https://issues.jboss.org/browse/JBTM-1634
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/246/
> http://172.17.131.2/job/blacktie-linux32/915/
> http://172.17.131.2/job/blacktie-linux64/1472/
> {code}
> 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager
> 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok
> 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1
> 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost
> 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13
> 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded
> 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000
> 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096
> 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes
> 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found
> Content-Length: 145
> Connection: keep-alive
> Content-Type: text/html
> Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager?
> 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found
> {code}
> It looks like restat-web.war has not regiter as /rest-tx
--
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, 7 months