[jbossts-issues] [JBoss JIRA] (JBTM-1149) Add some qa tests for the none-socket recovery manager

Fri Aug 23 09:41:27 EDT 2013

    [ https://issues.jboss.org/browse/JBTM-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798864#comment-12798864 ] 

Ondřej Chaloupka commented on JBTM-1149:
----------------------------------------

I've added the switch for test not trigger the recovery by socket push but by waiting for periodic time recovery trigger.
There were added two jobs based on this to release cycle testing and the same two to CI jobs.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbossts-crashrec-tests-oracle11gR2-master-no-scan-ci
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbossts-crashrec-tests-jms-master-no-scan-ci

I ran the jobs on my laptop and I didn't hit any issue. There is just some minor intermittent issue running these tests with Wildfly that time to time some test leave the jboss running and the following test fails at starting eap with socket not available error. When I will think that all is running I'll change the status of this task to resolved.

> Add some qa tests for the none-socket recovery manager
> ------------------------------------------------------
>
>                 Key: JBTM-1149
>                 URL: https://issues.jboss.org/browse/JBTM-1149
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>            Reporter: Tom Jenkinson
>            Assignee: Ondřej Chaloupka
>             Fix For: 5.0.0.Final
>
>
> By default the JBoss application server runs with a recovery manager that is not using a socket. We should try to add a crash recovery qa test that tests recovery in the different VMs but not by using the recovery manager socket API, rather waiting for periodic recovery.
> It is possible that there is a test for this, @ochaloup, in which case this issue can be closed as out of date

--
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