Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5280

Connector attribute max-save-post-size is neither migrated nor migration writing is shown

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 10.0.0.CR1
    • 10.0.0.Beta2
    • Web (Undertow)
    • None
    • Hide

      Try calling :migrate operation on Web subsystem with connector defined like this:

      <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-connections="100" max-post-size="2048000" enable-lookups="true" 
                          max-save-post-size="4092" />
      

      And see that there is no migration warning even though the attribute wasn't migrated (see created http listener in undertow subsystem:

      <http-listener name="http" max-connections="100" max-post-size="2048000" resolve-peer-address="true" socket-binding="http"/>
      
      Show
      Try calling :migrate operation on Web subsystem with connector defined like this: <connector name= "http" protocol= "HTTP/1.1" scheme= "http" socket-binding= "http" max-connections= "100" max-post-size= "2048000" enable-lookups= "true" max-save-post-size= "4092" /> And see that there is no migration warning even though the attribute wasn't migrated (see created http listener in undertow subsystem: <http-listener name= "http" max-connections= "100" max-post-size= "2048000" resolve-peer-address= "true" socket-binding= "http" />

    Description

      When migrating http connector, which has defined attribute max-save-post-size no warning that it is not possible to migrate the max-save-post-size is printed.

      Attachments

        Issue Links

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              rhatlapa@redhat.com Radim Hatlapatka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: