[jboss-jira] [JBoss JIRA] (WFLY-3274) connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final

Rituraj Sinha (JIRA) issues at jboss.org
Mon Apr 21 02:32:33 EDT 2014


Rituraj Sinha created WFLY-3274:
-----------------------------------

             Summary: connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final 
                 Key: WFLY-3274
                 URL: https://issues.jboss.org/browse/WFLY-3274
             Project: WildFly
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JMX, Web (Undertow)
    Affects Versions: 8.0.0.Final
            Reporter: Rituraj Sinha
            Assignee: Kabir Khan
            Priority: Critical


while using jboss 7.2.0 we were able to fetch above values from the cli command as

[domain at test.com:9999 subsystem=web] ls

configuration                        valve                                default-virtual-server=default-host  native=false

connector                            virtual-server                       instance-id=${jboss.node.name}

[domain at test.com:9999 connector] ls

ajp   http

[domain at test.com:9999 connector] cd http
[domain at test.com:9999 connector] pwd
/profile=ha/subsystem=web/connector=http

[domain at test.com:9999 connector=http] ls

configuration                                    max-connections=undefined                           proxy-port=undefined

ssl                                                    max-post-size=2097152                                    redirect-port=443

bytesReceived=                                max-save-post-size=4096                                      requestCount=

bytesSent=                                          maxTime=                                                         scheme=http

enable-lookups=false                             name=http                                                            secure=false

enabled=true                                     processingTime=                                             socket-binding=http

errorCount=                                      protocol=HTTP/1.1                                     virtual-server=undefined

executor=undefined                           proxy-name=undefined

 

Now we have moved to wildfly8 and trying to look for  the same values in underetow( as there is no "web" subsystem in wildfly8)

as below

[domain at test2.com:9990 subsystem=undertow] ls

buffer-cache                       server                             default-servlet-container=default  statistics-enabled=false         (Here there is no connector attribute available as this was in jboss 7.2.0 )

configuration                      servlet-container                  default-virtual-host=default-host

error-page                         default-server=default-server      instance-id=${jboss.node.name}

 

but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as

[domain at test2.com:9990 server=default-server] ls

ajp-listener               host                       http-listener              https-listener             default-host=default-host  servlet-container=default

after getting into http-listener we get the below

[domain at test2.com:9990 http-listener=default] ls

allow-encoded-slash=false        certificate-forwarding=false     max-cookies=200                  max-post-size=10485760           socket-binding=http

always-set-keep-alive=true       decode-url=true                  max-header-size=51200            proxy-address-forwarding=false   url-charset=UTF-8

buffer-pipelined-data=true       enabled=true                     max-headers=200                  record-request-start-time=false  worker=default

buffer-pool=default              max-buffered-request-size=16384  max-parameters=1000              redirect-socket=https

 

Can someone please look into it ..?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list