December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3397) Move undoable logic to AbstractCommand

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3397: ---------------------------------------- Summary: Move undoable logic to AbstractCommand Key: DROOLS-3397 URL: https://issues.jboss.org/browse/DROOLS-3397 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Move undoable logic from AbstractScenarioSimulationCommand to AbstractCommand. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.1.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 commented on WFLY-11374: ------------------------------------ Hi [~mnovak], the issue is because of below 2 lines in the start function of my script. If I commented, the master is able to announce the backup. *rm -rf $JBOSS_HOME/standalone/tmp rm -rf $JBOSS_HOME/standalone/data* > Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: active standalone full ha.xml, master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, rotateserver_active.log, rotateserver_active.log, rotateserver_backup.log, rotateserver_slave.log, slave standalone full ha.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 which may be impacting and I am not clear - > 1.2018-11-21 14:28:07,238 TRACE [org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge] (Thread-18 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@38e819b6-2112524495)) Setting up bridge between TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-30 and ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-41], discoveryGroupConfiguration=null]: java.lang.Exception: trace > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.<init>(ClusterConnectionBridge.java:129) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.createNewRecord(ClusterConnectionImpl.java:778) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.nodeUP(ClusterConnectionImpl.java:698) > at org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:264) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > 2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11456) IllegalArgumentException in EJBClientInvocationContext.java:1116

by Dominik Derwiński (Jira)

Dominik Derwiński created WFLY-11456: ---------------------------------------- Summary: IllegalArgumentException in EJBClientInvocationContext.java:1116 Key: WFLY-11456 URL: https://issues.jboss.org/browse/WFLY-11456 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 14.0.1.Final Environment: jboss-ejb-client-4.0.11.Final Reporter: Dominik Derwiński Some calls to get throw IllegalArgumentException from wait method: {noformat} java.lang.IllegalArgumentException: nanosecond timeout value out of range at java.lang.Object.wait(Object.java:452) at org.jboss.ejb.client.EJBClientInvocationContext$FutureResponse.get(EJBClientInvocationContext.java:1116) {noformat} The code in line 1116 is: {code:java} lock.wait(remaining / 1_000_000_000L, (int) (remaining % 1_000_000_000L)); {code} JavaDoc of method wait(long timeout, int nanos) says that it will throw: {noformat} IllegalArgumentException - if the value of timeout is negative or the value of nanos is not in the range 0-999999. {noformat} The problem is division/modulo by 1_000_000_000, instead of 1_000_000. In other places in the same class this bug is not present, for example in line 904. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11455) Validate requirement for modules previously exported by javax.ejb.api on org.jboss.narayana.txframework

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11455?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-11455: -------------------------------- Description: Validate the need of these module dependencies in org.jboss.narayana.txframework {code:xml} <module name="javax.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} Notice the following: This module is deprecated was: Validate the need of these module dependencies in org.jboss.narayana.txframework {code:xml} <module name="javax.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} > Validate requirement for modules previously exported by javax.ejb.api on org.jboss.narayana.txframework > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-11455 > URL: https://issues.jboss.org/browse/WFLY-11455 > Project: WildFly > Issue Type: Sub-task > Components: Server > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > Validate the need of these module dependencies in org.jboss.narayana.txframework > {code:xml} > <module name="javax.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > Notice the following: This module is deprecated -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11455) Validate requirement for modules previously exported by javax.ejb.api on org.jboss.narayana.txframework

by Yeray Borges (Jira)

Yeray Borges created WFLY-11455: ----------------------------------- Summary: Validate requirement for modules previously exported by javax.ejb.api on org.jboss.narayana.txframework Key: WFLY-11455 URL: https://issues.jboss.org/browse/WFLY-11455 Project: WildFly Issue Type: Sub-task Components: Server Reporter: Yeray Borges Assignee: Yeray Borges Validate the need of these module dependencies in org.jboss.narayana.txframework {code:xml} <module name="javax.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-515) Overview Page - Automate View Change

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-515?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-515: ------------------------------------ Assignee: Hayk Hovsepyan (was: Michael Foley) > Overview Page - Automate View Change > ------------------------------------ > > Key: SWSQE-515 > URL: https://issues.jboss.org/browse/SWSQE-515 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Automate https://issues.jboss.org/browse/KIALI-1878 and https://issues.jboss.org/browse/KIALI-1721 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-515) Overview Page - Automate View Change

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-515?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-515: --------------------------------- Sprint: Kiali Sprint #14, Kiali Sprint #15 (was: Kiali Sprint #14) > Overview Page - Automate View Change > ------------------------------------ > > Key: SWSQE-515 > URL: https://issues.jboss.org/browse/SWSQE-515 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > > Automate https://issues.jboss.org/browse/KIALI-1878 and https://issues.jboss.org/browse/KIALI-1721 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11454) Validate requirement for modules previously exported by javax.ejb.api on org.jboss.metadata.appclient

by Yeray Borges (Jira)

Yeray Borges created WFLY-11454: ----------------------------------- Summary: Validate requirement for modules previously exported by javax.ejb.api on org.jboss.metadata.appclient Key: WFLY-11454 URL: https://issues.jboss.org/browse/WFLY-11454 Project: WildFly Issue Type: Sub-task Components: Server Reporter: Yeray Borges Assignee: Yeray Borges Validate the need of these module dependencies in org.jboss.metadata.appclient {code:xml} <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-516) Adjust sidecars KIALI-1888

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-516?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-516. ---------------------------------- Resolution: Done PR Merged > Adjust sidecars KIALI-1888 > -------------------------- > > Key: SWSQE-516 > URL: https://issues.jboss.org/browse/SWSQE-516 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[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 reopened WFLY-11384: --------------------------------- Still occurs. > StatefulFailoverTestCase fails intermittently > --------------------------------------------- > > Key: WFLY-11384 > URL: https://issues.jboss.org/browse/WFLY-11384 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 15.0.0.Beta1 > Environment: Any > Reporter: Ondrej Kotek > Assignee: Radoslav Husar > Priority: Major > Fix For: 15.0.0.Final > > > 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... > simpleFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=4824753507849... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2018