[JBoss JIRA] (WFLY-11384) StatefulFailoverTestCase fails intermittently
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11384?page=com.atlassian.jira.plugin... ]
Ondrej Kotek updated WFLY-11384:
--------------------------------
Description:
The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example:
{noformat}
[ERROR] Failures:
[ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3>
{noformat}
or
{noformat}
[ERROR] Failures:
[ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500>
{noformat}
connectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-822829635945...
noFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-574944609062...
jmsConnectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=3564603678560...
was:
The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example:
{noformat}
[ERROR] Failures:
[ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3>
{noformat}
or
{noformat}
[ERROR] Failures:
[ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500>
[ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500>
{noformat}
Estimated failure rate is 50 %.
> StatefulFailoverTestCase fails intermittently
> ---------------------------------------------
>
> Key: WFLY-11384
> URL: https://issues.jboss.org/browse/WFLY-11384
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 15.0.0.Beta1
> Environment: Any
> Reporter: Ondrej Kotek
> Assignee: Radoslav Husar
> Priority: Major
>
> The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example:
> {noformat}
> [ERROR] Failures:
> [ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500>
> [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500>
> [ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3>
> {noformat}
> or
> {noformat}
> [ERROR] Failures:
> [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500>
> [ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500>
> [ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500>
> {noformat}
> connectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-822829635945...
> noFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-574944609062...
> jmsConnectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=3564603678560...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (SWSQE-526) UI Tests - Make version compatible to run for TP
by Hayk Hovsepyan (Jira)
Hayk Hovsepyan created SWSQE-526:
------------------------------------
Summary: UI Tests - Make version compatible to run for TP
Key: SWSQE-526
URL: https://issues.jboss.org/browse/SWSQE-526
Project: Kiali QE
Issue Type: QE Task
Reporter: Hayk Hovsepyan
Assignee: Michael Foley
Currently when Kiali is released with older version than latest master, UI tests is not possible to run:
1. UI tests are not tagged.
2. Kiali REST Client is always latest on jenkins slaves.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
by Srinivas ev (Jira)
[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ]
Srinivas ev updated WFLY-11374:
-------------------------------
Description:
I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
master in standalone-full-ha.xml - refer master.xml
slave in standalone-full-ha.xml - refer slave.xml
In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
Test scenario -
1. Bring master up.
2. Bring slave up.
3. slave will announce the backup. (AMQ221031: backup announced).
4. Make master down.
5. Replication is success.
6. Slave is acting as master/live.
7. Make master up.
Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
This backup announcement works fine in windows and failover also works as expected.
Please let me know if anything specific required along with this details.
Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
Few logs I found -
was:
I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
master in standalone-full-ha.xml - refer master.xml
slave in standalone-full-ha.xml - refer slave.xml
In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
Test scenario -
1. Bring master up.
2. Bring slave up.
3. slave will announce the backup. (AMQ221031: backup announced).
4. Make master down.
5. Replication is success.
6. Slave is acting as master/live.
7. Make master up.
Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
This backup announcement works fine in windows and failover also works as expected.
Please let me know if anything specific required along with this details.
Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
> Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted
> ------------------------------------------------------------------------------
>
> Key: WFLY-11374
> URL: https://issues.jboss.org/browse/WFLY-11374
> Project: WildFly
> Issue Type: Bug
> Reporter: Srinivas ev
> Assignee: Jason Greene
> Priority: Blocker
> Attachments: master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, slave-server-linux.log, slave-server-windows.log, slave.xml
>
>
> I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work.
> This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine.
> master in standalone-full-ha.xml - refer master.xml
> slave in standalone-full-ha.xml - refer slave.xml
> In the startup script, I am passing all the values for placeholders of my server host ip's accordingly.
> Test scenario -
> 1. Bring master up.
> 2. Bring slave up.
> 3. slave will announce the backup. (AMQ221031: backup announced).
> 4. Make master down.
> 5. Replication is success.
> 6. Slave is acting as master/live.
> 7. Make master up.
> Issue - master is unable to announce the backup and starts normally as a standalone wildfly.
> This backup announcement works fine in windows and failover also works as expected.
> Please let me know if anything specific required along with this details.
> Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar
> in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main
> Few logs I found -
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3339?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-3339:
--------------------------------------
[~elmiko], are you planning to add issues to this epic? If not, can I kindly suggest you to change the type of the issue to something else than an epic? The epics themselves cannot be displayed in the board, only the "issues in epic" can.
> refactor the PMML regression model to use an external library for regressions
> -----------------------------------------------------------------------------
>
> Key: DROOLS-3339
> URL: https://issues.jboss.org/browse/DROOLS-3339
> Project: Drools
> Issue Type: Epic
> Components: PMML
> Affects Versions: 7.14.0.Final
> Reporter: michael mccune
> Assignee: michael mccune
> Priority: Critical
>
> Replace the current DRL generation for regression calculation by a specialized regression library, in order to simplify the code and improve compilation and runtime performance.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-6803) Add multi-server support to mod_cluster
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/WFLY-6803?page=com.atlassian.jira.plugin.... ]
Jan Kašík closed WFLY-6803.
---------------------------
Thanks! This was fixed by EAP7-977.
> Add multi-server support to mod_cluster
> ---------------------------------------
>
> Key: WFLY-6803
> URL: https://issues.jboss.org/browse/WFLY-6803
> Project: WildFly
> Issue Type: Feature Request
> Components: mod_cluster
> Affects Versions: 10.0.0.Final, 11.0.0.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 14.0.0.Beta2
>
>
> Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11033) mod_cluster custom load metrics fail to load
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík closed WFLY-11033.
----------------------------
Thanks! Verified!
> mod_cluster custom load metrics fail to load
> --------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 15.0.0.Beta1
>
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11388) User is not informed about incorrect values in exposed-subsystems for MP Metrics
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFLY-11388:
----------------------------------------
Summary: User is not informed about incorrect values in exposed-subsystems for MP Metrics
Key: WFLY-11388
URL: https://issues.jboss.org/browse/WFLY-11388
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
User is not informed about incorrect values in exposed-subsystems for MP Metrics
When I do stuff like
{code}
/subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"])
{code}
instead of
{code}
/subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch-jberet"])
{code}
I get no warning about non-existing subsystem.
User should be informed about misconfiguration.
Question is when:
- when server boots
- when the cli / management command is invoked
- both cases
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11387) IllegalStateException when calling MetricsContextService.stop during shutdown sequence
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFLY-11387?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda reassigned WFLY-11387:
----------------------------------------
Assignee: Jeff Mesnil (was: Jason Greene)
> IllegalStateException when calling MetricsContextService.stop during shutdown sequence
> --------------------------------------------------------------------------------------
>
> Key: WFLY-11387
> URL: https://issues.jboss.org/browse/WFLY-11387
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> IllegalStateException when calling MetricsContextService.stop during shutdown sequence
> This doesn't happen regularly, it happened to me like once from 5 shutdowns. I saw the warning 3 times today.
> "not happening always" is because of parallelism in shutdown/boot of WF/EAP
> I did slight misconfiguration on purpose, but not sure if it's related or not
> {code}
> /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"])
> {code}
> Stacktrace is this:
> {code}
> 09:53:23,883 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.extension.metrics.context: java.lang.IllegalStateException
> at org.jboss.as.domain-http-interface@7.0.0.Beta1//org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234)
> at org.jboss.as.server@7.0.0.Beta1//org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144)
> at org.wildfly.extension.microprofile.metrics-smallrye@15.0.0.CR1-SNAPSHOT//org.wildfly.extension.microprofile.metrics.MetricsContextService.stop(MetricsContextService.java:131)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11387) IllegalStateException when calling MetricsContextService.stop during shutdown sequence
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFLY-11387?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda updated WFLY-11387:
-------------------------------------
Priority: Critical (was: Major)
> IllegalStateException when calling MetricsContextService.stop during shutdown sequence
> --------------------------------------------------------------------------------------
>
> Key: WFLY-11387
> URL: https://issues.jboss.org/browse/WFLY-11387
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Critical
>
> IllegalStateException when calling MetricsContextService.stop during shutdown sequence
> This doesn't happen regularly, it happened to me like once from 5 shutdowns. I saw the warning 3 times today.
> "not happening always" is because of parallelism in shutdown/boot of WF/EAP
> I did slight misconfiguration on purpose, but not sure if it's related or not
> {code}
> /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"])
> {code}
> Stacktrace is this:
> {code}
> 09:53:23,883 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.extension.metrics.context: java.lang.IllegalStateException
> at org.jboss.as.domain-http-interface@7.0.0.Beta1//org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234)
> at org.jboss.as.server@7.0.0.Beta1//org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144)
> at org.wildfly.extension.microprofile.metrics-smallrye@15.0.0.CR1-SNAPSHOT//org.wildfly.extension.microprofile.metrics.MetricsContextService.stop(MetricsContextService.java:131)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months