[JBoss JIRA] (WFLY-5840) mod_cluster proxies doesn't accept expressions
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5840?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed WFLY-5840.
--------------------------------
Resolution: Rejected
> mod_cluster proxies doesn't accept expressions
> ----------------------------------------------
>
> Key: WFLY-5840
> URL: https://issues.jboss.org/browse/WFLY-5840
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Rafael Benevides
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> proxy-list was deprecated in WFLY-457
> Now I'm forced to use proxies but it doesn't accept expressions.
> I want to create a customisable Docker image with where the modcluster ip can be configured at runtime
> I'd like that Wildfly image to accept the following command but
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])}}
> {noformat}
> but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color}
> With
> {noformat}
> /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80)
> {noformat}
> it fails with {color:red}WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.{color}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFLY-5840) mod_cluster proxies doesn't accept expressions
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5840?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-5840 at 12/13/15 7:46 PM:
----------------------------------------------------------------
To understand an attribute, its best to read the description:
{noformat}
[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description
{
"outcome" => "success",
"result" => {
...
"description" => "List of proxies for mod_cluster to register with defined by outbound-socket-binding in socket-binding-group.",
{noformat}
What you want to use is this, run in a batch ideally:
{noformat}
[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=advertise,value=false
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=proxies,value=[proxy1]
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=proxy1:add(host=${modcluster.host:modcluster},port=${modcluster.port:80}
{
"outcome" => "success",
"response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9990 /] :reload
{
"outcome" => "success",
"result" => undefined
}
{noformat}
was (Author: rhusar):
To understand an attribute, its best to read the description:
{noformat}
[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description
{
"outcome" => "success",
"result" => {
...
"description" => "List of proxies for mod_cluster to register with defined by outbound-socket-binding in socket-binding-group.",
{noformat}
> mod_cluster proxies doesn't accept expressions
> ----------------------------------------------
>
> Key: WFLY-5840
> URL: https://issues.jboss.org/browse/WFLY-5840
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Rafael Benevides
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> proxy-list was deprecated in WFLY-457
> Now I'm forced to use proxies but it doesn't accept expressions.
> I want to create a customisable Docker image with where the modcluster ip can be configured at runtime
> I'd like that Wildfly image to accept the following command but
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])}}
> {noformat}
> but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color}
> With
> {noformat}
> /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80)
> {noformat}
> it fails with {color:red}WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.{color}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFLY-5840) mod_cluster proxies doesn't accept expressions
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5840?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-5840:
--------------------------------------
To understand an attribute, its best to read the description:
{noformat}
[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description
{
"outcome" => "success",
"result" => {
...
"description" => "List of proxies for mod_cluster to register with defined by outbound-socket-binding in socket-binding-group.",
{noformat}
> mod_cluster proxies doesn't accept expressions
> ----------------------------------------------
>
> Key: WFLY-5840
> URL: https://issues.jboss.org/browse/WFLY-5840
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Rafael Benevides
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> proxy-list was deprecated in WFLY-457
> Now I'm forced to use proxies but it doesn't accept expressions.
> I want to create a customisable Docker image with where the modcluster ip can be configured at runtime
> I'd like that Wildfly image to accept the following command but
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])}}
> {noformat}
> but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color}
> With
> {noformat}
> /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80)
> {noformat}
> it fails with {color:red}WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.{color}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFLY-5840) mod_cluster proxies doesn't accept expressions
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5840?page=com.atlassian.jira.plugin.... ]
Radoslav Husar reassigned WFLY-5840:
------------------------------------
Assignee: Radoslav Husar (was: Paul Ferraro)
> mod_cluster proxies doesn't accept expressions
> ----------------------------------------------
>
> Key: WFLY-5840
> URL: https://issues.jboss.org/browse/WFLY-5840
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Rafael Benevides
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> proxy-list was deprecated in WFLY-457
> Now I'm forced to use proxies but it doesn't accept expressions.
> I want to create a customisable Docker image with where the modcluster ip can be configured at runtime
> I'd like that Wildfly image to accept the following command but
> {noformat}
> /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies,value=[${modcluster.host:modcluster}:${modcluster.port:80}])}}
> {noformat}
> but if fails with:{color:red} "Services that may be the cause:" => ["jboss.outbound-socket-binding.\"${modcluster.host:modcluster}:${modcluster.port:80}\""]{color}
> With
> {noformat}
> /subsystem=modcluster/:add-proxy(host=${modcluster.host:modcluster},port=80)
> {noformat}
> it fails with {color:red}WFLYMODCLS0016: No IP address could be resolved for the specified host of the proxy.{color}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1214) Operation headers not propagated to domain servers when 'composite' op is used
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1214?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1214:
-------------------------------------
Description:
When the user adds request headers to an op, they are not propagated to the servers during domain rollout if the 'composite' op is involved.
For example, if I add some stdout printing of what the headers are on the various processes and invoke this:
{code}
[domain@localhost:9990 /] deploy ~/tmp/helloworld.war --headers={blocking-timeout=5;rollback-on-runtime-failure=false} --all-server-groups
{code}
Then on a HC with two servers, this is logged:
[Host Controller] 10:53:40,697 INFO [stdout] (management-handler-thread - 3) "composite" headers: {
[Host Controller] 10:53:40,697 INFO [stdout] (management-handler-thread - 3) "blocking-timeout" => "5",
[Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) "rollback-on-runtime-failure" => "false",
[Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) "caller-type" => "user",
[Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) "access-mechanism" => "NATIVE"
[Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) }
[Host Controller] 10:53:40,727 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /Users/bstansberry/dev/wildfly/wildfly-core/dist/target/wildfly-core-2.0.5.Final-SNAPSHOT/domain/data/content/6f/cd9eae343ed6d5aa9fffa83012d155b1ef911c/content
[Server:server-one] 10:53:40,772 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: null
[Server:server-two] 10:53:40,772 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: null
The HC logs, then the servers report. The user-specified headers are not included.
Invoke the same op without the batch and this is logged:
{code}
[Host Controller] 10:43:50,400 INFO [stdout] (management-handler-thread - 4) "composite" headers: {
[Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "blocking-timeout" => "5",
[Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "rollback-on-runtime-failure" => "false",
[Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "caller-type" => "user",
[Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "access-mechanism" => "NATIVE"
[Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) }
[Host Controller] 10:43:50,425 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /Users/bstansberry/dev/wildfly/wildfly-core/dist/target/wildfly-core-2.0.5.Final-SNAPSHOT/domain/data/content/6f/cd9eae343ed6d5aa9fffa83012d155b1ef911c/content
[Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: {
[Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "blocking-timeout" => "5",
[Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "rollback-on-runtime-failure" => "false",
[Server:server-one] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: {
[Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "access-mechanism" => "NATIVE",
[Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "blocking-timeout" => "5",
[Server:server-two] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "domain-uuid" => "216d2e99-dba5-4c89-8020-b0c16bd553c5"
[Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "rollback-on-runtime-failure" => "false",
[Server:server-two] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) }
[Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "access-mechanism" => "NATIVE",
[Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "domain-uuid" => "216d2e99-dba5-4c89-8020-b0c16bd553c5"
[Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) }
{code}
Expected headers are present.
Note the CLI 'deploy' is far from the only time the 'composite' op is used. Among other places, the high level CLI 'batch' command in a domain involves use of 'composite'.
was:
When the user adds request headers to an op, they are not propagated to the servers during domain rollout if the 'composite' op is involved.
For example, if I add some stdout printing of what the headers are on the various processes and invoke this:
{code}
[domain@localhost:9999 /] batch
[domain@localhost:9999 / #] /system-property=add(value=bar){blocking-timeout=10;rollback-on-runtime-failure=false;allow-resource-service-retart=true}
[domain@localhost:9999 / #] run-batch
{code}
Then on a slave with two servers, this is logged:
{code}
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "composite" headers: {
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "caller-type" => "user",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "access-mechanism" => "NATIVE",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "domain-uuid" => "9adebc93-b318-4624-a26a-c08f53c6a503",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "execute-for-coordinator" => true,
[Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) "domain-controller-lock-id" => 38525532
[Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) }
[Host Controller] 17:10:11,146 INFO [stdout] (Host Controller Service Threads - 9) "composite" headers: null
[Host Controller] 17:10:11,147 INFO [stdout] (Host Controller Service Threads - 10) "composite" headers: null
[Server:server-one] 17:10:11,152 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "4ee59ca6-59dd-445f-99a5-190d00df34e0"}
[Server:server-two] 17:10:11,166 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "3da079cd-c0df-404d-9b1d-99b14a5ce7c2"}
{code}
The HC logs 3 requests; the rollout to itself and the calls it is proxying to the 2 servers. Then the servers report. The user-specified headers are not included.
Invoke the same op without the batch and this is logged:
{code}
[Host Controller] 17:15:51,856 INFO [stdout] (Host Controller Service Threads - 13) "add" headers: {
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "blocking-timeout" => "10",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "caller-type" => "user",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "execute-for-coordinator" => true,
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-controller-lock-id" => -351448963
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) }
[Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "add" headers: {
[Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "blocking-timeout" => "10",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "push-to-servers" => undefined
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) }
[Host Controller] 17:15:51,881 INFO [stdout] (Host Controller Service Threads - 15) "add" headers: {
[Host Controller] 17:15:51,882 INFO [stdout] (Host Controller Service Threads - 15) "blocking-timeout" => "10",
[Host Controller] 17:15:51,883 INFO [stdout] (Host Controller Service Threads - 15) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "push-to-servers" => undefined
[Host Controller] 17:15:51,885 INFO [stdout] (Host Controller Service Threads - 15) }
[Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "add" headers: {
[Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "blocking-timeout" => "10",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "rollback-on-runtime-failure" => "false",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "allow-resource-service-retart" => "true",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "access-mechanism" => "NATIVE",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "push-to-servers" => undefined
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) }
[Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "add" headers: {
[Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "blocking-timeout" => "10",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "rollback-on-runtime-failure" => "false",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "allow-resource-service-retart" => "true",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "access-mechanism" => "NATIVE",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "push-to-servers" => undefined
{code}
Expected headers are present.
Note the CLI 'batch' is far from the only time the 'composite' op is used. Among other places, the high level CLI 'deploy' command in a domain involves use of 'composite'.
> Operation headers not propagated to domain servers when 'composite' op is used
> ------------------------------------------------------------------------------
>
> Key: WFCORE-1214
> URL: https://issues.jboss.org/browse/WFCORE-1214
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.4.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 2.0.5.Final
>
>
> When the user adds request headers to an op, they are not propagated to the servers during domain rollout if the 'composite' op is involved.
> For example, if I add some stdout printing of what the headers are on the various processes and invoke this:
> {code}
> [domain@localhost:9990 /] deploy ~/tmp/helloworld.war --headers={blocking-timeout=5;rollback-on-runtime-failure=false} --all-server-groups
> {code}
> Then on a HC with two servers, this is logged:
> [Host Controller] 10:53:40,697 INFO [stdout] (management-handler-thread - 3) "composite" headers: {
> [Host Controller] 10:53:40,697 INFO [stdout] (management-handler-thread - 3) "blocking-timeout" => "5",
> [Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) "rollback-on-runtime-failure" => "false",
> [Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) "caller-type" => "user",
> [Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) "access-mechanism" => "NATIVE"
> [Host Controller] 10:53:40,698 INFO [stdout] (management-handler-thread - 3) }
> [Host Controller] 10:53:40,727 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /Users/bstansberry/dev/wildfly/wildfly-core/dist/target/wildfly-core-2.0.5.Final-SNAPSHOT/domain/data/content/6f/cd9eae343ed6d5aa9fffa83012d155b1ef911c/content
> [Server:server-one] 10:53:40,772 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: null
> [Server:server-two] 10:53:40,772 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: null
> The HC logs, then the servers report. The user-specified headers are not included.
> Invoke the same op without the batch and this is logged:
> {code}
> [Host Controller] 10:43:50,400 INFO [stdout] (management-handler-thread - 4) "composite" headers: {
> [Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "blocking-timeout" => "5",
> [Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "rollback-on-runtime-failure" => "false",
> [Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "caller-type" => "user",
> [Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) "access-mechanism" => "NATIVE"
> [Host Controller] 10:43:50,401 INFO [stdout] (management-handler-thread - 4) }
> [Host Controller] 10:43:50,425 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /Users/bstansberry/dev/wildfly/wildfly-core/dist/target/wildfly-core-2.0.5.Final-SNAPSHOT/domain/data/content/6f/cd9eae343ed6d5aa9fffa83012d155b1ef911c/content
> [Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: {
> [Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "blocking-timeout" => "5",
> [Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "rollback-on-runtime-failure" => "false",
> [Server:server-one] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "composite" headers: {
> [Server:server-two] 10:43:50,464 INFO [stdout] (ServerService Thread Pool -- 11) "access-mechanism" => "NATIVE",
> [Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "blocking-timeout" => "5",
> [Server:server-two] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "domain-uuid" => "216d2e99-dba5-4c89-8020-b0c16bd553c5"
> [Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "rollback-on-runtime-failure" => "false",
> [Server:server-two] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) }
> [Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "access-mechanism" => "NATIVE",
> [Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) "domain-uuid" => "216d2e99-dba5-4c89-8020-b0c16bd553c5"
> [Server:server-one] 10:43:50,465 INFO [stdout] (ServerService Thread Pool -- 11) }
> {code}
> Expected headers are present.
> Note the CLI 'deploy' is far from the only time the 'composite' op is used. Among other places, the high level CLI 'batch' command in a domain involves use of 'composite'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1214) Operation headers not propagated to domain servers when 'composite' op is used
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1214?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1214:
-------------------------------------
Description:
When the user adds request headers to an op, they are not propagated to the servers during domain rollout if the 'composite' op is involved.
For example, if I add some stdout printing of what the headers are on the various processes and invoke this:
{code}
[domain@localhost:9999 /] batch
[domain@localhost:9999 / #] /system-property=add(value=bar){blocking-timeout=10;rollback-on-runtime-failure=false;allow-resource-service-retart=true}
[domain@localhost:9999 / #] run-batch
{code}
Then on a slave with two servers, this is logged:
{code}
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "composite" headers: {
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "caller-type" => "user",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "access-mechanism" => "NATIVE",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "domain-uuid" => "9adebc93-b318-4624-a26a-c08f53c6a503",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "execute-for-coordinator" => true,
[Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) "domain-controller-lock-id" => 38525532
[Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) }
[Host Controller] 17:10:11,146 INFO [stdout] (Host Controller Service Threads - 9) "composite" headers: null
[Host Controller] 17:10:11,147 INFO [stdout] (Host Controller Service Threads - 10) "composite" headers: null
[Server:server-one] 17:10:11,152 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "4ee59ca6-59dd-445f-99a5-190d00df34e0"}
[Server:server-two] 17:10:11,166 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "3da079cd-c0df-404d-9b1d-99b14a5ce7c2"}
{code}
The HC logs 3 requests; the rollout to itself and the calls it is proxying to the 2 servers. Then the servers report. The user-specified headers are not included.
Invoke the same op without the batch and this is logged:
{code}
[Host Controller] 17:15:51,856 INFO [stdout] (Host Controller Service Threads - 13) "add" headers: {
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "blocking-timeout" => "10",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "caller-type" => "user",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "execute-for-coordinator" => true,
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-controller-lock-id" => -351448963
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) }
[Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "add" headers: {
[Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "blocking-timeout" => "10",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "push-to-servers" => undefined
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) }
[Host Controller] 17:15:51,881 INFO [stdout] (Host Controller Service Threads - 15) "add" headers: {
[Host Controller] 17:15:51,882 INFO [stdout] (Host Controller Service Threads - 15) "blocking-timeout" => "10",
[Host Controller] 17:15:51,883 INFO [stdout] (Host Controller Service Threads - 15) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "push-to-servers" => undefined
[Host Controller] 17:15:51,885 INFO [stdout] (Host Controller Service Threads - 15) }
[Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "add" headers: {
[Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "blocking-timeout" => "10",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "rollback-on-runtime-failure" => "false",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "allow-resource-service-retart" => "true",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "access-mechanism" => "NATIVE",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "push-to-servers" => undefined
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) }
[Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "add" headers: {
[Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "blocking-timeout" => "10",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "rollback-on-runtime-failure" => "false",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "allow-resource-service-retart" => "true",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "access-mechanism" => "NATIVE",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "push-to-servers" => undefined
{code}
Expected headers are present.
Note the CLI 'batch' is far from the only time the 'composite' op is used. Among other places, the high level CLI 'deploy' command in a domain involves use of 'composite'.
was:
When the user adds request headers to an op, that are not propagated to the servers during domain rollout if the 'composite' op is involved.
For example, if I add some stdout printing of what the headers are on the various processes and invoke this:
{code}
[domain@localhost:9999 /] batch
[domain@localhost:9999 / #] /system-property=add(value=bar){blocking-timeout=10;rollback-on-runtime-failure=false;allow-resource-service-retart=true}
[domain@localhost:9999 / #] run-batch
{code}
Then on a slave with two servers, this is logged:
{code}
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "composite" headers: {
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "caller-type" => "user",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "access-mechanism" => "NATIVE",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "domain-uuid" => "9adebc93-b318-4624-a26a-c08f53c6a503",
[Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "execute-for-coordinator" => true,
[Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) "domain-controller-lock-id" => 38525532
[Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) }
[Host Controller] 17:10:11,146 INFO [stdout] (Host Controller Service Threads - 9) "composite" headers: null
[Host Controller] 17:10:11,147 INFO [stdout] (Host Controller Service Threads - 10) "composite" headers: null
[Server:server-one] 17:10:11,152 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "4ee59ca6-59dd-445f-99a5-190d00df34e0"}
[Server:server-two] 17:10:11,166 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "3da079cd-c0df-404d-9b1d-99b14a5ce7c2"}
{code}
The HC logs 3 requests; the rollout to itself and the calls it is proxying to the 2 servers. Then the servers report. The user-specified headers are not included.
Invoke the same op without the batch and this is logged:
{code}
[Host Controller] 17:15:51,856 INFO [stdout] (Host Controller Service Threads - 13) "add" headers: {
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "blocking-timeout" => "10",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "caller-type" => "user",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "execute-for-coordinator" => true,
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-controller-lock-id" => -351448963
[Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) }
[Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "add" headers: {
[Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "blocking-timeout" => "10",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "push-to-servers" => undefined
[Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) }
[Host Controller] 17:15:51,881 INFO [stdout] (Host Controller Service Threads - 15) "add" headers: {
[Host Controller] 17:15:51,882 INFO [stdout] (Host Controller Service Threads - 15) "blocking-timeout" => "10",
[Host Controller] 17:15:51,883 INFO [stdout] (Host Controller Service Threads - 15) "rollback-on-runtime-failure" => "false",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "allow-resource-service-retart" => "true",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "access-mechanism" => "NATIVE",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "push-to-servers" => undefined
[Host Controller] 17:15:51,885 INFO [stdout] (Host Controller Service Threads - 15) }
[Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "add" headers: {
[Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "blocking-timeout" => "10",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "rollback-on-runtime-failure" => "false",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "allow-resource-service-retart" => "true",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "access-mechanism" => "NATIVE",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "push-to-servers" => undefined
[Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) }
[Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "add" headers: {
[Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "blocking-timeout" => "10",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "rollback-on-runtime-failure" => "false",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "allow-resource-service-retart" => "true",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "access-mechanism" => "NATIVE",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
[Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "push-to-servers" => undefined
{code}
Expected headers are present.
> Operation headers not propagated to domain servers when 'composite' op is used
> ------------------------------------------------------------------------------
>
> Key: WFCORE-1214
> URL: https://issues.jboss.org/browse/WFCORE-1214
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.4.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 2.0.5.Final
>
>
> When the user adds request headers to an op, they are not propagated to the servers during domain rollout if the 'composite' op is involved.
> For example, if I add some stdout printing of what the headers are on the various processes and invoke this:
> {code}
> [domain@localhost:9999 /] batch
> [domain@localhost:9999 / #] /system-property=add(value=bar){blocking-timeout=10;rollback-on-runtime-failure=false;allow-resource-service-retart=true}
> [domain@localhost:9999 / #] run-batch
> {code}
> Then on a slave with two servers, this is logged:
> {code}
> [Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "composite" headers: {
> [Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "caller-type" => "user",
> [Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "access-mechanism" => "NATIVE",
> [Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "domain-uuid" => "9adebc93-b318-4624-a26a-c08f53c6a503",
> [Host Controller] 17:10:11,104 INFO [stdout] (Host Controller Service Threads - 8) "execute-for-coordinator" => true,
> [Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) "domain-controller-lock-id" => 38525532
> [Host Controller] 17:10:11,105 INFO [stdout] (Host Controller Service Threads - 8) }
> [Host Controller] 17:10:11,146 INFO [stdout] (Host Controller Service Threads - 9) "composite" headers: null
> [Host Controller] 17:10:11,147 INFO [stdout] (Host Controller Service Threads - 10) "composite" headers: null
> [Server:server-one] 17:10:11,152 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "4ee59ca6-59dd-445f-99a5-190d00df34e0"}
> [Server:server-two] 17:10:11,166 INFO [stdout] (ServerService Thread Pool -- 68) "composite" headers: {"domain-uuid" => "3da079cd-c0df-404d-9b1d-99b14a5ce7c2"}
> {code}
> The HC logs 3 requests; the rollout to itself and the calls it is proxying to the 2 servers. Then the servers report. The user-specified headers are not included.
> Invoke the same op without the batch and this is logged:
> {code}
> [Host Controller] 17:15:51,856 INFO [stdout] (Host Controller Service Threads - 13) "add" headers: {
> [Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "blocking-timeout" => "10",
> [Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "rollback-on-runtime-failure" => "false",
> [Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "allow-resource-service-retart" => "true",
> [Host Controller] 17:15:51,857 INFO [stdout] (Host Controller Service Threads - 13) "caller-type" => "user",
> [Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "access-mechanism" => "NATIVE",
> [Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
> [Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "execute-for-coordinator" => true,
> [Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) "domain-controller-lock-id" => -351448963
> [Host Controller] 17:15:51,858 INFO [stdout] (Host Controller Service Threads - 13) }
> [Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "add" headers: {
> [Host Controller] 17:15:51,879 INFO [stdout] (Host Controller Service Threads - 14) "blocking-timeout" => "10",
> [Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "rollback-on-runtime-failure" => "false",
> [Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "allow-resource-service-retart" => "true",
> [Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "access-mechanism" => "NATIVE",
> [Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
> [Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) "push-to-servers" => undefined
> [Host Controller] 17:15:51,880 INFO [stdout] (Host Controller Service Threads - 14) }
> [Host Controller] 17:15:51,881 INFO [stdout] (Host Controller Service Threads - 15) "add" headers: {
> [Host Controller] 17:15:51,882 INFO [stdout] (Host Controller Service Threads - 15) "blocking-timeout" => "10",
> [Host Controller] 17:15:51,883 INFO [stdout] (Host Controller Service Threads - 15) "rollback-on-runtime-failure" => "false",
> [Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "allow-resource-service-retart" => "true",
> [Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "access-mechanism" => "NATIVE",
> [Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
> [Host Controller] 17:15:51,884 INFO [stdout] (Host Controller Service Threads - 15) "push-to-servers" => undefined
> [Host Controller] 17:15:51,885 INFO [stdout] (Host Controller Service Threads - 15) }
> [Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "add" headers: {
> [Server:server-one] 17:15:51,889 INFO [stdout] (ServerService Thread Pool -- 71) "blocking-timeout" => "10",
> [Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "rollback-on-runtime-failure" => "false",
> [Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "allow-resource-service-retart" => "true",
> [Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "access-mechanism" => "NATIVE",
> [Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
> [Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) "push-to-servers" => undefined
> [Server:server-one] 17:15:51,890 INFO [stdout] (ServerService Thread Pool -- 71) }
> [Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "add" headers: {
> [Server:server-two] 17:15:51,891 INFO [stdout] (ServerService Thread Pool -- 70) "blocking-timeout" => "10",
> [Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "rollback-on-runtime-failure" => "false",
> [Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "allow-resource-service-retart" => "true",
> [Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "access-mechanism" => "NATIVE",
> [Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "domain-uuid" => "a4fe2ef5-31bb-4297-b1fb-19bb91684452",
> [Server:server-two] 17:15:51,892 INFO [stdout] (ServerService Thread Pool -- 70) "push-to-servers" => undefined
> {code}
> Expected headers are present.
> Note the CLI 'batch' is far from the only time the 'composite' op is used. Among other places, the high level CLI 'deploy' command in a domain involves use of 'composite'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1033) ManagedDatagramSocketBinding and ManagedMulticastSocketBinding throw NPE if created with bind address
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1033?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-1033:
-------------------------------------------------
Romain Pelisse <rpelisse(a)redhat.com> changed the Status of [bug 1268185|https://bugzilla.redhat.com/show_bug.cgi?id=1268185] from ASSIGNED to VERIFIED
> ManagedDatagramSocketBinding and ManagedMulticastSocketBinding throw NPE if created with bind address
> -----------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1033
> URL: https://issues.jboss.org/browse/WFCORE-1033
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 2.0.0.CR6
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 2.0.0.CR7
>
>
> {noformat}
> &#27;[0m&#27;[31m14:51:47,114 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.jgroups.channel.ee.connector: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee.connector: java.lang.NullPointerException
> at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:96)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.network.ManagedMulticastSocketBinding.bind(ManagedMulticastSocketBinding.java:78)
> at java.net.MulticastSocket.<init>(MulticastSocket.java:172)
> at org.jboss.as.network.ManagedMulticastSocketBinding.<init>(ManagedMulticastSocketBinding.java:54)
> at org.jboss.as.network.ManagedMulticastSocketBinding.create(ManagedMulticastSocketBinding.java:40)
> at org.jboss.as.network.SocketBindingManagerImpl.createMulticastSocket(SocketBindingManagerImpl.java:82)
> at org.jboss.as.clustering.jgroups.ManagedSocketFactoryNew.createMulticastSocket(ManagedSocketFactoryNew.java:127)
> at org.jgroups.util.Util.createMulticastSocket(Util.java:3089)
> at org.jgroups.protocols.MPING.start(MPING.java:190)
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:965)
> at org.jgroups.JChannel.startStack(JChannel.java:890)
> at org.jgroups.JChannel._preConnect(JChannel.java:553)
> at org.jgroups.JChannel.connect(JChannel.java:288)
> at org.jgroups.JChannel.connect(JChannel.java:279)
> at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:94)
> {noformat}
> This is because the MulticastSocket and DatagramSocket constructors call bind(...), but the ManagedBindingRegistry is not yet set.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-5449:
-----------------------------------------------
Romain Pelisse <rpelisse(a)redhat.com> changed the Status of [bug 1268185|https://bugzilla.redhat.com/show_bug.cgi?id=1268185] from ASSIGNED to VERIFIED
> Custom socket factory for JGroups subsystem not set correctly
> -------------------------------------------------------------
>
> Key: WFLY-5449
> URL: https://issues.jboss.org/browse/WFLY-5449
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR2
> Reporter: Dennis Reed
> Assignee: Paul Ferraro
> Priority: Blocker
> Fix For: 10.0.0.CR4
>
>
> Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport.
> This is not the correct API to use, and it gets overwritten when the JGroups channel starts.
> A custom socket factory should be set on the JChannel.
> The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months