[jboss-jira] [JBoss JIRA] (AS7-4966) CLONE - JBoss EAP6 does not allow to associate connector to a specific virtual server

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar moved JBPAPP-9319 to AS7-4966:
---------------------------------------------

              Project: Application Server 7  (was: JBoss Enterprise Application Platform)
                  Key: AS7-4966  (was: JBPAPP-9319)
             Workflow: GIT Pull Request workflow   (was: jira)
    Affects Version/s: 7.1.2.Final (EAP)
                           (was: EAP 6.0.0 ER 3_Beta1)
                           (was: EAP 6.0.0 CR1)
          Component/s: Web
                           (was: Web)
             Security:     (was: JBoss Internal)
        Fix Version/s: 7.1.3.Final (EAP)
                       7.2.0.Alpha1
                           (was: TBD EAP 6)
       Docs QE Status:   (was: NEW)

    
> CLONE - JBoss EAP6 does not allow to associate connector to a specific virtual server
> -------------------------------------------------------------------------------------
>
>                 Key: AS7-4966
>                 URL: https://issues.jboss.org/browse/AS7-4966
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Web
>    Affects Versions: 7.1.2.Final (EAP)
>         Environment: JBoss Enterprise Application Platform (EAP) 6 
>            Reporter: Jay Kumar SenSharma
>            Assignee: Tomaz Cerar
>             Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> JBoss EAP 6 does not allow to associate connector to a specific virtual server.  Ideally it should because we can see virtual-server as an attribute of the connector tag.
> Example:
> ========
> /subsystem=web/connector=http/:read-resource(recursive=true,proxies=false,include-runtime=false,include-defaults=true)
> {
>     "outcome" => "success",
>     "result" => {
>         "enable-lookups" => false,
>         "enabled" => true,
>         "executor" => undefined,
>         "max-connections" => undefined,
>         "max-post-size" => 2097152,
>         "max-save-post-size" => 4096,
>         "name" => "http",
>         "protocol" => "HTTP/1.1",
>         "proxy-name" => undefined,
>         "proxy-port" => undefined,
>         "redirect-port" => 8433,
>         "scheme" => "http",
>         "secure" => false,
>         "socket-binding" => "http",
>         "ssl" => undefined,
>         "virtual-server" => undefined             
>     }
> }
> Steps to reproduce the issue:
> Creating Socket Binding: (Success)
> +++++++++++++++++++++++++++
> /socket-binding-group=standard-sockets/socket-binding=httpTest/:add(port=7070,fixed-port=false)
> Creating Virtual Server: (Success)
> +++++++++++++++++++++++++++
> /subsystem=web/virtual-server=testVirtualServer/:add(enable-welcome-root=false,default-web-module=SessionTest,alias=["test.com"],name=testVirtualServer)
> Adding a Connector with the Virtual Server Name: (Fails)
> +++++++++++++++++++++++++++ 
> /subsystem=web/connector=testConnector/:add(socket-binding=httpTest,scheme=http,protocol=HTTP/1.1,secure=false,virtual-server=testVirtualServer,name=testConnector,enabled=false,enable-lookups=false)
> We get the following Exception:
> /subsystem=web/connector=testConnector/:add(socket-binding=httpTest,scheme=http,protocol=HTTP/1.1,secure=false,virtual-server=testVirtualServer,name=testConnector,enabled=false,enable-lookups=false)
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014677: Failed to persist configuration change: JBAS014675: Failed to marshal configuration",
>     "rolled-back" => true
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira