[JBoss JIRA] (WFLY-10504) -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-10504?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-10504:
---------------------------------
Priority: Critical (was: Major)
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> -----------------------------------------------------------------------
>
> Key: WFLY-10504
> URL: https://issues.jboss.org/browse/WFLY-10504
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: R Searls
> Priority: Critical
>
> -secmgr and SECMGR=true env property doesn't work for domain.ps1 script
> Steps to reproduce:
> # start powershell
> # .\domain.bat "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is present in PC or HC
> # exit domain.bat
> # .\domain.ps1 "-secmgr"
> # WMIC PROCESS get Commandline | findstr java
> # check that "-secmgr" property is *not* present in PC or HC
> Secmgr can't be enabled also by $env:SECMGR = "true"
> This issue is not about java-opts, but it is related with WFCORE-3830
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3137:
--------------------------------
Description:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
- -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
- -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
- -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
- -Change of constraint type should re-render constraint component appropriately-
- Constraint component should be rendered appropriately between two openings of Manage Types dialog (/)
- "Add Constraints" Tick/Untick shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console (/)
was:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
- -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
- -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
- -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
- -Change of constraint type should re-render constraint component appropriately-
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- "Add Constraints" Tick/Untick shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console (/)
> [DMN Designer] Data Types Type - Constraints - MVP component
> ------------------------------------------------------------
>
> Key: DROOLS-3137
> URL: https://issues.jboss.org/browse/DROOLS-3137
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
> - -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
> - -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
> - -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
> - -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
> - -Change of constraint type should re-render constraint component appropriately-
> - Constraint component should be rendered appropriately between two openings of Manage Types dialog (/)
> - "Add Constraints" Tick/Untick shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3137:
--------------------------------
Description:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
- -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
- -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
- -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
- -Change of constraint type should re-render constraint component appropriately-
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- "Add Constraints" Tick/Untick shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console (/)
was:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
- -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
- -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
- -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
- -Change of constraint type should re-render constraint component appropriately-
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
> [DMN Designer] Data Types Type - Constraints - MVP component
> ------------------------------------------------------------
>
> Key: DROOLS-3137
> URL: https://issues.jboss.org/browse/DROOLS-3137
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
> - -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
> - -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
> - -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
> - -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
> - -Change of constraint type should re-render constraint component appropriately-
> - Constraint component should be rendered appropriately between two openings of Manage Types dialog
> - "Add Constraints" Tick/Untick shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3137:
--------------------------------
Description:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
- -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
- -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
- -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
- -Change of constraint type should re-render constraint component appropriately-
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
was:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;
- When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);
- When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);
- When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).
- Change of constraint type should re-render constraint component appropriately
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
> [DMN Designer] Data Types Type - Constraints - MVP component
> ------------------------------------------------------------
>
> Key: DROOLS-3137
> URL: https://issues.jboss.org/browse/DROOLS-3137
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
> - -When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;-
> - -When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);-
> - -When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);-
> - -When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).-
> - -Change of constraint type should re-render constraint component appropriately-
> - Constraint component should be rendered appropriately between two openings of Manage Types dialog
> - Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3137) [DMN Designer] Data Types Type - Constraints - MVP component
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3137?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3137:
--------------------------------
Description:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
- When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;
- When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);
- When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);
- When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).
- Change of constraint type should re-render constraint component appropriately
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
was:
- When the "Add Constraints" check box is selected, the Constraints component must be loaded;
- When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;
- When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);
- When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);
- When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).
- Change of constraint type should re-render constraint component appropriately
- Constraint component should be rendered appropriately between two openings of Manage Types dialog
- Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
> [DMN Designer] Data Types Type - Constraints - MVP component
> ------------------------------------------------------------
>
> Key: DROOLS-3137
> URL: https://issues.jboss.org/browse/DROOLS-3137
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> - When the "Add Constraints" check box is selected, the Constraints component must be loaded; (/)
> - When "None" is selected in the Constraints Component, no constraint must be set in the Data Type and no element should be loaded in the component;
> - When "Simple" is selected in the Constraints component, two fields (Min. and Max.) without any validation must be shown (the the Min. and Max. values must be set in the Data Type when the user clicks on save);
> - When "Expression" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save);
> - When "Enumeration" is selected in the Constraints Component, one field must be shown (the value must be set in the Data Type when user clicks on save).
> - Change of constraint type should re-render constraint component appropriately
> - Constraint component should be rendered appropriately between two openings of Manage Types dialog
> - Change of constraint component shouldn't throw warnings tho browser(Edge, Chrome, Firefox) console
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (JGRP-2307) Jgroup crashes when slf4j is used (Slf4jLogImpl)
by Daan Wendelen (Jira)
[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ]
Daan Wendelen updated JGRP-2307:
--------------------------------
Git Pull Request: https://github.com/belaban/JGroups/pull/404
> Jgroup crashes when slf4j is used (Slf4jLogImpl)
> ------------------------------------------------
>
> Key: JGRP-2307
> URL: https://issues.jboss.org/browse/JGRP-2307
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6, 4.0.15
> Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected
> - Only happens in docker (our image is based on "java:8")
> Reporter: Daan Wendelen
> Assignee: Bela Ban
> Priority: Major
> Attachments: jgroups-bug.zip
>
>
> When running our application, it crashes with the following stacktrace.
> {code}
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> Caused by: java.lang.ExceptionInInitializerError
> at Bug.main(Bug.java:5)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at java.util.Locale.<init>(Locale.java:648)
> at java.util.Locale.<init>(Locale.java:677)
> at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (JGRP-2307) Jgroup crashes when slf4j is used (Slf4jLogImpl)
by Daan Wendelen (Jira)
[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ]
Daan Wendelen commented on JGRP-2307:
-------------------------------------
Pull request: https://github.com/belaban/JGroups/pull/404
> Jgroup crashes when slf4j is used (Slf4jLogImpl)
> ------------------------------------------------
>
> Key: JGRP-2307
> URL: https://issues.jboss.org/browse/JGRP-2307
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6, 4.0.15
> Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected
> - Only happens in docker (our image is based on "java:8")
> Reporter: Daan Wendelen
> Assignee: Bela Ban
> Priority: Major
> Attachments: jgroups-bug.zip
>
>
> When running our application, it crashes with the following stacktrace.
> {code}
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> Caused by: java.lang.ExceptionInInitializerError
> at Bug.main(Bug.java:5)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at java.util.Locale.<init>(Locale.java:648)
> at java.util.Locale.<init>(Locale.java:677)
> at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (JGRP-2307) Jgroup crashes when slf4j is used (Slf4jLogImpl)
by Daan Wendelen (Jira)
[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ]
Daan Wendelen updated JGRP-2307:
--------------------------------
Summary: Jgroup crashes when slf4j is used (Slf4jLogImpl) (was: Jgroup crashes when slf4j is used)
> Jgroup crashes when slf4j is used (Slf4jLogImpl)
> ------------------------------------------------
>
> Key: JGRP-2307
> URL: https://issues.jboss.org/browse/JGRP-2307
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6, 4.0.15
> Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected
> - Only happens in docker (our image is based on "java:8")
> Reporter: Daan Wendelen
> Assignee: Bela Ban
> Priority: Major
> Attachments: jgroups-bug.zip
>
>
> When running our application, it crashes with the following stacktrace.
> {code}
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> Caused by: java.lang.ExceptionInInitializerError
> at Bug.main(Bug.java:5)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at java.util.Locale.<init>(Locale.java:648)
> at java.util.Locale.<init>(Locale.java:677)
> at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months