[JBoss JIRA] (WFLY-5627) Unable to view the infinispan statistics from CLI
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5627?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-5627:
------------------------------------
Until https://issues.jboss.org/browse/WFLY-5685 is complete, you can only see these metrics via JMX.
> Unable to view the infinispan statistics from CLI
> -------------------------------------------------
>
> Key: WFLY-5627
> URL: https://issues.jboss.org/browse/WFLY-5627
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Chao Wang
> Assignee: Paul Ferraro
>
> When I investigated https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its scenario with WildFly as:
> {noformat}
> Steps to Reproduce:
> ===================
> 1) Build latest Wildfly master and consider `standalone-ha.xml` file.
> 2) Enable the infinispan statistics in the standalone-ha.xml file.
> Configuration looks as below:
> -----
> <subsystem xmlns="urn:jboss:domain:infinispan:4.0">
> <cache-container name="server" aliases="singleton cluster" module="org.wildfly.clustering.server" default-cache="default">
> <transport lock-timeout="60000"/>
> <replicated-cache name="default" mode="SYNC">
> <transaction mode="BATCH"/>
> </replicated-cache>
> </cache-container>
> <cache-container name="web" module="org.wildfly.clustering.web.infinispan" default-cache="dist" statistics-enabled="true">
> <transport lock-timeout="60000"/>
> <distributed-cache name="dist" statistics-enabled="true" mode="ASYNC" l1-lifespan="0" owners="2">
> <locking isolation="REPEATABLE_READ"/>
> <transaction mode="BATCH"/>
> <file-store/>
> </distributed-cache>
> </cache-container>
> -----
> 3) Start the server with `standalone-ha.xml` file.
> 4) Deploy the cluster web application and hit the application.
> 5) and check the infinispan statistics by using the below cli command:
> -----
> /subsystem=infinispan/cache-container=web/distributed-cache=dist:read-resource(include-runtime=true)
> -----
> 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change.
> Actual results:
> ===============
> - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed.
> Expected results:
> =================
> - There should be a change in the runtime parameters values.
> Additional info:
> =================
> - I can see the expected result from the jconsole statistics.
> jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics.
> {noformat}
> It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes such difference. Once I revert this commit, I can see dynamic statistics change in CLI operation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-5627) Unable to view the infinispan statistics from CLI
by PEANO LUCA (JIRA)
[ https://issues.jboss.org/browse/WFLY-5627?page=com.atlassian.jira.plugin.... ]
PEANO LUCA commented on WFLY-5627:
----------------------------------
sorry but how i can get replicated web cache metrics via jboss cli?
> Unable to view the infinispan statistics from CLI
> -------------------------------------------------
>
> Key: WFLY-5627
> URL: https://issues.jboss.org/browse/WFLY-5627
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Chao Wang
> Assignee: Paul Ferraro
>
> When I investigated https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its scenario with WildFly as:
> {noformat}
> Steps to Reproduce:
> ===================
> 1) Build latest Wildfly master and consider `standalone-ha.xml` file.
> 2) Enable the infinispan statistics in the standalone-ha.xml file.
> Configuration looks as below:
> -----
> <subsystem xmlns="urn:jboss:domain:infinispan:4.0">
> <cache-container name="server" aliases="singleton cluster" module="org.wildfly.clustering.server" default-cache="default">
> <transport lock-timeout="60000"/>
> <replicated-cache name="default" mode="SYNC">
> <transaction mode="BATCH"/>
> </replicated-cache>
> </cache-container>
> <cache-container name="web" module="org.wildfly.clustering.web.infinispan" default-cache="dist" statistics-enabled="true">
> <transport lock-timeout="60000"/>
> <distributed-cache name="dist" statistics-enabled="true" mode="ASYNC" l1-lifespan="0" owners="2">
> <locking isolation="REPEATABLE_READ"/>
> <transaction mode="BATCH"/>
> <file-store/>
> </distributed-cache>
> </cache-container>
> -----
> 3) Start the server with `standalone-ha.xml` file.
> 4) Deploy the cluster web application and hit the application.
> 5) and check the infinispan statistics by using the below cli command:
> -----
> /subsystem=infinispan/cache-container=web/distributed-cache=dist:read-resource(include-runtime=true)
> -----
> 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change.
> Actual results:
> ===============
> - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed.
> Expected results:
> =================
> - There should be a change in the runtime parameters values.
> Additional info:
> =================
> - I can see the expected result from the jconsole statistics.
> jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics.
> {noformat}
> It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes such difference. Once I revert this commit, I can see dynamic statistics change in CLI operation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFLY-5627) Unable to view the infinispan statistics from CLI
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5627?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-5627:
------------------------------------
[~lpeano] The routing information is stored in a cache instance per server (i.e. undertow "server"), named using the name of that server (e.g. <server name="default-server">...</server>. I'm not sure why statistics from this cache would be of any interest.
> Unable to view the infinispan statistics from CLI
> -------------------------------------------------
>
> Key: WFLY-5627
> URL: https://issues.jboss.org/browse/WFLY-5627
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Chao Wang
> Assignee: Paul Ferraro
>
> When I investigated https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its scenario with WildFly as:
> {noformat}
> Steps to Reproduce:
> ===================
> 1) Build latest Wildfly master and consider `standalone-ha.xml` file.
> 2) Enable the infinispan statistics in the standalone-ha.xml file.
> Configuration looks as below:
> -----
> <subsystem xmlns="urn:jboss:domain:infinispan:4.0">
> <cache-container name="server" aliases="singleton cluster" module="org.wildfly.clustering.server" default-cache="default">
> <transport lock-timeout="60000"/>
> <replicated-cache name="default" mode="SYNC">
> <transaction mode="BATCH"/>
> </replicated-cache>
> </cache-container>
> <cache-container name="web" module="org.wildfly.clustering.web.infinispan" default-cache="dist" statistics-enabled="true">
> <transport lock-timeout="60000"/>
> <distributed-cache name="dist" statistics-enabled="true" mode="ASYNC" l1-lifespan="0" owners="2">
> <locking isolation="REPEATABLE_READ"/>
> <transaction mode="BATCH"/>
> <file-store/>
> </distributed-cache>
> </cache-container>
> -----
> 3) Start the server with `standalone-ha.xml` file.
> 4) Deploy the cluster web application and hit the application.
> 5) and check the infinispan statistics by using the below cli command:
> -----
> /subsystem=infinispan/cache-container=web/distributed-cache=dist:read-resource(include-runtime=true)
> -----
> 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change.
> Actual results:
> ===============
> - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed.
> Expected results:
> =================
> - There should be a change in the runtime parameters values.
> Additional info:
> =================
> - I can see the expected result from the jconsole statistics.
> jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics.
> {noformat}
> It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes such difference. Once I revert this commit, I can see dynamic statistics change in CLI operation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (ELY-680) No log messages comming from Elytron - kerberos
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-680?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina commented on ELY-680:
--------------------------------
Improved in second PR.
> No log messages comming from Elytron - kerberos
> -----------------------------------------------
>
> Key: ELY-680
> URL: https://issues.jboss.org/browse/ELY-680
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
>
> Elytron is missing log messages related to kerberos authentication. These log messages should be added. See JBEAP-6041 for more details.
> I consider to be useful to have TRACE log messages at least in:
> - SpnegoAuthenticationMechanism
> - GSSCredentialSecurityFactory
> If there are more classes involved in kerberos authnetication include them as well.
> Kerberos issues are very specific. So it is very important to have as much trace information as possible. Therefore raising priority to Critical.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-2160:
-------------------------------------------------
Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1410924|https://bugzilla.redhat.com/show_bug.cgi?id=1410924] from POST to MODIFIED
> Incorrect JBOSS_HOME warning in vault.sh
> ----------------------------------------
>
> Key: WFCORE-2160
> URL: https://issues.jboss.org/browse/WFCORE-2160
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 3.0.0.Alpha16
> Reporter: Dennis Reed
> Assignee: Romain Pelisse
> Priority: Minor
> Fix For: 3.0.0.Alpha23
>
>
> vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly.
> SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
> if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
> The check will always fail because of the incorrect "/..", which should be removed.
> The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months