[JBoss JIRA] (WFLY-2760) Intermittent failure of ExternalContextBindingTestCase
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2760?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2760:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1061618|https://bugzilla.redhat.com/show_bug.cgi?id=1061618] from VERIFIED to CLOSED
> Intermittent failure of ExternalContextBindingTestCase
> -------------------------------------------------------
>
> Key: WFLY-2760
> URL: https://issues.jboss.org/browse/WFLY-2760
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.0.0.CR1
> Reporter: Jan Martiska
> Assignee: Jan Martiska
> Priority: Minor
>
> The server setup task sometimes fails to start the ApacheDS server instance because for some reason, BouncyCastle security provider doesn't get registered (it is added through a maven dependency rather than added to the JDK). This leads to a "connection refused" error during the test when it is trying to connect to the LDAP instance.
> It worked for us if we just programatically forced registration of the BouncyCastleProvider before the initialization of ApacheDS.
--
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
12 years, 4 months
[JBoss JIRA] (WFLY-2633) Cannot use deployments with same runtime-name in a domain
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2633?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2633:
-----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1039699|https://bugzilla.redhat.com/show_bug.cgi?id=1039699] from VERIFIED to CLOSED
> Cannot use deployments with same runtime-name in a domain
> ---------------------------------------------------------
>
> Key: WFLY-2633
> URL: https://issues.jboss.org/browse/WFLY-2633
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.CR1
>
>
> The check for duplicate runtime-name in a server group on startup is too aggressive. It is incorrectly throwing an error on startup if there are any duplicate runtime-names in the whole domain, instead of just in a single server group.
> Steps to Reproduce:
> 1. Start a single HC/DC
> 2. deploy --name=foo1 --runtime-name=bar --disabled testfile
> 3. deploy --name=foo2 --runtime-name=bar --disabled testfile
> 4. restart the DC/HC
> Actual results:
> JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> ...
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1348,9]
> ...
> Message: JBAS014664: An element of this type named 'bar' has already been declared
> Expected results:
> No errors
--
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
12 years, 4 months