May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4082) Cant use whitespaces in expression duration("P1Y")

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4082?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4082: -------------------------------- Fix Version/s: 7.23.0.Final > Cant use whitespaces in expression duration("P1Y") > -------------------------------------------------- > > Key: DROOLS-4082 > URL: https://issues.jboss.org/browse/DROOLS-4082 > Project: Drools > Issue Type: Bug > Affects Versions: 7.23.0.Final > Reporter: Yevgeniy Fomin > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.23.0.Final > > > If you will try use duration with white spaces it causing crashing of format in Enumeration -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4081) [DMN Designer] Constraints are allowed for inappropriate data types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4081?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4081: -------------------------------- Fix Version/s: 7.23.0.Final > [DMN Designer] Constraints are allowed for inappropriate data types > ------------------------------------------------------------------- > > Key: DROOLS-4081 > URL: https://issues.jboss.org/browse/DROOLS-4081 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.23.0.Final > > Attachments: Screenshot from 2019-05-27 17-51-55.png, Screenshot from 2019-05-27 17-52-08.png > > > Currently user is allowed to specify constraints even for *context* or *List* data type. See two attached cases. For both we should prohibit user from setting constraints. We should hide the constraints link/button. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4032) Parameterize Kogito source directory (default: src/main/resources)

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4032?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4032: ----------------------------------- Summary: Parameterize Kogito source directory (default: src/main/resources) (was: Add src/main/resources as compiler root directory to Maven plugin) > Parameterize Kogito source directory (default: src/main/resources) > ------------------------------------------------------------------ > > Key: DROOLS-4032 > URL: https://issues.jboss.org/browse/DROOLS-4032 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > this is required for the Quarkus extension to work -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4032) Add src/main/resources as compiler root directory to Maven plugin

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4032?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4032: ----------------------------------- Story Points: 3 (was: 1) > Add src/main/resources as compiler root directory to Maven plugin > ----------------------------------------------------------------- > > Key: DROOLS-4032 > URL: https://issues.jboss.org/browse/DROOLS-4032 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > this is required for the Quarkus extension to work -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4032) Add src/main/resources as compiler root directory to Maven plugin

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4032?page=com.atlassian.jira.plugi... ] Edoardo Vacchi commented on DROOLS-4032: ---------------------------------------- clarified f2f; we needed the maven plugin to declare a source directory in order for hot-code reload to work. We might not need this in the future, as we opt-in to go quarkus-extension-only (**if** people use quarkus; the maven plugin will stay for all other use cases). I am repurposing this ticket to include another change: allow the kie source directory (src/main/resources) to be customized i.e. not hardcode it. > Add src/main/resources as compiler root directory to Maven plugin > ----------------------------------------------------------------- > > Key: DROOLS-4032 > URL: https://issues.jboss.org/browse/DROOLS-4032 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > this is required for the Quarkus extension to work -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

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

by Gonzalo Muñoz Fernández (Jira)

[ https://issues.jboss.org/browse/WFLY-9631?page=com.atlassian.jira.plugin.... ] Gonzalo Muñoz Fernández commented on WFLY-9631: ----------------------------------------------- I've also tested with EAP 7.2.0.GA in Openshift, and same warning: 17:40:05,861 WARN [org.jboss.as.ejb3.timer] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'ROOT.ROOT.EJBTimerScheduler' (id=6f066747-f57e-4ad3-85e5-2a6f5e20333f) from its persistent state: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource 6f066747-f57e-4ad3-85e5-2a6f5e20333f at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:299) at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:178) at org.jboss.as.ejb3.subsystem.deployment.TimerServiceResource.timerCreated(TimerServiceResource.java:193) at org.jboss.as.ejb3.timerservice.TimerServiceImpl.registerTimerResource(TimerServiceImpl.java:1126) at org.jboss.as.ejb3.timerservice.TimerServiceImpl.startTimer(TimerServiceImpl.java:786) at org.jboss.as.ejb3.timerservice.TimerServiceImpl$TimerRefreshListener.timerAdded(TimerServiceImpl.java:1319) at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:832) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Then, following traces are shown: 17:54:06,718 INFO [org.jboss.as.ejb3.timer] (Timer-1) WFLYEJB0017: Next expiration is null. No tasks will be scheduled for timer [ID=9B432AAB-6388-40B3-8E1E-BB41909AB742 TIMEDOBJECTID=ROOT.ROOT.EJBTIMERSCHEDULER AUTO-TIMER?:FALSE PERSISTENT?:TRUE TIMERSERVICE=ORG.JBOSS.AS.EJB3.TIMERSERVICE.TIMERSERVICEIMPL@426E9346 INITIALEXPIRATION=2019-05-28 17:46:16.528 INTERVALDURATION(IN MILLI SEC)=0 NEXTEXPIRATION=NULL TIMERSTATE=ACTIVE INFO=EJBTIMERJOB [TIMERJOBINSTANCE=GLOBALJPATIMERJOBINSTANCE [TIMERSERVICEID=CONT-ID-TIMERSERVICEID, GETJOBHANDLE()=EJBGLOBALJOBHANDLE [UUID=2023-2022-1]]]] I was testing a performance scenario with EJB Timers for RHPAM (thousand of them are scheduled to be triggered at same time inside their corresponding processes). When "TIMER_SERVICE_DATA_STORE_REFRESH_INTERVAL" for the EJB timers is set up with a low value (120 seconds, for example), these timers are never triggered and our RHPAM processes do not finish. This only happens with one pod and low values of "TIMER_SERVICE_DATA_STORE_REFRESH_INTERVAL" (not happening when this value is set up to 60000 seconds, for example) > "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, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-112) Bypass ServiceLoader for AgroalDefaultSecurityProvider

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-112?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-112. ---------------------------- > Bypass ServiceLoader for AgroalDefaultSecurityProvider > ------------------------------------------------------ > > Key: AG-112 > URL: https://issues.jboss.org/browse/AG-112 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.5 > > > Make direct calls to AgroalDefaultSecurityProvider to work around limitations on some environments that have restrictions on reflection / service loader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-119) ResultSetWrapper does not remove itself from tracking statement

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-119?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-119. ---------------------------- > ResultSetWrapper does not remove itself from tracking statement > --------------------------------------------------------------- > > Key: AG-119 > URL: https://issues.jboss.org/browse/AG-119 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.5 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-111) Add a feature to remove connections older than a certain amount of time

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-111?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-111. ---------------------------- > Add a feature to remove connections older than a certain amount of time > ------------------------------------------------------------------------- > > Key: AG-111 > URL: https://issues.jboss.org/browse/AG-111 > Project: Agroal > Issue Type: Feature Request > Components: pool > Affects Versions: 1.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.5 > > > The reason behind this feature is firewalls with strict connection timeouts (even if the connection is active). In order to prevent those connections from becoming invalid, they should be removed before the firewall timeout. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-115) Replace deprecated calls to Class#newInstance to Constructor.newInstance

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-115?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-115. ---------------------------- > Replace deprecated calls to Class#newInstance to Constructor.newInstance > ------------------------------------------------------------------------ > > Key: AG-115 > URL: https://issues.jboss.org/browse/AG-115 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.5 > > -- 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 May 2019