[JBoss JIRA] (DROOLS-3124) Nested GridCell/GridCellValue
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-3124:
----------------------------------------
Summary: Nested GridCell/GridCellValue
Key: DROOLS-3124
URL: https://issues.jboss.org/browse/DROOLS-3124
Project: Drools
Issue Type: Bug
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
Attachments: Screenshot from 2018-10-12 10-10-01.png
For some click/double click combination (not easy to reproduce) inside a gridcell, it seems that a nested GridCell or gridcellvallue will be created:
in the screenshot it is shown by the empty box inside the cell below do2.mydo1.myint1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFCORE-4115) JDK11 - GC logging format needs to be reviewed
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-4115?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-4115:
---------------------------------------
[~jamezp]:
* Weird naming of gc log files
** this would be probably fixed by one of the two scenarios on [WFCORE-4147 comment|https://issues.jboss.org/browse/WFCORE-4147?focusedCommentId=1364...].
* GC logs are much more verbose against jdk8 gc logs.
** If there is no option how to make JDK11 gc log more similar to JDK8 gc log, I have no objections for closing this part.
> JDK11 - GC logging format needs to be reviewed
> ----------------------------------------------
>
> Key: WFCORE-4115
> URL: https://issues.jboss.org/browse/WFCORE-4115
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts, Server
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Major
> Labels: Java11, jdk11
>
> * Weird naming of gc log files
> ** I test this with JDK11
> ** I start standalone and stop standalone
> ** JDK10 creates JBOSS_HOME/standalone/log/gc.log (with detailed information) and JBOSS_HOME/standalone/log/gc.log.0 (with brief summary of gc logging)
> ** I start standalone and stop standalone again
> ** JDK10 moves original gc.log to gc.log.1
> ** JDK10 keep original gc.log.0
> ** JDK10 creates new gc.log (with detailed information) and gc.log.2 (with brief summary of gc logging)
> ** Can this be changed by GC settings?
> * GC logs are much more verbose against jdk8 gc logs. Can this be fixed by some JDK10 gc settings?
> This is follow up for WFCORE-3996
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11
by Ingo Weiss (Jira)
[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ]
Ingo Weiss commented on WFLY-11026:
-----------------------------------
I can take a look at this and see how far I go
> 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
> 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: Martyn Taylor
> 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, 9 months
[JBoss JIRA] (WFCORE-4147) (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-4147?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-4147:
---------------------------------------
[~jamezp] Thank you for your investigation. So ... I guess that one (first or second) of these two options is correct, right? (the other one is wrong)
* sh and bat scripts shouldn't call "-version" command with JDK11, because it is redundant and it creates redundant and confusing (confusing for WF users) "gc.log.0" file
* ps1 script should call "-version" command with JDK11 (and probably also with JDK8), because this check is necessary. Sh, bat and ps1 scripts needs to remove redundant and confusing (confusing for WF users) "gc.log.0" file right after "-version" command on JDK11 (not necessary on JDK8)
> (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> ---------------------------------------------------------------
>
> Key: WFCORE-4147
> URL: https://issues.jboss.org/browse/WFCORE-4147
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: Radovan Stancel
> Priority: Blocker
> Labels: Java11
>
> Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
> * new blocker regression
> ** Wrong JAVA_OPTS propagation on JDK8
> *** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
> *** set "GC_LOG=true"
> *** standalone.bat
> *** ->
> *** {noformat}===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
> JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
> ==============================================================================={noformat}
> *** it looks like some quotation bug
> *** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
> * new blocker bug
> ** wrong PowerShell GC logging
> *** "standalone.bat + jdk11 + gc enabled" creates:
> **** standalone\log\gc.log
> **** standalone\log\gc.log.0
> *** "standalone.ps1 + jdk11 + gc enabled" creates:
> **** * standalone\log\gc.log
> Target release of this jira should be WF15
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3123) [DMN Designer] Decision Navigator throws and error in Read Only Mode
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3123:
-----------------------------------
Summary: [DMN Designer] Decision Navigator throws and error in Read Only Mode
Key: DROOLS-3123
URL: https://issues.jboss.org/browse/DROOLS-3123
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.13.0.Final
Reporter: Jozef Marko
Assignee: Guilherme Carreiro
Attachments: Screenshot from 2018-10-12 08-04-29.png
The decision navigator dock throws an error if user tries to navigate to expression of decision node while model is opened in read only mode. See the attached error.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-2804) [DMN Designer] Properties Panel to drill-down to DMN component level - Literal Expression
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2804?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2804:
--------------------------------
Description:
The Properties Panel currently shows properties for Stunner-level "graph" components.
We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type||Found Issues||
|Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118, DROOLS-3124|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
was:
The Properties Panel currently shows properties for Stunner-level "graph" components.
We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type||Found Issues||
|Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
> [DMN Designer] Properties Panel to drill-down to DMN component level - Literal Expression
> -----------------------------------------------------------------------------------------
>
> Key: DROOLS-2804
> URL: https://issues.jboss.org/browse/DROOLS-2804
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Literal expression
> ||Selected item||Properties panel items||type||Found Issues||
> |Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118, DROOLS-3124|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-2804) [DMN Designer] Properties Panel to drill-down to DMN component level - Literal Expression
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2804?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2804:
--------------------------------
Description:
The Properties Panel currently shows properties for Stunner-level "graph" components.
We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type||Found Issues||
|Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118, DROOLS-3122|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
was:
The Properties Panel currently shows properties for Stunner-level "graph" components.
We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type||Found Issues||
|Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118, DROOLS-3124|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
> [DMN Designer] Properties Panel to drill-down to DMN component level - Literal Expression
> -----------------------------------------------------------------------------------------
>
> Key: DROOLS-2804
> URL: https://issues.jboss.org/browse/DROOLS-2804
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth.
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Literal expression
> ||Selected item||Properties panel items||type||Found Issues||
> |Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118, DROOLS-3122|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months