[JBoss JIRA] (DROOLS-3405) [DMN Designer] Add support for collapsing Decision Services
by Michael Anstis (Jira)
Michael Anstis created DROOLS-3405:
--------------------------------------
Summary: [DMN Designer] Add support for collapsing Decision Services
Key: DROOLS-3405
URL: https://issues.jboss.org/browse/DROOLS-3405
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.16.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
Decision Services are shown _expanded_ by default.
We need to add the ability to collapse Decision Services hiding their content.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-2147?page=com.atlassian.jira.plugi... ]
Yeray Borges reassigned WFCORE-2147:
------------------------------------
Assignee: Yeray Borges
> Impossible to use environment variables or system properties in permissions.xml
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2147
> URL: https://issues.jboss.org/browse/WFCORE-2147
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Adrian Boangiu
> Assignee: Yeray Borges
> Priority: Major
>
> Without this feature it is impossible to migrate "variable" Java file permissions such as:
> {noformat}
> permission java.io.FilePermission "${java.io.tmpdir}","read";
> permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete";
> permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete";
> {noformat}
> that were defined in Java policy file in previous verions of JBoss.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3234) Add a Donut widget to improve the visualisation of test report screen
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3234?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3234:
-------------------------------------
[~kkufova] I will add my feedback, and ask that you consider these as possible "enhancements." Amy's issues seem like clear "bugs." I created a picture to illustrate some proposed enhancements (A):
* Metric in the center - the benefit of the doughnut chart is the ability to offer additional metrics in the center of the chart that speak to the whole unit - so in this case # of scenarios. Adding that would be nice. And better keeps to the spirit of the PatternFly pattern: https://www.patternfly.org/pattern-library/data-visualization/donut-chart/
* Imo, the legend should be static regardless of the outcome of the results - it should also explain the color for passed or failed. Example (B) is from the current implementation, "Failed" is missing.
* While it's somewhat obvious, I think it might be nice to offer the hint text for the segment regardless of the percentage value - "100%" as illustrated in example A. There is no harm in showing it and could provide additional information.
!donut.png|thumbnail!
A) Enhancements, B) Current implementation. ^^
Thanks Klara!
> Add a Donut widget to improve the visualisation of test report screen
> ---------------------------------------------------------------------
>
> Key: DROOLS-3234
> URL: https://issues.jboss.org/browse/DROOLS-3234
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: donut.png, screencast-04-12-18.webm
>
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JGRP-2316) DNS_PING is not using correct ports with SRV based service discovery
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2316:
--------------------------------
I think a better algorithm would be to always use the ports returned by SRV records *unless they're 0 or probe_transport_ports is true*.
> DNS_PING is not using correct ports with SRV based service discovery
> --------------------------------------------------------------------
>
> Key: JGRP-2316
> URL: https://issues.jboss.org/browse/JGRP-2316
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Reporter: dmcnair
> Assignee: Bela Ban
> Priority: Major
>
> This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve the port for SRV records. While that change is working as desired, `DNS_PING.java` is not using the port when doing member discovery.
> Here are the log entries using *4.0.15*
> {noformat}
> 2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105]
> 2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) 982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105] on ports [7600 .. 7600]
> {noformat}
> Since the port was found via the SRV record, it should be used instead of the *transportPort* port.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11477) README file at the root of the WildFy quickstarts needs to be made more readable
by Sande Gilda (Jira)
Sande Gilda created WFLY-11477:
----------------------------------
Summary: README file at the root of the WildFy quickstarts needs to be made more readable
Key: WFLY-11477
URL: https://issues.jboss.org/browse/WFLY-11477
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Reporter: Sande Gilda
Assignee: Sande Gilda
With the move to AsciiDoc and the use of variables, the README file in the root of the quickstarts is no longer readable in the WildFly quickstart repository. This isn't an issue with the JBoss EAP quickstarts because the build process generates the
README.html files.
The WildFly quickstarts also require that you build the server and BOMs, and that you install the parent artifact. We also need to provide instructions to developers to build the README.html files.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (LOGMGR-219) JBoss Logmanager is incompatibile with -Xbootclasspath and JDK 11
by Brian Stansberry (Jira)
Brian Stansberry created LOGMGR-219:
---------------------------------------
Summary: JBoss Logmanager is incompatibile with -Xbootclasspath and JDK 11
Key: LOGMGR-219
URL: https://issues.jboss.org/browse/LOGMGR-219
Project: JBoss Log Manager
Issue Type: Bug
Reporter: Brian Stansberry
Assignee: James Perkins
The current logmanager implementation is incompatible with use with the -Xbootclasspath/a option on JDK 11. The is because it is a multi-release jar which is incompatible with -Xbootclasspath/a. This is problematic because to allow Java Agents to work with JBoss Modules based applications (i.e. WildFly and derivatives) often it is necessary to include logmanager in -Xbootclasspath/a .
Here's me starting WildFly with a -Xbootclasspath/a setting and JDK 11:
{code}
$ build/target/wildfly-core-7.0.0.CR2-SNAPSHOT/bin/standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/bstansberry/dev/wildfly/wildfly-core/build/target/wildfly-core-7.0.0.CR2-SNAPSHOT
JAVA: /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.awt.headless=true -Xbootclasspath/a:/Users/bstansberry/dev/wildfly/wildfly-core/dist/target/wildfly-core-7.0.0.CR2-SNAPSHOT/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.5.Final.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-modules=java.se
=========================================================================
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.logmanager.LogLevelInitTask to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogLevelInitTask
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:57)
at org.jboss.as.server@7.0.0.CR2-SNAPSHOT//org.jboss.as.server.Main.main(Main.java:89)
at org.jboss.modules.Module.run(Module.java:352)
at org.jboss.modules.Module.run(Module.java:320)
at org.jboss.modules.Main.main(Main.java:593)
{code}
Right now jboss-logmanager is a multi-release jar. But, per the MR jar spec (https://openjdk.java.net/jeps/238) that is incompatible with -Xbootclasspath:
{quote}
Multi-release jars and the boot loader
Multi-release JARs are not supported by the boot loader (for example, when a multi-release JAR file is declared with the -Xbootclasspath/a option). Such support would complicate the boot loader implementation for what is considered a rare use-case.
{quote}
At this point I've identified two java agents that are commonly used with WildFly derived apps that cannot be installed in a JDK 11 environment: Hawkular and the Prometheus jmx-exporter. The former I could perhaps work around (i.e. don't install it with JDK 11) as it's use is deprecated. But being able to use of jmx-exporter is quite important.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months