[jboss-jira] [JBoss JIRA] (WFCORE-1214) Operation headers not propagated to domain servers when 'composite' op is used

Brian Stansberry (JIRA) issues at jboss.org
Fri Dec 11 18:18:00 EST 2015


Brian Stansberry created WFCORE-1214:
----------------------------------------

             Summary: 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, 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 at localhost:9999 /] batch
[domain at localhost:9999 / #] /system-property=add(value=bar){blocking-timeout=10;rollback-on-runtime-failure=false;allow-resource-service-retart=true}
[domain at 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list