[JBoss JIRA] (DROOLS-2747) [DMN Designer] Support table header cell selection
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2747?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-2747:
----------------------------------
Component/s: Scenario Simulation and Testing
> [DMN Designer] Support table header cell selection
> --------------------------------------------------
>
> Key: DROOLS-2747
> URL: https://issues.jboss.org/browse/DROOLS-2747
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2018-03-20 08-59-39.png, Screenshot from 2018-03-20 09-20-04.png
>
>
> The decision table header cell does not support highlight / selection feature, see:
> !Screenshot from 2018-03-20 08-59-39.png|thumbnail!
> In contrast context entry name cell support this:
> !Screenshot from 2018-03-20 09-20-04.png|thumbnail!
> The outline should be consistent, i.e. blue rectangle should be rendered regardless of the selected cell type (data vs. header).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-9631) "Failed to reinstate timer" warning is shown when creating large number of EJB timers
by Marián Macik (Jira)
[ https://issues.jboss.org/browse/WFLY-9631?page=com.atlassian.jira.plugin.... ]
Marián Macik commented on WFLY-9631:
------------------------------------
[~mjurc]
is there a way we can push this a little bit to at least know if this is a bug or a potential misconfiguration?
> "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: Marián Macik
> Assignee: Michal Jurc
> Priority: Major
>
> 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, 7 months
[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi edited comment on DROOLS-3073 at 10/8/18 3:09 AM:
-------------------------------------------------------------------
[~jomarko] [~kkufova]
The exception is due to a server-side bug ( https://issues.jboss.org/browse/DROOLS-3085 ).
For the moment being, be sure to fill the "description" field
The behavior is expected.
was (Author: gabriolo):
[~jomarko][~kkufova]
The exception is due to a server-side bug ( https://issues.jboss.org/browse/DROOLS-3085 ).
The behavior is expected.
> Wrong full package if you use classes from another folder
> ----------------------------------------------------------
>
> Key: DROOLS-3073
> URL: https://issues.jboss.org/browse/DROOLS-3073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip
>
>
> Step to reproduce:
> - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject)
> - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace)
> - Use Data Objects tab to import "Object1" to "Test1"
> - Reload the asset and map a field of "Object1" to a column
> - Fill "Test1" with valid values
> - Run the scenario
> Result: Impossible to load class com.myspace.Object1
> Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3073:
------------------------------------------
[~jomarko][~kkufova]
The exception is due to a server-side bug ( https://issues.jboss.org/browse/DROOLS-3085 ).
The behavior is expected.
> Wrong full package if you use classes from another folder
> ----------------------------------------------------------
>
> Key: DROOLS-3073
> URL: https://issues.jboss.org/browse/DROOLS-3073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip
>
>
> Step to reproduce:
> - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject)
> - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace)
> - Use Data Objects tab to import "Object1" to "Test1"
> - Reload the asset and map a field of "Object1" to a column
> - Fill "Test1" with valid values
> - Run the scenario
> Result: Impossible to load class com.myspace.Object1
> Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months