[
https://issues.jboss.org/browse/WFLY-3862?page=com.atlassian.jira.plugin....
]
Petr Kremensky edited comment on WFLY-3862 at 9/24/14 5:33 AM:
---------------------------------------------------------------
Moving discussion from WFLY-3890
Tomaz Cerar added a comment - 9 minutes ago
No! proper fix is to do proper cleanup of vault files as it usually breaks because of
leftovers or some corrupt vault.dat stuff.
Petr Kremensky added a comment - 2 minutes ago
Than we have to look more into WFLY-3778 as that is why this issue occures. Please see
https://bugzilla.redhat.com/show_bug.cgi?id=1136220#c5
was (Author: pkremens):
Tomaz Cerar added a comment - 9 minutes ago
No! proper fix is to do proper cleanup of vault files as it usually breaks because of
leftovers or some corrupt vault.dat stuff.
Petr Kremensky added a comment - 2 minutes ago
Than we have to look more into WFLY-3778 as that is why this issue occures. Please see
https://bugzilla.redhat.com/show_bug.cgi?id=1136220#c5
Run HTTPSConnectionWithCLITestCase and
VaultPasswordsInCLITestCase.java with standalone profile
-----------------------------------------------------------------------------------------------
Key: WFLY-3862
URL:
https://issues.jboss.org/browse/WFLY-3862
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Petr Kremensky
Assignee: Petr Kremensky
HTTPSConnectionWithCLITestCase and VaultPasswordsInCLITestCase.java secures management
interface with SSL, but they sometimes fail to unsecure it due to problem mentioned in
WFLY-3778. We should use different configuration to avoid breaking whole manual-mode
module due to this (other tests cannot use secured server).
Also change tests to use :*reload* command instead of *reload* operation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)