[JBoss JIRA] (DROOLS-3877) DMN Decision table headers: Add edit table actions to contextual menu.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3877?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3877:
-------------------------------------------
[~manstis] The pic is just an example for this one grid/column of course. The menu for each would be contextual to the type of grid and header. :)
> DMN Decision table headers: Add edit table actions to contextual menu.
> ----------------------------------------------------------------------
>
> Key: DROOLS-3877
> URL: https://issues.jboss.org/browse/DROOLS-3877
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: Field, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-04-18 at 5.04.49 PM.png, header-context.png, header-context2b.png
>
>
> As a user of this feature I want to have the possibility to add columns or rows in a DT when right-clicking on the table header.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3877) DMN Decision table headers: Add edit table actions to contextual menu.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3877?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3877:
-------------------------------------------
[~manstis] Thanks for opening this up for consideration. I guess if I were to propose a more long term solution, then I would weigh in favor of consistency. In this case, because Scenario already has header menus then we should align with them. In which case then we would:
* Hide, rather than disable, the menu items that don't apply to the header.
* Use generic actions (Insert column left) with context-specific headers (Output Clause). This was presented earlier in this document: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-...
The menu would end up looking something like this:
!header-context2b.png|thumbnail!
I wasn't sure how to deal with Clear because I'm a little unclear (no pun intended) about that action? Also, I used the verbiage that [~stetson.robinson] recommended in the above document. I defer to him wrt adding an Append action or just leave it as "Insert row below" or "Insert row" (which could add to the bottom by default.)
The above would require reworking all the contextual menus in DMN, not just the header menus.
P.S. [~danielezonca] The header cell in Scenario does appear to get the highlight selection, is there a fix for that or is it in the works?
> DMN Decision table headers: Add edit table actions to contextual menu.
> ----------------------------------------------------------------------
>
> Key: DROOLS-3877
> URL: https://issues.jboss.org/browse/DROOLS-3877
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: Field, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-04-18 at 5.04.49 PM.png, header-context.png, header-context2b.png
>
>
> As a user of this feature I want to have the possibility to add columns or rows in a DT when right-clicking on the table header.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-6892) Access logging for EJBs
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ]
Cheng Fang updated WFLY-6892:
-----------------------------
Fix Version/s: 17.0.0.Beta1
> Access logging for EJBs
> -----------------------
>
> Key: WFLY-6892
> URL: https://issues.jboss.org/browse/WFLY-6892
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Cheng Fang
> Priority: Major
> Labels: affects_elytron
> Fix For: 17.0.0.Beta1
>
>
> Access logging for EJB requests similar to Web access logging would be very useful.
> Possibly something like:
> {code}
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet commented on WFLY-11026:
------------------------------------------
A simpler solution would be to use a dedicated Artemis server
> Journal compacting doesn't work with JDK 11
> -------------------------------------------
>
> Key: WFLY-11026
> URL: https://issues.jboss.org/browse/WFLY-11026
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final, 16.0.0.Final
> Environment: {noformat}
> java 11-ea 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11-ea+21)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {noformat}
> Reporter: Martin Styk
> Assignee: Emmanuel Hugonnet
> Priority: Critical
> Labels: Java11, jdk10, jdk11
>
> Journal compacting doesn't work with Artemis 1.5 and JDK 11
> It fails with following stack trace:
> {noformat}
> 12:34:58,017 ERROR [org.apache.activemq.artemis.journal] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$4@5483fda8)) AMQ144003: Error compacting: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at io.netty@4.1.25.Final//io.netty.util.internal.CleanerJava9.freeDirectBuffer(CleanerJava9.java:77)
> at io.netty@4.1.25.Final//io.netty.util.internal.PlatformDependent.freeDirectBuffer(PlatformDependent.java:388)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFileFactory.releaseBuffer(NIOSequentialFileFactory.java:175)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.doInternalWrite(NIOSequentialFile.java:312)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.internalWrite(NIOSequentialFile.java:282)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.writeDirect(NIOSequentialFile.java:255)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.AbstractJournalUpdateTask.flush(AbstractJournalUpdateTask.java:217)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.compact(JournalImpl.java:1520)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl$14.run(JournalImpl.java:2060)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalArgumentException: duplicate or slice
> at jdk.unsupported/sun.misc.Unsafe.invokeCleaner(Unsafe.java:1238)
> {noformat}
> This causes issues also in scenario with journal replication.
> {noformat}
> 13:09:32,133 WARN [org.apache.activemq.artemis.core.server] (Thread-173) AMQ222013: Error when trying to start replication: java.lang.RuntimeException: Error during compact, look at the logs
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.scheduleCompactAndBlock(JournalImpl.java:1428)
> at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.startReplication(JournalStorageManager.java:540)
> at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation$2.run(SharedNothingLiveActivation.java:166)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11
by Marcel Šebek (Jira)
[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ]
Marcel Šebek commented on WFLY-11026:
-------------------------------------
It is quite unfortunate that official Wildfly release notes mention JDK 11 as the recommended runtime JDK version, but the server is broken in such a critical way when running on this version of Java. I had to clone jboss-activemq-artemis repository, cherry-pick the fix, build artemis, and replace artemis-journal-2.6.3.jbossorg-00014.jar in the server modules directory to get the server working again. I hope that this will be fixed in Wildfly 17. The easiest way to do it is to release artemis-journal hotfix with cherry-picked fix, the harder way to rebase jboss version of activemq on 2.6.4, and the hardest way is to upgrade to 2.7.0. At least the first one is quite possible.
> Journal compacting doesn't work with JDK 11
> -------------------------------------------
>
> Key: WFLY-11026
> URL: https://issues.jboss.org/browse/WFLY-11026
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final, 16.0.0.Final
> Environment: {noformat}
> java 11-ea 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11-ea+21)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {noformat}
> Reporter: Martin Styk
> Assignee: Emmanuel Hugonnet
> Priority: Critical
> Labels: Java11, jdk10, jdk11
>
> Journal compacting doesn't work with Artemis 1.5 and JDK 11
> It fails with following stack trace:
> {noformat}
> 12:34:58,017 ERROR [org.apache.activemq.artemis.journal] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$4@5483fda8)) AMQ144003: Error compacting: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at io.netty@4.1.25.Final//io.netty.util.internal.CleanerJava9.freeDirectBuffer(CleanerJava9.java:77)
> at io.netty@4.1.25.Final//io.netty.util.internal.PlatformDependent.freeDirectBuffer(PlatformDependent.java:388)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFileFactory.releaseBuffer(NIOSequentialFileFactory.java:175)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.doInternalWrite(NIOSequentialFile.java:312)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.internalWrite(NIOSequentialFile.java:282)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.writeDirect(NIOSequentialFile.java:255)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.AbstractJournalUpdateTask.flush(AbstractJournalUpdateTask.java:217)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.compact(JournalImpl.java:1520)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl$14.run(JournalImpl.java:2060)
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalArgumentException: duplicate or slice
> at jdk.unsupported/sun.misc.Unsafe.invokeCleaner(Unsafe.java:1238)
> {noformat}
> This causes issues also in scenario with journal replication.
> {noformat}
> 13:09:32,133 WARN [org.apache.activemq.artemis.core.server] (Thread-173) AMQ222013: Error when trying to start replication: java.lang.RuntimeException: Error during compact, look at the logs
> at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.scheduleCompactAndBlock(JournalImpl.java:1428)
> at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.startReplication(JournalStorageManager.java:540)
> at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation$2.run(SharedNothingLiveActivation.java:166)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3784:
--------------------------------------
Sprint: 2019 Week 17-19
> Increase the advanced user productivity when he creates a new Data Type
> -----------------------------------------------------------------------
>
> Key: DROOLS-3784
> URL: https://issues.jboss.org/browse/DROOLS-3784
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Donato Marrazzo
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: Field, UX, UXTeam, drools-tools
> Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png
>
>
> The Data Type editor could be improved in terms of productivity and usability.
> Ideally, the user should be able to create a complex type minimizing the mouse usage.
> 1) Saving the node is an overhead for basic data type (e.g. age: number)
> 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete.
> 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11978) EAR with 2+ JPA does not shutdown cleanly
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11978?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11978:
-----------------------------------------
[~pferraro] FYI.
> EAR with 2+ JPA does not shutdown cleanly
> -----------------------------------------
>
> Key: WFLY-11978
> URL: https://issues.jboss.org/browse/WFLY-11978
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 16.0.0.Final
> Environment: Windows JDK8 WF16
> Reporter: Darryl Miles
> Assignee: Scott Marlow
> Priority: Major
> Attachments: td8948.txt
>
>
> EAR with 2+ JPA does not shutdown cleanly.
> I see in the logs each JPA project have an entry:
> WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project1'
> WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project2'
> then a few lines later:
> WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'blah....jpa.project2'
> I never see the "phase 1 of 2" entry for "jpa.project1" in the log.
> The container will wait 300 seconds and timeout.
> The management console during the time shows
> Operation: undeploy
> Execution Status: awaiting-stablility.
> The container is killed and the configuration.xml still contains the EAR deployment info, as undeploy did not complete.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months