November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3385) Stateful session is not thread safe for update operation on JDK11

by Radovan Synek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3385?page=com.atlassian.jira.plugi... ] Radovan Synek updated DROOLS-3385: ---------------------------------- Summary: Stateful session is not thread safe for update operation on JDK11 (was: Stateful session not thread safe for update operation) > Stateful session is not thread safe for update operation on JDK11 > ----------------------------------------------------------------- > > Key: DROOLS-3385 > URL: https://issues.jboss.org/browse/DROOLS-3385 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.16.0.Final > Reporter: Radovan Synek > Assignee: Mario Fusco > Priority: Critical > > We have a test failure in multithreaded solving in OptaPlanner (please see the linked issue for details). > java.util.ConcurrentModificationException: null > at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1134) > at org.drools.core.impl.KnowledgeBaseImpl.getOrCreateExactTypeDeclaration(KnowledgeBaseImpl.java:1458) > at org.drools.core.common.NamedEntryPoint.update(NamedEntryPoint.java:324) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:1570) > at org.optaplanner.core.impl.score.director.drools.DroolsScoreDirector.update(DroolsScoreDirector.java:254) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3385) Stateful session not thread safe for update operation

by Radovan Synek (Jira)

Radovan Synek created DROOLS-3385: ------------------------------------- Summary: Stateful session not thread safe for update operation Key: DROOLS-3385 URL: https://issues.jboss.org/browse/DROOLS-3385 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.16.0.Final Reporter: Radovan Synek Assignee: Mario Fusco We have a test failure in multithreaded solving in OptaPlanner (please see the linked issue for details). java.util.ConcurrentModificationException: null at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1134) at org.drools.core.impl.KnowledgeBaseImpl.getOrCreateExactTypeDeclaration(KnowledgeBaseImpl.java:1458) at org.drools.core.common.NamedEntryPoint.update(NamedEntryPoint.java:324) at org.drools.core.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:1570) at org.optaplanner.core.impl.score.director.drools.DroolsScoreDirector.update(DroolsScoreDirector.java:254) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11437) IllegalStateException on server shutdown

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11437?page=com.atlassian.jira.plugin... ] Jeff Mesnil resolved WFLY-11437. -------------------------------- Resolution: Duplicate Issue > IllegalStateException on server shutdown > ---------------------------------------- > > Key: WFLY-11437 > URL: https://issues.jboss.org/browse/WFLY-11437 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Richard Opalka > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 15.0.0.CR1 > > > 22:04:00,129 WARN [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000004: Failure during stop of service org.wildfly.extension.microprofile.metrics.http-context: java.lang.IllegalStateException > at org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234) > at org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144) > at org.wildfly.extension.microprofile.metrics.MetricsContextService.stop(MetricsContextService.java:130) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

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: ------------------------------------ Need some more info - 1. Do starting wildfly directly under bin path of wildfly starts it as a system process. 2. Does kill -15 $pid in custom stop script won't communicate effectively to the slave server like ctrl+c does. Will it still holds some resources for it to signal failure. 3. as per new rhel, it redirects to etc/systemd/system/aor_myproject_service.service and redirects as below ExecStart=/etc/init.d/aor_myproject_service start ExecStop = /etc/init.d/aor_myproject_service stop Do this impacting anything? > 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, 7 months

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], can you let me know if you have any update :) ? > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1632) Server processing request isn't stopped immediately but waits for request processing to finish

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-1632?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1632: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2557 (was: https://github.com/wildfly/wildfly-core/pull/1654) > Server processing request isn't stopped immediately but waits for request processing to finish > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1632 > URL: https://issues.jboss.org/browse/WFCORE-1632 > Project: WildFly Core > Issue Type: Bug > Components: IO, Management, Server > Reporter: Lin Gao > Assignee: Brian Stansberry > Priority: Critical > Original Estimate: 1 day > Remaining Estimate: 1 day > > When stopping server which is processing request, it terminates the connection from the client but doesn't stop the request processing as such. > After debugging and searching when the issue appeared I've found out that the issue was introduced with this commit: [https://github.com/wildfly/wildfly-core/commit/7304c019705c5f7ec0378e1c51...] > Steps to reproduce: > 1) start EAP server with deployed app from attachment > 2) create request to long running application: {{curl -i http://127.0.0.1:8080/long-running-servlet/HeavyProcessing?duration=25000}} > 3) stop server (you can do it even gracefully) using {{./jboss-cli.sh -c ":shutdown(timeout=1)"}} > See that server is stopped after 25 seconds since request from step 2 was issued, as that is duration of the request processing requested by param duration, instead of being terminated after 1 second. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-524) Checker Not Checking For Traffice Unless Skip-Checker Stage Is Run

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-524?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-524. -------------------------------- Resolution: Done > Checker Not Checking For Traffice Unless Skip-Checker Stage Is Run > ------------------------------------------------------------------ > > Key: SWSQE-524 > URL: https://issues.jboss.org/browse/SWSQE-524 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > The Checker job should validate Bookinfo Traffic every time that the traffic generator is deployed for the Bookinfo/Bookinfo2 meshes. > Currently the only time that Bookinfo Traffic is checked is when the Skip-Checker phase is run. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11437) IllegalStateException on server shutdown

by Richard Opalka (Jira)

Richard Opalka created WFLY-11437: ------------------------------------- Summary: IllegalStateException on server shutdown Key: WFLY-11437 URL: https://issues.jboss.org/browse/WFLY-11437 Project: WildFly Issue Type: Bug Components: MP Metrics Reporter: Richard Opalka Assignee: Jeff Mesnil Fix For: 15.0.0.CR1 22:04:00,129 WARN [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000004: Failure during stop of service org.wildfly.extension.microprofile.metrics.http-context: java.lang.IllegalStateException at org.jboss.as.domain.http.server.ManagementHttpServer.removeContext(ManagementHttpServer.java:234) at org.jboss.as.server.mgmt.UndertowHttpManagementService$1.removeContext(UndertowHttpManagementService.java:144) at org.wildfly.extension.microprofile.metrics.MetricsContextService.stop(MetricsContextService.java:130) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1794) at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1763) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-524) Checker Not Checking For Traffice Unless Skip-Checker Stage Is Run

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-524?page=com.atlassian.jira.plugin.... ] Matt Mahoney edited comment on SWSQE-524 at 11/28/18 3:17 PM: -------------------------------------------------------------- Jenkins pipeline file: http://git.app.eng.bos.redhat.com/git/kiali-qe-utils.git/tree/jenkins/jen... was (Author: mmahoney): Jenkins pipeline file: [http://git.app.eng.bos.redhat.com/git/kiali-qe-utils.git/tree/jenkins/jen...] > Checker Not Checking For Traffice Unless Skip-Checker Stage Is Run > ------------------------------------------------------------------ > > Key: SWSQE-524 > URL: https://issues.jboss.org/browse/SWSQE-524 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > The Checker job should validate Bookinfo Traffic every time that the traffic generator is deployed for the Bookinfo/Bookinfo2 meshes. > Currently the only time that Bookinfo Traffic is checked is when the Skip-Checker phase is run. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4239) WARN if system-property is already set and is being overridden

by Brad Maxwell (Jira)

Brad Maxwell created WFCORE-4239: ------------------------------------ Summary: WARN if system-property is already set and is being overridden Key: WFCORE-4239 URL: https://issues.jboss.org/browse/WFCORE-4239 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brad Maxwell Assignee: Jeff Mesnil WARN if system-property is already set and is being overridden If user sets a system property using the java opts or on the command line and the same system property is defined in the standalone.xml, then the standalone.xml value overrides that passed on the commandline/JAVA_OPTS, a warning would be useful as looking at the logs (and ps), it shows value1 passed on the command line and nothing indicating that the value was changed later. JAVA_OPTS="$JAVA_OPTS -Dmy.system.property=value1" {code} <system-properties> <property name="my.system.property" value="value2"/> </system-properties> {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

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 November 2018