[Red Hat JIRA] (WFCORE-4970) Changing the JVM settings at host level does not put the servers in restart-required
by Yeray Borges Santana (Jira)
[ https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug... ]
Yeray Borges Santana updated WFCORE-4970:
-----------------------------------------
Priority: Minor (was: Major)
[~parsharma] My understanding of Brian's suggestion by inspecting the possibilities of using [arbitrary descriptors|https://docs.wildfly.org/22/Admin_Guide.html#arbitrary-descri...] was to use this additional metadata to describe that certain attribute modifications need to restart the managed servers JVMs.
If that's correct and since all the attributes need a JVM restart, I think it would be enough to enhance the resource description itself and describe there that changes in the attributes of these resources will require to restart of the managed servers to make the changes effective.
The point here seems to be that the following resources change the configuration of the managed servers JVM:
/host=*/jvm=
/host=*/server-config=*/jvm=
/server-group=*/jvm=
However, modifying this configuration should not affect the HC process. If we flag the jvm attributes with setRestartJvm, then the HC process-state will get a restart-required. What is required is to restart the affected managed servers to make the changes effective, but not the HC itself.
> Changing the JVM settings at host level does not put the servers in restart-required
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-4970
> URL: https://issues.redhat.com/browse/WFCORE-4970
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 12.0.0.Beta2
> Reporter: Yeray Borges Santana
> Assignee: Parul Sharma
> Priority: Minor
>
> Operations like the following one should put the servers in restart required to indicate the user changes will be applied after restarting the servers:
> {noformat}
> [domain@localhost:9990 /] /host=master/jvm=default:write-attribute(name=heap-size, value=256m)
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-4170) [DMN Designer] Decision Navigator Firefox styling issue
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4170?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-4170.
-------------------------------
Resolution: Won't Do
Minor issue still reproducible, however too long without any progress. Not reported by a customer.
> [DMN Designer] Decision Navigator Firefox styling issue
> -------------------------------------------------------
>
> Key: DROOLS-4170
> URL: https://issues.redhat.com/browse/DROOLS-4170
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Environment: firefox
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Attachments: chrome.png, firefox.png
>
>
> We have a minor styling issue in the Decision Navigator shown on Firefox. Please compare the attached pictures from Chrome and Firefox. On Firefox there is no whitespace between function icon and text. On Chrome it is.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-4419) [DMN Designer] User can search for non-existing data type
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4419?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-4419.
-------------------------------
Resolution: Won't Do
Over year without a progress
> [DMN Designer] User can search for non-existing data type
> ---------------------------------------------------------
>
> Key: DROOLS-4419
> URL: https://issues.redhat.com/browse/DROOLS-4419
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.25.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: search-edit.webm, search.webm
>
>
> User can search for a non existing result and then error is thrown.
> Imagine situation, you are going trough search results. You stop at one of them. You decide to edit it or remove it completely. The you want to continue going trough results however an error is thrown. See the attached video.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month