[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1838:
-------------------------------------
Simplest approach is to move the gist into a quickstart. We can do something better in the future.
> Document how to configure XTS to use SSL
> ----------------------------------------
>
> Key: JBTM-1838
> URL: https://issues.jboss.org/browse/JBTM-1838
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, Documentation
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
> Original Estimate: 1 day
> Time Spent: 1 day
> Remaining Estimate: 4 hours
>
> The documentation should show how to use 'https' for all communications.
> I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS.
> We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart.
> Other options are a community wiki page or blog posting.
--
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, 2 months
[JBoss JIRA] (JBTM-1674) btadmin.PauseDomainTest failed with ArrayIndexOutOfBoundsException
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1674?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1674:
--------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.0.0.Final)
> btadmin.PauseDomainTest failed with ArrayIndexOutOfBoundsException
> ------------------------------------------------------------------
>
> Key: JBTM-1674
> URL: https://issues.jboss.org/browse/JBTM-1674
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 6.0.0.Final
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1501
> {noformat}
> -------------------------------------------------------------------------------
> Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE!
> testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command failed
> at junit.framework.Assert.fail(Assert.java:47)
> at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
> at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
> at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at com.sun.proxy.$Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> {noformat}
--
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, 2 months
[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1683:
--------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.0.0.Final)
> btadmin tests on windows failed with "Could not start the server"
> -----------------------------------------------------------------
>
> Key: JBTM-1683
> URL: https://issues.jboss.org/browse/JBTM-1683
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 6.0.0.Final
>
>
> http://172.17.131.2/job/blacktie-windows2008-taconic/272
> {code}
> Failed tests:
> testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful
> testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server
> testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server
> testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful
> testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server
> {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, 2 months
[JBoss JIRA] (JBTM-1969) Test Narayana with released version of WildFly
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1969:
-----------------------------------
Summary: Test Narayana with released version of WildFly
Key: JBTM-1969
URL: https://issues.jboss.org/browse/JBTM-1969
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.Final
There is a hole a the moment. We test Narayana when it is integrated into the nightly WildFly but we don't retest when WildFly is released. For example M4 is in Beta1 but we haven't retested the QS with that _released_ version.
We should have a CI job that tests the final version of WildFly.
Maybe the QS release job should be tracking the WildFly branch and retesting when changes are added there.
--
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, 2 months