[JBoss JIRA] (WFLY-7916) Undertow listener wrong type INT/LONG
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-7916?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-7916:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> Undertow listener wrong type INT/LONG
> -------------------------------------
>
> Key: WFLY-7916
> URL: https://issues.jboss.org/browse/WFLY-7916
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Bogdan Sikora
> Assignee: Brian Stansberry
> Fix For: 11.0.0.Alpha1
>
>
> Description of the "max-post-size" stays
> {noformat}
> "max-post-size" => {
> "type" => LONG,
> "description" => "The maximum size of a post that will be accepted, in bytes.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => 10485760L,
> "unit" => "BYTES",
> "min" => 1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> {noformat}
> but when trying to set long value this error is printed.
> {noformat}
> [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=max-post-size, value=9223372036854775807)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0097: Wrong type for 'max-post-size'. Expected [INT] but was STRING. Couldn't convert \"9223372036854775807\" to [INT]",
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-7903) Requests which are being proxied are not logged in access log
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-7903?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-7903:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> Requests which are being proxied are not logged in access log
> -------------------------------------------------------------
>
> Key: WFLY-7903
> URL: https://issues.jboss.org/browse/WFLY-7903
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Fix For: 11.0.0.Alpha1
>
>
> If I defined undertow as proxy (with mod_cluster filter), and enable access-log then for requests against proxy which are at the end handled by one of the workers are not logged in access log.
> There are logged only requests which are being directly handled by balancer (and not the one balanced to workers)
> I believe that with enabled access log on balancer all requests should be logged.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8439) Unregistering node throws error: MEM: Can't update or insert context
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-8439?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-8439:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> Unregistering node throws error: MEM: Can't update or insert context
> --------------------------------------------------------------------
>
> Key: WFLY-8439
> URL: https://issues.jboss.org/browse/WFLY-8439
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster, Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Tomaz Cerar
> Labels: mod_cluster
> Fix For: 11.0.0.Beta1
>
>
> New error message in proxy balancer log
> {noformat}
> 2017-03-21 15:22:24,957 INFO [io.undertow] (default task-23) UT005047: Unregistering context wildfly-services, from node jboss-eap-7.1-1
> 2017-03-21 15:22:24,962 ERROR [io.undertow] (default task-23) UT005043: Error in processing MCMP commands: Type:MEM, Mess: MEM: Can't update or insert context
> 2017-03-21 15:22:28,694 INFO [io.undertow] (default task-29) UT005047: Unregistering context wildfly-services, from node jboss-eap-7.1-2
> 2017-03-21 15:22:28,696 ERROR [io.undertow] (default task-29) UT005043: Error in processing MCMP commands: Type:MEM, Mess: MEM: Can't update or insert context
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-7267) [Proxy] No failover on empty response from node
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-7267?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-7267:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> [Proxy] No failover on empty response from node
> -----------------------------------------------
>
> Key: WFLY-7267
> URL: https://issues.jboss.org/browse/WFLY-7267
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Fix For: 11.0.0.Alpha1
>
>
> Undertow balancer do not recognizes empty response as an error.
> Can happen when JVM got killed when handling request (System.exit())
> {code}
> @Override
> public void failed(final HttpServerExchange exchange) {
> final long time = System.currentTimeMillis();
> if (tries++ < maxRetryAttempts) {
> ...
> {code}
> Undertow make curl hang.
> Apache httpd correctly recognizes empty response as error and starts fail over method. If unsuccessful, 50x is returned in response.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8119) NPE in mod_cluster stopping
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-8119?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-8119:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> NPE in mod_cluster stopping
> ---------------------------
>
> Key: WFLY-8119
> URL: https://issues.jboss.org/browse/WFLY-8119
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 10.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 11.0.0.Alpha1
>
>
> Don't know what causing it or how to reproduce it.
> It started to show with EAP 7.1.0.DR10.
> At first glance it shows quite randomly without any significant effect on server
> {noformat}
> 2017-01-11 08:29:19,989 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.4.8.Final-redhat-1 stopping
> 2017-01-11 08:29:20,108 ERROR [org.jboss.mod_cluster.undertow] (UndertowEventHandlerAdapter - 1) null: java.lang.NullPointerException
> at org.jboss.modcluster.ModClusterService.connectionEstablished(ModClusterService.java:305)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:392)
> at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.status(DefaultMCMPHandler.java:365)
> at org.jboss.modcluster.ModClusterService.status(ModClusterService.java:454)
> at org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapter.run(UndertowEventHandlerAdapter.java:179)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> http://paste.fedoraproject.org/530763/30767148/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-7496) Non complete resource description
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-7496?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-7496:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> Non complete resource description
> ---------------------------------
>
> Key: WFLY-7496
> URL: https://issues.jboss.org/browse/WFLY-7496
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Fix For: 11.0.0.Alpha1
>
>
> Missing time unit
> {noformat}
> "session-timeout" => {
> "type" => INT,
> "description" => "The session timeout for sessions that are owned by crawlers",
> "expressions-allowed" => true,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> "timeout" => {
> "type" => INT,
> "description" => "The request timeout",
> "expressions-allowed" => false,
> "nillable" => true,
> "access-type" => "read-only",
> "storage" => "runtime"
> "connection-idle-timeout" => {
> "type" => INT,
> "description" => "The amount of time a connection can be idle before it will be closed. Connections will not time out once the pool size is down to the configured minimum (as configured by cached-connections-per-thread)",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 60L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> "max-request-time" => {
> "type" => INT,
> "description" => "The maximum time that a proxy request can be active for, before being killed. Defaults to unlimited",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => -1,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> {noformat}
> Description not fully understandable
> {noformat}
> "require-host-http11" => {
> "type" => BOOLEAN,
> "description" => "Require the Host header when using the HTTP/1.1 protocol",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> "proxy-address-forwarding" => {
> "type" => BOOLEAN,
> "description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {noformat}
> Name X Description
> {noformat}
> "disabled" => {
> "type" => BOOLEAN,
> "description" => "Enable the JSP container.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8291) mod_cluster operation descriptions only refer to Apache httpd
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-8291?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-8291:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> mod_cluster operation descriptions only refer to Apache httpd
> -------------------------------------------------------------
>
> Key: WFLY-8291
> URL: https://issues.jboss.org/browse/WFLY-8291
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 10.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> Please repair description in following operations as they are outdated, undertow proxy
> is able to process this messages.
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "disable",
> "description" => "Tell Apache httpd that all contexts of the node can't process new requests.",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "disable-context",
> "description" => "Tell Apache httpd that the context can't process new requests.",
> "request-properties" => {
> "virtualhost" => {
> "type" => STRING,
> "description" => "virtual host",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "context" => {
> "type" => STRING,
> "description" => "context",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> }
> },
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "enable",
> "description" => "Tell Apache httpd that all contexts of the node are ready receive requests.",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "enable-context",
> "description" => "Tell Apache httpd that the context is ready receive requests.",
> "request-properties" => {
> "virtualhost" => {
> "type" => STRING,
> "description" => "Virtual host",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "context" => {
> "type" => STRING,
> "description" => "Context",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> }
> },
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "stop",
> "description" => "Tell Apache httpd that all contexts of the node can't process requests.",
> "request-properties" => {"waittime" => {
> "type" => INT,
> "description" => "wait timeout",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => 10,
> "unit" => "SECONDS"
> }},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "stop-context",
> "description" => "Tell Apache httpd that the context can't process requests.",
> "request-properties" => {
> "virtualhost" => {
> "type" => STRING,
> "description" => "Virtual host",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "context" => {
> "type" => STRING,
> "description" => "Context",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "waittime" => {
> "type" => INT,
> "description" => "wait timeout",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => 10,
> "unit" => "SECONDS"
> }
> },
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8654) mod_cluster stop/stop-context(waittime=..) attribute description is wrong
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-8654?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-8654:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> mod_cluster stop/stop-context(waittime=..) attribute description is wrong
> -------------------------------------------------------------------------
>
> Key: WFLY-8654
> URL: https://issues.jboss.org/browse/WFLY-8654
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 11.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 11.0.0.Beta1
>
>
> Cli operation description
> {noformat}
> [standalone@localhost:9990 /] /subsystem=modcluster/:read-operation-description(name=stop
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "stop",
> "description" => "Tell reverse proxies that all contexts on the node can't process requests.",
> "request-properties" => {"waittime" => {
> "type" => INT,
> "description" => "Timeout to wait for all contexts to stop.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => 10,
> "unit" => "SECONDS"
> }},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> Documentation
> {noformat}
> Stopping a context with waittime set to 0, meaning no timeout, instructs the balancer to stop routing any request to it immediately, which forces failover to another available context.
> If you set a timeout value using the waittime argument, no new sessions are created on this context, but existing sessions will continue to be directed to this node until they complete or the specified timeout has elapsed. The waittime argument defaults to 10 seconds.
> {noformat}
> There is difference, documentation basically says that till timeout is hit, node is disabled, cli description isn't that specific. Could you elaborate this?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8304) mod_cluster max-attempts minimal value
by Jan Stefl (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Jan Stefl updated WFLY-8304:
----------------------------
Tester: Jan Kašík (was: Bogdan Sikora)
> mod_cluster max-attempts minimal value
> --------------------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months