[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Sarah Rambacher (Jira)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Sarah Rambacher commented on DROOLS-2522:
-----------------------------------------
The sizing of the icons inside the palette looks good now, thanks!!
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: DROOLS-2522 (resized).png, DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
> h2. Manual Acceptance test
> h3. Stunner
> - Chrome (/)
> - Firefox (/)
> - Edge (/)
> h3. DMN
> - Chrome (/)
> - Firefox (/)
> - Edge (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10531:
--------------------------------------------------
Thanks Jiri! I'll create a local build and report whether the error is gone for me! I have good faith in that this fix wil indeed solve the issue, the fix looks quite obvious :)
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jiri Ondrusek (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jiri Ondrusek commented on WFLY-10531:
--------------------------------------
I've prepared PR https://github.com/wildfly/wildfly/pull/11709, wchich contains fix of regression caused by https://github.com/wildfly/wildfly/pull/10614
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (DROOLS-3064) POJO Unification
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-3064:
--------------------------------------
Summary: POJO Unification
Key: DROOLS-3064
URL: https://issues.jboss.org/browse/DROOLS-3064
Project: Drools
Issue Type: Task
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
implement a general algorithm for recursive unification of POJO structures
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (SWSQE-450) Analyze Pipeline Execution Times
by Matt Mahoney (Jira)
Matt Mahoney created SWSQE-450:
----------------------------------
Summary: Analyze Pipeline Execution Times
Key: SWSQE-450
URL: https://issues.jboss.org/browse/SWSQE-450
Project: Kiali QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Filip Brychta
PR Jenkins CI jobs are taking at times 30 min to complete. Are there any optimization opportunities that could improve on the pipeline execution time duration?
This is just *one* snapshot of a pipeline time breakdown, but perhaps s
17 minutes was waiting (Spin up the Jenkins Agent)
17 minutes running the jobs themselves
Almost 2 minutes (1.30 min) to Install Istio (Which doesn't sound too much)
3 Minutes to Install Bookinfo
8 minutes to Build and Deploy Kiali
4 minutes -> to deploy kiali with Kiali Checker
4 minutes -> to build with Yarn
2 Minutes to run e2e-tests
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 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ý updated WFCORE-4147:
----------------------------------
Labels: Java11 (was: )
> (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: James Perkins
> 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)
6 years, 3 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ý updated WFCORE-4147:
----------------------------------
Description:
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
was:
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 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
> (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: James Perkins
> Priority: Blocker
>
> 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)
6 years, 3 months