[JBoss JIRA] (WFLY-4420) Need Hot fix for WildFly 8.2 : Expose connector metric values such as requestCount , maxTime, bytesReceived, etc
by bk lau (JIRA)
[ https://issues.jboss.org/browse/WFLY-4420?page=com.atlassian.jira.plugin.... ]
bk lau updated WFLY-4420:
-------------------------
Affects Version/s: 8.2.0.Final
8.1.0.Final
Priority: Blocker (was: Major)
> Need Hot fix for WildFly 8.2 : Expose connector metric values such as requestCount , maxTime, bytesReceived, etc
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4420
> URL: https://issues.jboss.org/browse/WFLY-4420
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final, 8.1.0.Final, 8.2.0.Final
> Reporter: bk lau
> Assignee: Stuart Douglas
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
>
> while using jboss 7.2.0 we were able to fetch above values from the cli command as
> {noformat}
> [domain@test.com:9999 subsystem=web] ls
> configuration valve default-virtual-server=default-host native=false
> connector virtual-server instance-id=${jboss.node.name}
> [domain@test.com:9999 connector] ls
> ajp http
> [domain@test.com:9999 connector] cd http
> [domain@test.com:9999 connector] pwd
> /profile=ha/subsystem=web/connector=http
> [domain@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
> {noformat}
>
> 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
> {noformat}
> [domain@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}
> {noformat}
>
> but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
> {noformat}
> [domain@test2.com:9990 server=default-server] ls
> ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
> {noformat}
> after getting into http-listener we get the below
> {noformat}
> [domain@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
> {noformat}
>
> Can someone please look into it ..?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4420) Need Hot fix for WildFly 8.2 : Expose connector metric values such as requestCount , maxTime, bytesReceived, etc
by bk lau (JIRA)
[ https://issues.jboss.org/browse/WFLY-4420?page=com.atlassian.jira.plugin.... ]
bk lau commented on WFLY-4420:
------------------------------
We have a production plugin targeting AS 7.1 and now migrating to WildFly 8.2, it no longer works due to absence of "/subsystem=web/connector=http" node
Can we get a hotfix for WildFly 8.2 instead of waiting for WildFly 9.0.0 to be released?. It could take months!
> Need Hot fix for WildFly 8.2 : Expose connector metric values such as requestCount , maxTime, bytesReceived, etc
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4420
> URL: https://issues.jboss.org/browse/WFLY-4420
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: bk lau
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Beta1
>
>
> while using jboss 7.2.0 we were able to fetch above values from the cli command as
> {noformat}
> [domain@test.com:9999 subsystem=web] ls
> configuration valve default-virtual-server=default-host native=false
> connector virtual-server instance-id=${jboss.node.name}
> [domain@test.com:9999 connector] ls
> ajp http
> [domain@test.com:9999 connector] cd http
> [domain@test.com:9999 connector] pwd
> /profile=ha/subsystem=web/connector=http
> [domain@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
> {noformat}
>
> 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
> {noformat}
> [domain@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}
> {noformat}
>
> but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
> {noformat}
> [domain@test2.com:9990 server=default-server] ls
> ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
> {noformat}
> after getting into http-listener we get the below
> {noformat}
> [domain@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
> {noformat}
>
> Can someone please look into it ..?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-4420) Need Hot fix for WildFly 8.2 : Expose connector metric values such as requestCount , maxTime, bytesReceived, etc
by bk lau (JIRA)
bk lau created WFLY-4420:
----------------------------
Summary: Need Hot fix for WildFly 8.2 : Expose connector metric values such as requestCount , maxTime, bytesReceived, etc
Key: WFLY-4420
URL: https://issues.jboss.org/browse/WFLY-4420
Project: WildFly
Issue Type: Feature Request
Components: Web (Undertow)
Affects Versions: 8.0.0.Final
Reporter: bk lau
Assignee: Stuart Douglas
Fix For: 9.0.0.Beta1
while using jboss 7.2.0 we were able to fetch above values from the cli command as
{noformat}
[domain@test.com:9999 subsystem=web] ls
configuration valve default-virtual-server=default-host native=false
connector virtual-server instance-id=${jboss.node.name}
[domain@test.com:9999 connector] ls
ajp http
[domain@test.com:9999 connector] cd http
[domain@test.com:9999 connector] pwd
/profile=ha/subsystem=web/connector=http
[domain@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
{noformat}
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
{noformat}
[domain@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}
{noformat}
but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
{noformat}
[domain@test2.com:9990 server=default-server] ls
ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
{noformat}
after getting into http-listener we get the below
{noformat}
[domain@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
{noformat}
Can someone please look into it ..?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3420) UndertowJSRWebSocketDeploymentProcessor uses hard coded IO module dependencies
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3420?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-3420.
-------------------------------
Assignee: Stuart Douglas (was: Tomaz Cerar)
Fix Version/s: 9.0.0.CR1
8.2.0.Final
Resolution: Done
This was fixed back in October.
> UndertowJSRWebSocketDeploymentProcessor uses hard coded IO module dependencies
> ------------------------------------------------------------------------------
>
> Key: WFLY-3420
> URL: https://issues.jboss.org/browse/WFLY-3420
> Project: WildFly
> Issue Type: Enhancement
> Components: IO, Web (Undertow)
> Environment: any
> Reporter: Matthias Berndt
> Assignee: Stuart Douglas
> Priority: Minor
> Fix For: 9.0.0.CR1, 8.2.0.Final
>
>
> UndertowJSRWebSocketDeploymentProcessor uses hard coded dependencies to a buffer pool und worker pool named "default" of the IO module.
> My suggestion is to introduce two additional attributes "worker" and "buffer-pool" to the undertow module get rid of the hard coded pools. The default values will garanty a compatibility.
> If you agree to this approach i'll provide a patch adding und using these attributes.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (LOGMGR-120) Thread local log level overriding
by Thiago Veronezi (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-120?page=com.atlassian.jira.plugin... ]
Thiago Veronezi commented on LOGMGR-120:
----------------------------------------
Hi David,
Thanks for the quick feedback.
Regarding performance:
* I added a system property for that so the user can opt-in.
* When the system is enabled, the callback interface will be used to dynamically determine whether to force the log or not. It means that a custom implementation of this interface should take care of it; Example: an implementation could use memoization.
{quote}
... the core of the logging system itself is the place that this modification should be happening, ...
{quote}
Hmmmm, I didn't quite get that. Where is the core of the logging system? :)
> Thread local log level overriding
> ---------------------------------
>
> Key: LOGMGR-120
> URL: https://issues.jboss.org/browse/LOGMGR-120
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Affects Versions: 1.5.2.Final
> Reporter: Matthew Robson
> Assignee: James Perkins
> Attachments: force_logging.patch
>
>
> Having the ability to force logs down to a filter no matter what the log level is set to.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JGRP-1920) FC: Flag NO_FC is not applied on RPC calls/responses
by Karim AMMOUS (JIRA)
Karim AMMOUS created JGRP-1920:
----------------------------------
Summary: FC: Flag NO_FC is not applied on RPC calls/responses
Key: JGRP-1920
URL: https://issues.jboss.org/browse/JGRP-1920
Project: JGroups
Issue Type: Bug
Reporter: Karim AMMOUS
Assignee: Bela Ban
When we set Flag.NO_FC on an RPC call through "RequestOptions", we expect that both request and response will be not rate limited.
Currently, both request and response could be slow down by flow control protocols.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JGRP-1910) MERGE3: Do not lose any members from view during a series of merges
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1910?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1910:
--------------------------------
You lost me here. Can you give a concrete example ? The current algorithm tries to use something akin to a Lamport time as view-id and discards views with view-id <= to the current view-id.
> MERGE3: Do not lose any members from view during a series of merges
> -------------------------------------------------------------------
>
> Key: JGRP-1910
> URL: https://issues.jboss.org/browse/JGRP-1910
> Project: JGroups
> Issue Type: Bug
> Reporter: Radim Vansa
> Assignee: Bela Ban
> Fix For: 3.6.3
>
> Attachments: SplitMergeFailFastTest.java, SplitMergeTest.java
>
>
> When connection between nodes is re-established, MERGE3 should merge the cluster together. This often does not involve a single MergeView but a series of such events. The problematic property of this protocol is that some of those views can lack certain members, though these are reachable.
> This causes problem in Infinispan since the cache cannot be fully rebalanced before another merge arrives, and all owners of certain segment can be gradually removed (and added again) to the view, while this is not detected as partition but crashed nodes -> losing all owners means data loss.
> Removing members from view should be the role of FDx protocols, not MERGEx.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (LOGMGR-120) Thread local log level overriding
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-120?page=com.atlassian.jira.plugin... ]
David Lloyd commented on LOGMGR-120:
------------------------------------
Thanks for the contribution. There are several problems with the approach you take though, particularly around performance. In addition, you are modifying the structure of the log record which is not advisable at present. Finally as I described above, the core of the logging system itself is the place that this modification should be happening, in the way that I describe, for the reasons I give above.
> Thread local log level overriding
> ---------------------------------
>
> Key: LOGMGR-120
> URL: https://issues.jboss.org/browse/LOGMGR-120
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Affects Versions: 1.5.2.Final
> Reporter: Matthew Robson
> Assignee: James Perkins
> Attachments: force_logging.patch
>
>
> Having the ability to force logs down to a filter no matter what the log level is set to.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months