[JBoss JIRA] (SWSQE-294) Investigate ElasticSearch memory requirements on B24 cluster
by Kevin Earls (JIRA)
[ https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin.... ]
Kevin Earls commented on SWSQE-294:
-----------------------------------
Bonjour,
En l'absence de votre correspondant, merci d'adresser votre email à Michael Foley - mfoley(a)redhat.com.
Bien cordialement.
-
Dear Sender,
In the absence of your contact, please send your email to Michael Foley - mfoley(a)redhat.com.
Many thanks.
-
Lieber Absender,
In Abwesenheit Ihrers Kontaktes senden Sie Ihre E-Mail bitte an Michael Foley - mfoley(a)redhat.com.
Vielen Dank.
> Investigate ElasticSearch memory requirements on B24 cluster
> ------------------------------------------------------------
>
> Key: SWSQE-294
> URL: https://issues.jboss.org/browse/SWSQE-294
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
> Attachments: es1.log
>
>
> On minishift and the CNCF CI OpenShift cluster, we install ElasticSearch using the commands:
> curl https://raw.githubusercontent.com/RHsyseng/docker-rhel-elasticsearch/5.x/... --output es-cluster-deployment.yml
> oc create -f es-cluster-deployment.yml
> However, on B24 this fails. The first 2 elasticsearch pods will start up, but then elasticsearch-2 gets into the following failure loop like:
> elasticsearch-2 1/1 Running 3 1m
> elasticsearch-2 0/1 OOMKilled 3 1m
> elasticsearch-2 0/1 CrashLoopBackOff 3 2m
> If I increase memory in the es-cluster-deployment.yml to 1Gi it will at least start, but I've found I really need to increase it to 2Gi to do anything non trivial.
> We may need to track down the people who originally created this template for help on this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-294) Investigate ElasticSearch memory requirements on B24 cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-294:
------------------------------------------
Team: Infrastructure (was: Infrastructure)
Sprint: Kiali QE Sprint 8
> Investigate ElasticSearch memory requirements on B24 cluster
> ------------------------------------------------------------
>
> Key: SWSQE-294
> URL: https://issues.jboss.org/browse/SWSQE-294
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
> Attachments: es1.log
>
>
> On minishift and the CNCF CI OpenShift cluster, we install ElasticSearch using the commands:
> curl https://raw.githubusercontent.com/RHsyseng/docker-rhel-elasticsearch/5.x/... --output es-cluster-deployment.yml
> oc create -f es-cluster-deployment.yml
> However, on B24 this fails. The first 2 elasticsearch pods will start up, but then elasticsearch-2 gets into the following failure loop like:
> elasticsearch-2 1/1 Running 3 1m
> elasticsearch-2 0/1 OOMKilled 3 1m
> elasticsearch-2 0/1 CrashLoopBackOff 3 2m
> If I increase memory in the es-cluster-deployment.yml to 1Gi it will at least start, but I've found I really need to increase it to 2Gi to do anything non trivial.
> We may need to track down the people who originally created this template for help on this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2738 at 7/16/18 8:58 AM:
---------------------------------------------------------------------
[~uxdlc],
Thank you for the new ideas. It's nice to see new approaches for this problem.
Given this structure:
- Person
-- name (String)
-- age (String)
-- address (Address)
--- city_name (String)
--- street (String)
--- zipcode (String)
I'm going to describe the steps that the user would need to do to define the structure above.
// First, the user needs to create fields for "Address"
1 - type "city_name" in the "Name Data Type" input;
2 - drag "String" from the "Basic" section and drop in the big square;
3 - click on "Add"
4 - type "street" in the "Name Data Type" input;
5 - drag "String" from the "Basic" section and drop in the big square;
6 - click on "Add"
7 - type "zipcode" in the "Name Data Type" input;
8 - drag "String" from the "Basic" section and drop in the big square;
9 - click on "Add"
// and then, the user creates the "Address" structure
11 - type "Address" in the "Name Data Type" input;
12 - drag "city_name" from the "Custom" section and drop in the big square;
13 - drag "street" from the "Custom" section and drop in the big square;
14 - drag "zipcode" from the "Custom" section and drop in the big square;
15 - click on "Add"
// and then, the user needs to create fields for "Person"
16 - type "name" in the "Name Data Type" input;
17 - drag "String" from the "Basic" section and drop in the big square;
18 - click on "Add"
19 - type "age" in the "Name Data Type" input;
20 - drag "Number" from the "Basic" section and drop in the big square;
21 - click on "Add"
22 - type "address" in the "Name Data Type" input;
23 - drag "Address" from the "Structured" section and drop in the big square;
24 - click on "Add"
// and then, the user creates the "Person" structure
25 - type "Person" in the "Name Data Type" input;
26 - drag "name" from the "Custom" section and drop in the big square;
27 - drag "age" from the "Custom" section and drop in the big square;
28 - drag "address" from the "Custom" section and drop in the big square;
29 - click on "Add"
I liked this model because everything is pretty explicit. However, the user needs to think in the entity from the most nested node to the top (from Address to the Person), and not the opposite. This can be difficult in deeply nested structures.
I think that is more intuitive for the user to create the entity Person and then create the entity Address (on demand). But, it's my personal opinion.
Thanks again, Liz. Please let know if I'm getting the steps wrong.
was (Author: karreiro):
@Liz,
Thank you for the new ideas. It's nice to see new approaches for this problem.
Given this structure:
- Person
-- name (String)
-- age (String)
-- address (Address)
--- city_name (String)
---- street (String)
---- zipcode (String)
I'm going to describe the steps that the user would need to do to define the structure above.
// First, the user needs to create fields for "Address"
1 - type "city_name" in the "Name Data Type" input;
2 - drag "String" from the "Basic" section and drop in the big square;
3 - click on "Add"
4 - type "street" in the "Name Data Type" input;
5 - drag "String" from the "Basic" section and drop in the big square;
6 - click on "Add"
7 - type "zipcode" in the "Name Data Type" input;
8 - drag "String" from the "Basic" section and drop in the big square;
9 - click on "Add"
// and then, the user creates the "Address" structure
11 - type "Address" in the "Name Data Type" input;
12 - drag "city_name" from the "Custom" section and drop in the big square;
13 - drag "street" from the "Custom" section and drop in the big square;
14 - drag "zipcode" from the "Custom" section and drop in the big square;
15 - click on "Add"
// and then, the user needs to create fields for "Person"
16 - type "name" in the "Name Data Type" input;
17 - drag "String" from the "Basic" section and drop in the big square;
18 - click on "Add"
19 - type "age" in the "Name Data Type" input;
20 - drag "Number" from the "Basic" section and drop in the big square;
21 - click on "Add"
22 - type "address" in the "Name Data Type" input;
23 - drag "Address" from the "Structured" section and drop in the big square;
24 - click on "Add"
// and then, the user creates the "Person" structure
25 - type "Person" in the "Name Data Type" input;
26 - drag "name" from the "Custom" section and drop in the big square;
27 - drag "age" from the "Custom" section and drop in the big square;
28 - drag "address" from the "Custom" section and drop in the big square;
29 - click on "Add"
I liked this model because everything is pretty explicit. However, the user needs to think in the entity from the most nested node to the top (from Address to the Person), and not the opposite. This can be difficult in deeply nested structures.
I think that is more intuitive for the user to create the entity Person and then create the entity Address (on demand). But, it's my personal opinion.
Thanks again, Liz. Please let know if I'm getting the steps wrong.
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: customDO-drilldown.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10474) AMQ119012: Timed out waiting to receive initial broadcast from cluster
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10474?page=com.atlassian.jira.plugin... ]
Erich Duda updated WFLY-10474:
------------------------------
Steps to Reproduce:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/447//artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ReplicatedColocatedClusterFailoverTestCase#testFailbackTransAckQueueTcpStack -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1527157321-wildfly-master-SNAPSHOT -DfailIfNoTests=false -Deap=7x | tee log
{code}
was:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout eap7.2.0.EO12
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/447//artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ReplicatedColocatedClusterFailoverTestCase#testFailbackTransAckQueueTcpStack -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1527157321-wildfly-master-SNAPSHOT -DfailIfNoTests=false -Deap=7x | tee log
{code}
> AMQ119012: Timed out waiting to receive initial broadcast from cluster
> ----------------------------------------------------------------------
>
> Key: WFLY-10474
> URL: https://issues.jboss.org/browse/WFLY-10474
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: blocker-WF14
>
> In messaging HA scenarios we see that tests sometimes fail because of exception \[1\]. The exception is thrown from {{ServerLocatorImpl::createSessionFactory}} which waits until initial broadcast from cluster is received, but it is not received in 10 seconds timeout. In following scenario the issue causes split brain - both live and backup are active at the same time.
> *Scenario*
> * There are two Wildfly/Artemis servers configured as Live-Backup pair
> * Live server is killed
> * Backup server becomes new Live server
> * Live server is restarted and failback is performed
> *Expectation:* Failback performs successfully. Original Live becomes Live again and original Backup becomes Backup again.
> *Reality:* After the Live is restarted, it does not detect that there is already another active Live with the same nodeId and it activates (becomes Live) so both Live and Backup are active at the same time.
> *Technical details*
> I found out that original Live server does not detect that its Backup is active, because SharedNothingLiveActivation::isNodeIdUsed returns false. I added more logs to this method and found out that the {{false}} is returned from line \[2\] after that the exception \[1\] is thrown.
> *Investigation report*
> I tried to downgrade Artemis to {{1.5.5.jbossorg-010}} version but I hit the same issue. So the issue is not caused by recent Artemis upgrade.
> It is regression against EAP 7.1.0.GA but it is not regression against Wildfly 12.
> We see the issue only with JGroups. I tried to run the test with Netty discovery and it passed 50 times in row.
> \[1\]
> {code}
> ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:749) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:627) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connectNoWarnings(ServerLocatorImpl.java:633) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.isNodeIdUsed(SharedNothingLiveActivation.java:280) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.run(SharedNothingLiveActivation.java:90) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:539) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:485) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:413) [artemis-jms-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:205) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT]
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:64) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT]
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:99) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_171]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_171]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> {code}
> \[2\] https://github.com/rh-messaging/jboss-activemq-artemis/blob/465eb8733e465...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-2738:
--------------------------------------------
@Liz,
Thank you for the new ideas. It's nice to see new approaches for this problem.
Given this structure:
- Person
-- name (String)
-- age (String)
-- address (Address)
--- city_name (String)
---- street (String)
---- zipcode (String)
I'm going to describe the steps that the user would need to do to define the structure above.
// First, the user needs to create fields for "Address"
1 - type "city_name" in the "Name Data Type" input;
2 - drag "String" from the "Basic" section and drop in the big square;
3 - click on "Add"
4 - type "street" in the "Name Data Type" input;
5 - drag "String" from the "Basic" section and drop in the big square;
6 - click on "Add"
7 - type "zipcode" in the "Name Data Type" input;
8 - drag "String" from the "Basic" section and drop in the big square;
9 - click on "Add"
// and then, the user creates the "Address" structure
11 - type "Address" in the "Name Data Type" input;
12 - drag "city_name" from the "Custom" section and drop in the big square;
13 - drag "street" from the "Custom" section and drop in the big square;
14 - drag "zipcode" from the "Custom" section and drop in the big square;
15 - click on "Add"
// and then, the user needs to create fields for "Person"
16 - type "name" in the "Name Data Type" input;
17 - drag "String" from the "Basic" section and drop in the big square;
18 - click on "Add"
19 - type "age" in the "Name Data Type" input;
20 - drag "Number" from the "Basic" section and drop in the big square;
21 - click on "Add"
22 - type "address" in the "Name Data Type" input;
23 - drag "Address" from the "Structured" section and drop in the big square;
24 - click on "Add"
// and then, the user creates the "Person" structure
25 - type "Person" in the "Name Data Type" input;
26 - drag "name" from the "Custom" section and drop in the big square;
27 - drag "age" from the "Custom" section and drop in the big square;
28 - drag "address" from the "Custom" section and drop in the big square;
29 - click on "Add"
I liked this model because everything is pretty explicit. However, the user needs to think in the entity from the most nested node to the top (from Address to the Person), and not the opposite. This can be difficult in deeply nested structures.
I think that is more intuitive for the user to create the entity Person and then create the entity Address (on demand). But, it's my personal opinion.
Thanks again, Liz. Please let know if I'm getting the steps wrong.
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: customDO-drilldown.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10700) WildFly13 Infinispan Query
by Majid Mostafavi (JIRA)
Majid Mostafavi created WFLY-10700:
--------------------------------------
Summary: WildFly13 Infinispan Query
Key: WFLY-10700
URL: https://issues.jboss.org/browse/WFLY-10700
Project: WildFly
Issue Type: Bug
Environment: {color:#14892c}Pom.xml{color}
<!-- cache -->
<infinispan.version>9.2.4.Final</infinispan.version>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-core</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-commons</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-cachestore-jdbc</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-cachestore-jpa</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-query</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-query-dsl</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-client-hotrod</artifactId>
<version>${infinispan.version}</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-lucene-directory</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-objectfilter</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-directory-provider</artifactId>
<version>${infinispan.version}</version>
</dependency>
<dependency>
<groupId>org.infinispan.protostream</groupId>
<artifactId>protostream</artifactId>
<version>4.0.0.Final</version>
</dependency>
-----------------------------------------------------------------------------------------------
{color:#14892c}jboss-deployment-structure.xml{color}
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<!--
we want to use the saaj module provided by JBoss
it looks like we can't use the implementation provided by the JDK - JBoss somehow does not seem to allow it
-->
<module name="com.sun.xml.messaging.saaj" />
<module name="org.antlr" export="true" services="export" />
<module name="org.infinispan" export="true" />
<module name="org.infinispan.commons" export="true" />
<module name="org.hibernate.search.engine" export="true"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
------------------------------------------------------------
{color:#f79232}CacheContainer{color} container = (CacheContainer) {color:#f79232}new{color} javax.naming.InitialContext().lookup(Configuration.getProperty("cache_name").trim());
this.{color:#205081}cache{color} =container.getCache();
-----------------------------------------------------------------------
{color:#59afe1}QueryFactory{color} queryFactory = {color:#59afe1}org.infinispan.query.Search.getQueryFactory{color}({color:#205081}systemManager.getCache(){color});
Reporter: Majid Mostafavi
Assignee: Jason Greene
{color:#d04437}16:58:45,501 ERROR [stderr] (default task-5) org.infinispan.commons.CacheException: ISPN014038: infinispan-query.jar module is in the classpath but has not been properly initialised!
16:58:45,502 ERROR [stderr] (default task-5) at org.infinispan.query.Search.getQueryFactory(Search.java:60)
16:58:45,502 ERROR [stderr] (default task-5) at ir.ac.tums.core.utils.SystemManager$Proxy$_$$_WeldClientProxy.findOrganizations(Unknown Source)
16:58:45,502 ERROR [stderr] (default task-5) at ir.ac.tums.core.managedBean.SystemManagerBean.findOrganizations(SystemManagerBean.java:48)
16:58:45,503 ERROR [stderr] (default task-5) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
16:58:45,503 ERROR [stderr] (default task-5) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
16:58:45,503 ERROR [stderr] (default task-5) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
16:58:45,503 ERROR [stderr] (default task-5) at java.lang.reflect.Method.invoke(Method.java:498)
16:58:45,503 ERROR [stderr] (default task-5) at com.sun.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:181)
16:58:45,503 ERROR [stderr] (default task-5) at com.sun.el.parser.AstValue.invoke(AstValue.java:289)
16:58:45,503 ERROR [stderr] (default task-5) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:304)
16:58:45,504 ERROR [stderr] (default task-5) at org.jboss.weld.module.web.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40)
16:58:45,504 ERROR [stderr] (default task-5) at org.jboss.weld.module.web.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
16:58:45,504 ERROR [stderr] (default task-5) at org.jboss.weld.module.web.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40)
16:58:45,504 ERROR [stderr] (default task-5) at org.jboss.weld.module.web.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
16:58:45,504 ERROR [stderr] (default task-5) at javax.faces.event.MethodExpressionActionListener.processAction(MethodExpressionActionListener.java:149)
16:58:45,504 ERROR [stderr] (default task-5) at javax.faces.event.ActionEvent.processListener(ActionEvent.java:88)
16:58:45,505 ERROR [stderr] (default task-5) at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:814)
16:58:45,505 ERROR [stderr] (default task-5) at javax.faces.component.UICommand.broadcast(UICommand.java:300)
16:58:45,505 ERROR [stderr] (default task-5) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:790)
16:58:45,505 ERROR [stderr] (default task-5) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1282)
16:58:45,505 ERROR [stderr] (default task-5) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
16:58:45,505 ERROR [stderr] (default task-5) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
16:58:45,505 ERROR [stderr] (default task-5) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198)
16:58:45,505 ERROR [stderr] (default task-5) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:658)
16:58:45,506 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
16:58:45,506 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
16:58:45,506 ERROR [stderr] (default task-5) at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)
16:58:45,506 ERROR [stderr] (default task-5) at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)
16:58:45,506 ERROR [stderr] (default task-5) at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
16:58:45,506 ERROR [stderr] (default task-5) at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
16:58:45,506 ERROR [stderr] (default task-5) at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:387)
16:58:45,507 ERROR [stderr] (default task-5) at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)
16:58:45,507 ERROR [stderr] (default task-5) at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)
16:58:45,507 ERROR [stderr] (default task-5) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
16:58:45,507 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
16:58:45,507 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
16:58:45,507 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
16:58:45,507 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68)
16:58:45,507 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
16:58:45,508 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
16:58:45,508 ERROR [stderr] (default task-5) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
16:58:45,509 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
16:58:45,509 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
16:58:45,509 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
16:58:45,510 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
16:58:45,510 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
16:58:45,510 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
16:58:45,510 ERROR [stderr] (default task-5) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
16:58:45,510 ERROR [stderr] (default task-5) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
16:58:45,510 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
16:58:45,510 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
16:58:45,510 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
16:58:45,510 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
16:58:45,511 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
16:58:45,511 ERROR [stderr] (default task-5) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
16:58:45,511 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
16:58:45,511 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
16:58:45,511 ERROR [stderr] (default task-5) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
16:58:45,511 ERROR [stderr] (default task-5) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
16:58:45,511 ERROR [stderr] (default task-5) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
16:58:45,511 ERROR [stderr] (default task-5) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
16:58:45,511 ERROR [stderr] (default task-5) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
16:58:45,511 ERROR [stderr] (default task-5) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
16:58:45,511 ERROR [stderr] (default task-5) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
16:58:45,511 ERROR [stderr] (default task-5) at java.lang.Thread.run(Thread.java:748){color}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10474) AMQ119012: Timed out waiting to receive initial broadcast from cluster
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10474?page=com.atlassian.jira.plugin... ]
Erich Duda updated WFLY-10474:
------------------------------
Priority: Blocker (was: Critical)
> AMQ119012: Timed out waiting to receive initial broadcast from cluster
> ----------------------------------------------------------------------
>
> Key: WFLY-10474
> URL: https://issues.jboss.org/browse/WFLY-10474
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: blocker-WF14
>
> In messaging HA scenarios we see that tests sometimes fail because of exception \[1\]. The exception is thrown from {{ServerLocatorImpl::createSessionFactory}} which waits until initial broadcast from cluster is received, but it is not received in 10 seconds timeout. In following scenario the issue causes split brain - both live and backup are active at the same time.
> *Scenario*
> * There are two Wildfly/Artemis servers configured as Live-Backup pair
> * Live server is killed
> * Backup server becomes new Live server
> * Live server is restarted and failback is performed
> *Expectation:* Failback performs successfully. Original Live becomes Live again and original Backup becomes Backup again.
> *Reality:* After the Live is restarted, it does not detect that there is already another active Live with the same nodeId and it activates (becomes Live) so both Live and Backup are active at the same time.
> *Technical details*
> I found out that original Live server does not detect that its Backup is active, because SharedNothingLiveActivation::isNodeIdUsed returns false. I added more logs to this method and found out that the {{false}} is returned from line \[2\] after that the exception \[1\] is thrown.
> *Investigation report*
> I tried to downgrade Artemis to {{1.5.5.jbossorg-010}} version but I hit the same issue. So the issue is not caused by recent Artemis upgrade.
> It is regression against EAP 7.1.0.GA but it is not regression against Wildfly 12.
> We see the issue only with JGroups. I tried to run the test with Netty discovery and it passed 50 times in row.
> \[1\]
> {code}
> ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:749) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:627) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connectNoWarnings(ServerLocatorImpl.java:633) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.isNodeIdUsed(SharedNothingLiveActivation.java:280) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.run(SharedNothingLiveActivation.java:90) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:539) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:485) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:413) [artemis-jms-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT]
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:205) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT]
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:64) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT]
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:99) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_171]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_171]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
> {code}
> \[2\] https://github.com/rh-messaging/jboss-activemq-artemis/blob/465eb8733e465...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years