[JBoss JIRA] (WFWIP-268) Specifying empty list of constant-headers causes fatal error
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-268?page=com.atlassian.jira.plugin.... ]
Tomas Terem updated WFWIP-268:
------------------------------
Steps to Reproduce:
Execute the following cli commands:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[]}])
{code}
{code:java}
reload
{code}
was:
Execute the following command:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[]}])
{code}
> Specifying empty list of constant-headers causes fatal error
> ------------------------------------------------------------
>
> Key: WFWIP-268
> URL: https://issues.jboss.org/browse/WFWIP-268
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Specifying empty list of constant-headers causes fatal error.
> {code:java}
> 17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: "WFLYCTL0155: 'headers' may not be null"
> 17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-270) Configured headers can override headers added by the corresponding endpoint
by Tomas Terem (Jira)
[ https://issues.jboss.org/browse/WFWIP-270?page=com.atlassian.jira.plugin.... ]
Tomas Terem updated WFWIP-270:
------------------------------
Steps to Reproduce:
Execute the following cli commands:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=Connection, value=abc}, {name=Date, value=abcd}]}])
{code}
{code:java}
reload
{code}
And try:
{code:java}
curl -v http://localhost:9990/management
{code}
was:
Execute the following cli command:
{code:java}
/core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=Connection, value=abc}, {name=Date, value=abcd}]}])
{code}
And try:
{code:java}
curl -v http://localhost:9990/management
{code}
> Configured headers can override headers added by the corresponding endpoint
> ---------------------------------------------------------------------------
>
> Key: WFWIP-270
> URL: https://issues.jboss.org/browse/WFWIP-270
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> [Analysis document|https://github.com/wildfly/wildfly-proposals/pull/263] says that
> 'Configured headers will not override any headers added by the corresponding endpoint.'
> However, I was able to override Connection and Date headers on /management endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFCORE-4626) Expose ExternalModuleService as WildFly capability
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-4626?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-4626:
---------------------------------
Summary: Expose ExternalModuleService as WildFly capability (was: Expose ExternalModuleService as WidlFly capability)
> Expose ExternalModuleService as WildFly capability
> --------------------------------------------------
>
> Key: WFCORE-4626
> URL: https://issues.jboss.org/browse/WFCORE-4626
> Project: WildFly Core
> Issue Type: Task
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
>
> ExternalModuleService is used to create the ExternalModuleSpecService which exposes the ModuleDefinition for any external module dependency.
> Currently, ExternalModuleService is used via DUPs to scan the deployment and add external modules. We should expose this service via a Capability so it can be easily accessed via not only by the DUPs, but also other services that could require configure external modules.
> This capability should be registered in ServerService, see for example PathManager. It should be something that ExternalModuleService implements, the goal is not to expose the start/stop/getValue methods via the capability.
> See [this|https://github.com/wildfly/wildfly-core/pull/3890#issuecomment-52180...] as reference comment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-272) Specifying header name containing '\'n in constant-headers causes fatal error
by Tomas Terem (Jira)
Tomas Terem created WFWIP-272:
---------------------------------
Summary: Specifying header name containing '\'n in constant-headers causes fatal error
Key: WFWIP-272
URL: https://issues.jboss.org/browse/WFWIP-272
Project: WildFly WIP
Issue Type: Bug
Reporter: Tomas Terem
Assignee: Darran Lofthouse
Specifying header name containing '\'n in constant-headers causes fatal error:
{code:java}
10:02:36,853 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: WFLYSRV0083: Failed to start the http-interface service
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:393)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A
B
at io.undertow.util.HttpString.checkForNewlines(HttpString.java:126)
at io.undertow.util.HttpString.<init>(HttpString.java:120)
at io.undertow.util.HttpString.<init>(HttpString.java:103)
at org.jboss.as.domain.http.server.StaticHeadersHandler$HeaderConstant.<init>(StaticHeadersHandler.java:70)
at org.jboss.as.domain.http.server.StaticHeadersHandler.addHeader(StaticHeadersHandler.java:61)
at org.jboss.as.domain.http.server.ManagementHttpServer.setupOpenListener(ManagementHttpServer.java:369)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:279)
at org.jboss.as.domain.http.server.ManagementHttpServer.access$2600(ManagementHttpServer.java:111)
at org.jboss.as.domain.http.server.ManagementHttpServer$Builder.build(ManagementHttpServer.java:666)
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:351)
... 8 more
10:02:36,856 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "WFLYSRV0083: Failed to start the http-interface service
Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A
B"}}
10:02:36,856 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "WFLYSRV0083: Failed to start the http-interface service
Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A
B"}}
10:02:36,868 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
10:02:36,875 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 3ms
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
- Reorder columns
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> - Reorder columns
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-11328) EE Concurency Utilities "hung-task-threshold" / "long-running-tasks" do not work and are not implemented as explained
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11328?page=com.atlassian.jira.plugin... ]
Eduardo Martins commented on WFLY-11328:
----------------------------------------
[~bmaxwell][~brian.stansberry] EAP7-1397 created
> EE Concurency Utilities "hung-task-threshold" / "long-running-tasks" do not work and are not implemented as explained
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11328
> URL: https://issues.jboss.org/browse/WFLY-11328
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities, Documentation
> Reporter: Jiri Ondrusek
> Assignee: Eduardo Martins
> Priority: Major
>
> ee subsystem parameters "hung-task-threshold" and "long-running-tasks" for managed-executor-service / managed-scheduled-executor-service do not work and are not implemented as described in [EAP 7 Development Guide|https://access.redhat.com/documentation/en-us/red_hat_jboss_enterpr...]:
> - hung-task-threshold: Defines the time, in milliseconds, after which tasks are considered hung by the managed executor service and forcefully aborted. If the value is 0 (which is the default), tasks are never considered hung.
> - long-running-tasks: Suggests optimizing the execution of long running tasks, and defaults to false.
> I tested with [EAP 7 QuickStarts managed-executor-service example|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.0...] but these paremeters doe not take any effect:
> - tasks exceeding hung-task-threshold are never forcefully aborted. And there's no way to detect hung tasks exceeding hung-task-threshold.
> - setting long-running-tasks to true does not change the behavior.
> As far as I checked the source code, I noticed the following:
> - EAP 7.x uses the EE Concurency Utilities RI [org.glassfish.enterprise.concurrent|https://github.com/javaee/cu-ri] internally and just passes the paramters to the RI.
> - In the EE Concurency Utilities RI, these parameters are used in the methods [ManagedThreadFactoryImpl#isTaskHung(long now)|https://github.com/javaee/cu-ri/blob/master/src/main/java/org/glassf...], [AbstractManagedExecutorService#getHungThreads()|https://github.com/javaee...] and [AbstractManagedExecutorService#isLongRunningTasks()|https://github.com/ja...] (AbstractManagedExecutorService is the parent class of ManagedExecutorServiceImpl / ManagedScheduledExecutorServiceImpl).
> - However, these methods are never invoked from EAP 7.x. So, these parameters do not take any effect in EAP 7.x.
> - In addition, even if these methods are used, it looks the implementation is totally different from the description in the documentation. The parameter "long-running-tasks" is just used as a flag to skip from checking hung thread detection. And the parameter "hung-task-threshold" never forcefully abort the hung thread exceeding the threshold.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months