[JBoss JIRA] (WFLY-9962) ReverseProxyTestCase fails when running after ForwardedHandlerTestCase
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9962?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-9962:
-----------------------------
Description:
When ForwardedHandlerTestCase installs {{/subsystem=undertow/configuration=filter/expression-filter=ff}}, even through it removes it after, {{/proxy}} location defined as part of ReverseProxyTestCase setup returns error 404:
{code}
testReverseProxy(org.jboss.as.test.integration.web.reverseproxy.ReverseProxyTestCase) Time elapsed: 0.087 sec <<< FAILURE!
java.lang.AssertionError: expected:<200> but was:<404>
{code}
* Direct calling of {{/server1/name}} and {{/server2/name}} from the same tests gives 200 correctly.
* When I comment out the ff filter setup (or skip whole ForwardedHandlerTestCase), ReverseProxyTestCase suceed.
* When I copy configuration and deployments from running test and run in standalone server outside of test, proxy works correctly.
As it is unrelated to my original issue in the end, keeping unassigned.
was:
When ForwardedHandlerTestCase installs {{/subsystem=undertow/configuration=filter/expression-filter=ff}}, even through it removes it after, {{/proxy}} location defined as part of ReverseProxyTestCase setup returns error 404:
{code}
testReverseProxy(org.jboss.as.test.integration.web.reverseproxy.ReverseProxyTestCase) Time elapsed: 0.087 sec <<< FAILURE!
java.lang.AssertionError: expected:<200> but was:<404>
{code}
* Direct calling of {{/server1/name}} and {{/server2/name}} from the same tests gives 200 correctly.
* When I comment out the ff filter setup (or skip whole ForwardedHandlerTestCase), ReverseProxyTestCase suceed.
* When I copy configuration and deployments from running test and run in standalone server outside of test, proxy works correctly.
As it is unrelated to my original issue in the end, keeping unresolved for now.
> ReverseProxyTestCase fails when running after ForwardedHandlerTestCase
> ----------------------------------------------------------------------
>
> Key: WFLY-9962
> URL: https://issues.jboss.org/browse/WFLY-9962
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
>
> When ForwardedHandlerTestCase installs {{/subsystem=undertow/configuration=filter/expression-filter=ff}}, even through it removes it after, {{/proxy}} location defined as part of ReverseProxyTestCase setup returns error 404:
> {code}
> testReverseProxy(org.jboss.as.test.integration.web.reverseproxy.ReverseProxyTestCase) Time elapsed: 0.087 sec <<< FAILURE!
> java.lang.AssertionError: expected:<200> but was:<404>
> {code}
> * Direct calling of {{/server1/name}} and {{/server2/name}} from the same tests gives 200 correctly.
> * When I comment out the ff filter setup (or skip whole ForwardedHandlerTestCase), ReverseProxyTestCase suceed.
> * When I copy configuration and deployments from running test and run in standalone server outside of test, proxy works correctly.
> As it is unrelated to my original issue in the end, keeping unassigned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9962) ReverseProxyTestCase fails when running after ForwardedHandlerTestCase
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9962?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-9962:
----------------------------------
I looks the problem is resolved when server reload is added into ForwaredHandlerTestCase:
{code}
ServerReload.executeReloadAndWaitForCompletion(managementClient.getControllerClient());
{code}
But it reveals deeper problem - it looks the missing reload was hiding failures:
{code}
testRewriteWithUndertowHandlers(org.jboss.as.test.integration.web.handlers.ForwardedHandlerTestCase) Time elapsed: 0.036 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:</1[92.121.210.60:455|https|/203.0.113.43:777]> but was:</1[27.0.0.1:46926|http|/127.0.0.1:8080]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.as.test.integration.web.handlers.ForwardedHandlerTestCase.commonTestPart(ForwardedHandlerTestCase.java:165)
at org.jboss.as.test.integration.web.handlers.ForwardedHandlerTestCase.testRewriteWithUndertowHandlers(ForwardedHandlerTestCase.java:123)
{code}
[~jstourac] as you are author of ForwardedHandlerTestCase, maybe you want to check?
> ReverseProxyTestCase fails when running after ForwardedHandlerTestCase
> ----------------------------------------------------------------------
>
> Key: WFLY-9962
> URL: https://issues.jboss.org/browse/WFLY-9962
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
>
> When ForwardedHandlerTestCase installs {{/subsystem=undertow/configuration=filter/expression-filter=ff}}, even through it removes it after, {{/proxy}} location defined as part of ReverseProxyTestCase setup returns error 404:
> {code}
> testReverseProxy(org.jboss.as.test.integration.web.reverseproxy.ReverseProxyTestCase) Time elapsed: 0.087 sec <<< FAILURE!
> java.lang.AssertionError: expected:<200> but was:<404>
> {code}
> * Direct calling of {{/server1/name}} and {{/server2/name}} from the same tests gives 200 correctly.
> * When I comment out the ff filter setup (or skip whole ForwardedHandlerTestCase), ReverseProxyTestCase suceed.
> * When I copy configuration and deployments from running test and run in standalone server outside of test, proxy works correctly.
> As it is unrelated to my original issue in the end, keeping unresolved for now.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9962) ReverseProxyTestCase fails when running after ForwardedHandlerTestCase
by Jan Kalina (JIRA)
Jan Kalina created WFLY-9962:
--------------------------------
Summary: ReverseProxyTestCase fails when running after ForwardedHandlerTestCase
Key: WFLY-9962
URL: https://issues.jboss.org/browse/WFLY-9962
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 12.0.0.Final
Reporter: Jan Kalina
When ForwardedHandlerTestCase installs {{/subsystem=undertow/configuration=filter/expression-filter=ff}}, even through it removes it after, {{/proxy}} location defined as part of ReverseProxyTestCase setup returns error 404:
{code}
testReverseProxy(org.jboss.as.test.integration.web.reverseproxy.ReverseProxyTestCase) Time elapsed: 0.087 sec <<< FAILURE!
java.lang.AssertionError: expected:<200> but was:<404>
{code}
* Direct calling of {{/server1/name}} and {{/server2/name}} from the same tests gives 200 correctly.
* When I comment out the ff filter setup (or skip whole ForwardedHandlerTestCase), ReverseProxyTestCase suceed.
* When I copy configuration and deployments from running test and run in standalone server outside of test, proxy works correctly.
As it is unrelated to my original issue in the end, keeping unresolved for now.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent
by cnsgithub cnsgithub (JIRA)
[ https://issues.jboss.org/browse/WFLY-9417?page=com.atlassian.jira.plugin.... ]
cnsgithub cnsgithub commented on WFLY-9417:
-------------------------------------------
Still wrong in WF12, especially for long-lasting deployment this is causing some trouble for us, as a frontend server will not respond as long as the server is deploying instead of showing an error code during deployment.
Any fix in sight? Or reasonable workaround? Is it possible to "force" the server to boot BEFORE doing any deployment?
> No default-response-code during deployment sent
> -----------------------------------------------
>
> Key: WFLY-9417
> URL: https://issues.jboss.org/browse/WFLY-9417
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 11.0.0.CR1
> Reporter: Nero M
> Assignee: Stuart Douglas
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10.
> When a *.dodeploy file exists during server-start. The Default response code
> e.g.
> <host name="default-host" alias="localhost" default-response-code="503">
> Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout.
> If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete.
> (After this line): WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms
> I think the server should not "hang" during the deployment-time, just like it was on WF10.
> Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2368) Remove HasExpressionEditorControls
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2368:
--------------------------------------
Summary: Remove HasExpressionEditorControls
Key: DROOLS-2368
URL: https://issues.jboss.org/browse/DROOLS-2368
Project: Drools
Issue Type: Sub-task
Components: DMN Editor
Reporter: Michael Anstis
Assignee: Michael Anstis
When all "controls" are moved "inline" {{HasExpressionEditorControls}} and all use thereof can be deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months