[ https://issues.jboss.org/browse/WFLY-2876?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2876:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Add mod_cluster support for all Undertow servers, not only the default-server
> -----------------------------------------------------------------------------
>
> Key: WFLY-2876
> URL: https://issues.jboss.org/browse/WFLY-2876
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Alpha3
>
>
> Currently only the default host is registered with the proxy.
> This will require:
> * configuration change for listener<>host mapping
> * instance-id be configured per server, instead of per whole undertow subsystem (or just appended to the unique server name)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/WFLY-2824?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2824:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Remove https://issues.apache.org/jira/browse/DIRAPI-125 workaround
> -------------------------------------------------------------------
>
> Key: WFLY-2824
> URL: https://issues.jboss.org/browse/WFLY-2824
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 8.0.0.CR1
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
> Fix For: 10.0.0.Alpha3
>
>
> As a workaround for an Apache DS bug (https://issues.apache.org/jira/browse/DIRAPI-125) we forked their LdapUrl class in the testsuite/integration/basic module. This JIRA is a reminder to check if the upstream bug is fixed and the fix is in the release WF uses; if so remove the workaround.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/WFLY-3064?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-3064:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case.
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3064
> URL: https://issues.jboss.org/browse/WFLY-3064
> Project: WildFly
> Issue Type: Sub-task
> Components: Test Suite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 10.0.0.Alpha3
>
>
> A new test case was added under WFLY-3063 that demonstrates the correct way to do this so now remove the original way that depended on internal APIs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/WFLY-2982?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-2982:
-------------------------------
Fix Version/s: 10.0.0.Alpha3
(was: 10.0.0.Alpha2)
> refactor two phase persistence unit services (PhaseOnePersistenceUnitServiceImpl + PersistenceUnitServiceImpl) into one service
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2982
> URL: https://issues.jboss.org/browse/WFLY-2982
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 10.0.0.Alpha3
>
>
> Related feedback from https://github.com/wildfly/wildfly/pull/4722:
> {quote}
> This is asymetrical, so if this service , and phase one are stopped, and then phase 1 is started again, phase 2 will appear started. The side effects seem minor though
> {quote}
> {quote}
> We have a long term goal to somehow verify every service can be stopped and started with the expected effect. Right now many of our services are not restartable which makes potential new features like partial deployment standby hard to achieve. So Im just offering pointers whenever I see lifecycle symmetry issues.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)