May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9631) "Failed to reinstate timer" warning is shown when creating large number of EJB timers

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/WFLY-9631?page=com.atlassian.jira.plugin.... ] Martin Weiler updated WFLY-9631: -------------------------------- Attachment: WFLY-9631-reproducer.zip > "Failed to reinstate timer" warning is shown when creating large number of EJB timers > ------------------------------------------------------------------------------------- > > Key: WFLY-9631 > URL: https://issues.jboss.org/browse/WFLY-9631 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: EAP 7.0.8.GA > Oracle 12 c > [Configuration of datasources|https://github.com/MarianMacik/timers-testing/blob/c7dde64d27...] - XA Datasource for jBPM - our application - and a separate XA Datasource for EJB Timers in a different schema. > Reporter: Marian Macik > Assignee: Michal Jurc > Priority: Major > Attachments: WFLY-9631-reproducer.zip > > > Hi, [~manovotn], > as we discussed before, I am creating a JIRA for an issue I experienced when testing EJB Timers with jBPM. > What I did was that I started a large number of processes with jBPM, let's say 10 000 and more. Each process contains a timer which jBPM will create an EJB Timer for. Each timer was configured to fire at exactly the same time, e.g. 12:00 PM. During the test I got this warning displayed about 5 times for each 10 000 timers created: > {code:java} > WARN [org.jboss.as.ejb3] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' (id=09afab21-6b0f-41b0-9338-403b4a12e507) from its persistent state: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource 09afab21-6b0f-41b0-9338-403b4a12e507 > at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:290) > at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:169) > at org.jboss.as.ejb3.subsystem.deployment.TimerServiceResource.timerCreated(TimerServiceResource.java:193) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.registerTimerResource(TimerServiceImpl.java:1094) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.startTimer(TimerServiceImpl.java:767) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl$TimerRefreshListener.timerAdded(TimerServiceImpl.java:1235) > at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:820) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} > The result of these warnings was that when I had only one EAP instance to fire these timers, it wouldn't fire exactly the timers with ids that were in those warnings, e.g. if it was id=09afab21-6b0f-41b0-9338-403b4a12e507 then this timer wouldn't fire. I had waited for minutes to be sure there is another tick of a refresh interval (configured to 1 min) but nothing happened. But when I started the second EAP instance, they were immediately picked up by that instance and fired. It seems that if there is this warning on a particular instance, the instance won't pick up the timer whatsoever. They will be picked up only by some other instances if there are any. With 2 EAP instances there were warnings too, but all timers fired since I guess affected timers were picked up each time by the other instance. > Another interesting observation is that when I configured a refresh interval to be shorter, e.g. 5 seconds, these warnings were showing up almost every 5 seconds. When I set it to 30 minutes, I didn't get warnings at all, since all timers fired earlier than a refresh occurred. > So I think it has something to do with refresh interval. > Can you please have a look at it? For further configuration details, check the Environment field. > Thank you very much! > Marian Macik -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4047) Unable to use CSV in a ruleTemplate

by Adam Baxter (Jira)

[ https://issues.jboss.org/browse/DROOLS-4047?page=com.atlassian.jira.plugi... ] Adam Baxter commented on DROOLS-4047: ------------------------------------- Also, hi Mario! Long time no chat! > Unable to use CSV in a ruleTemplate > ----------------------------------- > > Key: DROOLS-4047 > URL: https://issues.jboss.org/browse/DROOLS-4047 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.5.0.Final, 7.21.0.Final > Environment: Any Java env > Reporter: Adam Baxter > Assignee: Mario Fusco > Priority: Major > Attachments: csv_import_test.tar.gz > > > I believe there is a bug where you cannot use a CSV file to use as a decision table to drive a ruleTemplate. Our issue appears to be a duplicate of the one mentioned in this pull request -https://github.com/kiegroup/drools/pull/1920 > The drools version we're using is 6.50.FINAL, but the reproducer I've attached is for the latest released version. > We'd like to move away from binary files as they're opaque to most version control and it makes branching difficult. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4047) Unable to use CSV in a ruleTemplate

by Adam Baxter (Jira)

Adam Baxter created DROOLS-4047: ----------------------------------- Summary: Unable to use CSV in a ruleTemplate Key: DROOLS-4047 URL: https://issues.jboss.org/browse/DROOLS-4047 Project: Drools Issue Type: Bug Components: decision tables Affects Versions: 7.21.0.Final, 6.5.0.Final Environment: Any Java env Reporter: Adam Baxter Assignee: Mario Fusco Attachments: csv_import_test.tar.gz I believe there is a bug where you cannot use a CSV file to use as a decision table to drive a ruleTemplate. Our issue appears to be a duplicate of the one mentioned in this pull request -https://github.com/kiegroup/drools/pull/1920 The drools version we're using is 6.50.FINAL, but the reproducer I've attached is for the latest released version. We'd like to move away from binary files as they're opaque to most version control and it makes branching difficult. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2833) Extend the CustomCLIExecutor to allow an assertion failure if the exit code was not 0

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-2833?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-2833. --------------------------------- Resolution: Rejected I'm not sure why I wanted this, but if hasn't been changed in a year I don't see the point of keeping it open. > Extend the CustomCLIExecutor to allow an assertion failure if the exit code was not 0 > ------------------------------------------------------------------------------------- > > Key: WFCORE-2833 > URL: https://issues.jboss.org/browse/WFCORE-2833 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently if the exit code of the CLI process is not equal to 0 the error may be logged. There should be an option to allow a failure if the exit code is not 0. A simple assertion should do since this is only in the test suite. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3997) [DMN Designer] Included Model Name marshalling issues depending on imported model name

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3997?page=com.atlassian.jira.plugi... ] Daniel José dos Santos commented on DROOLS-3997: ------------------------------------------------ As we talked in the BlueJeans, we have to change how we create the alias. Now we're creating the alias using the same name of the imported model (example: "foo import"). We have to change it to be something like "include1", "include2", etc. > [DMN Designer] Included Model Name marshalling issues depending on imported model name > -------------------------------------------------------------------------------------- > > Key: DROOLS-3997 > URL: https://issues.jboss.org/browse/DROOLS-3997 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-05-10 08-20-54.png, Screenshot from 2019-05-10 08-28-42.png > > > There is issue in marshalling, if the included model name contains *whitespace* character. In such case xml editor is opened instead of the dmn editor. See the attached picture and steps to reproduce for more details. > Issue spotted during review of DROOLS-3720 and DROOLS-3721. However it is probably not related. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-748) Import Kiali GoLang Unit Tests Into Polarion Run

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-748: ------------------------------------- Summary: Import Kiali GoLang Unit Tests Into Polarion Run Key: SWSQE-748 URL: https://issues.jboss.org/browse/SWSQE-748 Project: Kiali QE Issue Type: Sub-task Reporter: Matthew Mahoney Using the polarion_uploader tool, upload Kiali Unit Tests into Polarion. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-747) Capture Kiali GoLang Unit Test Results in JUnit Style Output

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-747: ------------------------------------- Summary: Capture Kiali GoLang Unit Test Results in JUnit Style Output Key: SWSQE-747 URL: https://issues.jboss.org/browse/SWSQE-747 Project: Kiali QE Issue Type: Sub-task Reporter: Matthew Mahoney Ref: https://github.com/gotestyourself/gotestsum#junit-xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-746) Include Kiali Unit Tests Results In PQI Metrics

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-746: ------------------------------------- Summary: Include Kiali Unit Tests Results In PQI Metrics Key: SWSQE-746 URL: https://issues.jboss.org/browse/SWSQE-746 Project: Kiali QE Issue Type: Story Reporter: Matthew Mahoney So that PQI metrics better reflect all automation tests, include Kiali GoLang Unit tests in PQI metrics. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-746) Include Kiali Unit Tests Results In PQI Metrics

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-746?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-746: ---------------------------------- Labels: infrastructure pqi (was: ) > Include Kiali Unit Tests Results In PQI Metrics > ----------------------------------------------- > > Key: SWSQE-746 > URL: https://issues.jboss.org/browse/SWSQE-746 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure, pqi > > So that PQI metrics better reflect all automation tests, include Kiali GoLang Unit tests in PQI metrics. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1525: ---------------------------------- Fix Version/s: 1.10.0.CR1 (was: 1.9.1.Final) > When SSO is enabled, multipart form and form enconding stop working. > -------------------------------------------------------------------- > > Key: ELY-1525 > URL: https://issues.jboss.org/browse/ELY-1525 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.6.Final, 1.2.1.Final > Reporter: Estevão Freitas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.10.0.CR1 > > > I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ". > I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On . > When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working. > If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019