November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3150) Race condition on clicks to enable inline editing into Scenario grid

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3150: --------------------------------- Story Points: 5 > Race condition on clicks to enable inline editing into Scenario grid > -------------------------------------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2298) InputStream is processed after the different version error

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2298?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2298: -------------------------------- Eventually, reading gibberish would lead to closing the connection, too, so this should not produce incorrect behavior... > InputStream is processed after the different version error > ---------------------------------------------------------- > > Key: JGRP-2298 > URL: https://issues.jboss.org/browse/JGRP-2298 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.11, 4.0.13 > Environment: OS: Debian 8 > Reporter: Boris Kantor > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.16 > > > Occasionally JGroups shows up a warning when receiving a message with a different JGroups version: > {{JGRP000010: packet from 10.10.10.130:7800 has different version (0.0.0) than ours (4.0.11); packet is discarded | (Log4J2LogImpl.java:91)}} > Although the message is then discarded, the socket connection will be kept open. The input stream still contains data that will be processed and falsly interpreted as the next message. > If you have bad luck, the next bytes will match the correct version number. This leads then to following errors: > {code:java} > 2018-07-17 10:15:34.052 [Connect | ] WARN TCP - JGRP000010: packet from 10.10.10.130:7800 has different version (0.0.0) than ours (4.0.11); packet is discarded | (Log4J2LogImpl.java:91) > 2018-07-17 10:15:34.059 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 8237 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.065 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 8237 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.072 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.io.IOException: length has to be 4 or 16 bytes (was 47 bytes) > at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:171) > at org.jgroups.util.Util.readAddress(Util.java:1379) > at org.jgroups.Message.readFrom(Message.java:731) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.076 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 28789 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.077 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 8237 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.078 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.io.IOException: length has to be 4 or 16 bytes (was 47 bytes) > at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:171) > at org.jgroups.util.Util.readAddress(Util.java:1379) > at org.jgroups.Message.readFrom(Message.java:731) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.078 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 8237 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.079 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.io.IOException: length has to be 4 or 16 bytes (was 47 bytes) > at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:171) > at org.jgroups.util.Util.readAddress(Util.java:1379) > at org.jgroups.Message.readFrom(Message.java:731) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.080 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 12320 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.089 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 25193 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1346) > at org.jgroups.protocols.TP.receive(TP.java:1323) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > 2018-07-17 10:15:34.107 [Connect | ] ERROR TCP - JGRP000030: jgm113: failed handling incoming message | (Log4J2LogImpl.java:116) > java.lang.ClassNotFoundException: Class for magic number 25970 cannot be found > at org.jgroups.conf.ClassConfigurator.create(ClassConfigurator.java:118) > at org.jgroups.Message.readHeader(Message.java:869) > at org.jgroups.Message.readFrom(Message.java:742) > at org.jgroups.util.Util.readMessageBatch(Util.java:1193) > at org.jgroups.protocols.TP.handleMessageBatch(TP.java:1329) > at org.jgroups.protocols.TP.receive(TP.java:1321) > at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171) > at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290) > at eu.application.nac.cluster.jgroups.JGroupsTask.execute(JGroupsTask.java:41) > at eu.application.nac.engine.scheduling.Task.run(Task.java:339) > at java.lang.Thread.run(Thread.java:745) > {code} > When it comes to the payload of the message the size of the payload can be as big as 2GB ({{len=in.readInt();}}). On small machines this will lead to an OutOfMemoryError. > There is a need for some handling of such misinterpreted messages. Like closing and reopening a socket connection or completely ignoring the following bytes until a new message begins or an other algorithm that would prevent the processing of the remaining bytes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3082) Header Edit Mode remains active

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3082?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3082: --------------------------------- Sprint: 2018 Week 45-47 > Header Edit Mode remains active > ------------------------------- > > Key: DROOLS-3082 > URL: https://issues.jboss.org/browse/DROOLS-3082 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: Screenshot from 2018-10-05 15-23-39.png > > > Sometimes during editing header cells they remains in edit mode unexpectedly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3150) Race condition on clicks to enable inline editing into Scenario grid

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3150: --------------------------------- Sprint: 2018 Week 45-47 > Race condition on clicks to enable inline editing into Scenario grid > -------------------------------------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3177) Move to public API RegistryContext

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3177?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3177: --------------------------------- Story Points: 5 > Move to public API RegistryContext > ---------------------------------- > > Key: DROOLS-3177 > URL: https://issues.jboss.org/browse/DROOLS-3177 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation > > RegistryContext interface is inside drools-core but should be moved to public to be able to use it for custom commands > Remove drools-core dependency from scenario simulation backend module after that -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3177) Move to public API RegistryContext

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3177?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3177: ---------------------------------- Sprint: 2018 Week 45-47 > Move to public API RegistryContext > ---------------------------------- > > Key: DROOLS-3177 > URL: https://issues.jboss.org/browse/DROOLS-3177 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation > > RegistryContext interface is inside drools-core but should be moved to public to be able to use it for custom commands > Remove drools-core dependency from scenario simulation backend module after that -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3234) Add a Donut widget to improve the visualisation of test report screen

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3234?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3234: --------------------------------- Story Points: 5 > Add a Donut widget to improve the visualisation of test report screen > --------------------------------------------------------------------- > > Key: DROOLS-3234 > URL: https://issues.jboss.org/browse/DROOLS-3234 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3099) Add advanced column properties

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3099?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3099: --------------------------------- Story Points: 5 > Add advanced column properties > ------------------------------ > > Key: DROOLS-3099 > URL: https://issues.jboss.org/browse/DROOLS-3099 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > > As user I want to be able to specify advanced column properties like hidden, required and default value -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-146) WARN messages when /metrics endpoint is accessed

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-146?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFWIP-146. ------------------------------- Resolution: Done fixed in dev branch 37a845c64c46e8307a8b50b938bb586441588f45 > WARN messages when /metrics endpoint is accessed > ------------------------------------------------ > > Key: WFWIP-146 > URL: https://issues.jboss.org/browse/WFWIP-146 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > WARN messages when /metrics endpoint is accessed. > With standalone.xml I see 12 warnings. > {code} > 14:52:14,117 WARN [io.smallrye.metrics] (management I/O-1) Unable to export metric subsystem_undertow_server_default_server_http_listener_default_processing_time: java.lang.IllegalStateException: WFLYMETRICS0006: Metric attribute processing-time on [ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("http-listener" => "default") > ] is undefined and will not be exposed. > at org.wildfly.extension.microprofile.metrics-smallrye@15.0.0.Alpha1-SNAPSHOT//org.wildfly.extension.microprofile.metrics.MetricsRegistrationService$1.getValue(MetricsRegistrationService.java:197) > at org.wildfly.extension.microprofile.metrics-smallrye@15.0.0.Alpha1-SNAPSHOT//org.wildfly.extension.microprofile.metrics.MetricsRegistrationService$1.getValue(MetricsRegistrationService.java:174) > at io.smallrye.metrics//io.smallrye.metrics.exporters.PrometheusExporter.createSimpleValueLine(PrometheusExporter.java:340) > at io.smallrye.metrics//io.smallrye.metrics.exporters.PrometheusExporter.exposeEntries(PrometheusExporter.java:140) > at io.smallrye.metrics//io.smallrye.metrics.exporters.PrometheusExporter.getEntriesForScope(PrometheusExporter.java:116) > at io.smallrye.metrics//io.smallrye.metrics.exporters.PrometheusExporter.exportAllScopes(PrometheusExporter.java:85) > at io.smallrye.metrics//io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:83) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3099) Add advanced column properties

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3099?page=com.atlassian.jira.plugi... ] Klara Kufova reassigned DROOLS-3099: ------------------------------------ Assignee: Gabriele Cardosi (was: Daniele Zonca) > Add advanced column properties > ------------------------------ > > Key: DROOLS-3099 > URL: https://issues.jboss.org/browse/DROOLS-3099 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > > As user I want to be able to specify advanced column properties like hidden, required and default value -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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