[JBoss JIRA] (WFLY-13118) Delete any existing licenses.html before transforming to create a new one
by Ingo Weiss (Jira)
Ingo Weiss created WFLY-13118:
---------------------------------
Summary: Delete any existing licenses.html before transforming to create a new one
Key: WFLY-13118
URL: https://issues.redhat.com/browse/WFLY-13118
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Ingo Weiss
Assignee: Brian Stansberry
Fix For: 19.0.0.Beta1
If the transform task in the tasks.xml from the docs.licenses.merge galleon package from more than one f-p gets executed it will fail because the first task to run will create a licenses.html and 'transform' will fail if the target file already exists. So as a safety measure have the tasks delete any such file before doing the transform.
AIUI a fix for GAL-305 will remove the need for this by preventing more than one docs.licenses.merge package being provisioned, but having this in there will do no harm and makes things a bit more robust.
Also, remove the crufty 'alternative-tasks.xml' files from these docs.licenses.merge packages.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13115) MP Fault tolerance tests are failing on Ubuntu
by Ingo Weiss (Jira)
Ingo Weiss created WFLY-13115:
---------------------------------
Summary: MP Fault tolerance tests are failing on Ubuntu
Key: WFLY-13115
URL: https://issues.redhat.com/browse/WFLY-13115
Project: WildFly
Issue Type: Bug
Components: MP Fault Tolerance, Test Suite
Affects Versions: No Release
Reporter: Ingo Weiss
Assignee: Emmanuel Hugonnet
Fix For: 19.0.0.Beta1
Environment variables with dots in their name are not supported on Ubuntu making the fault tolerance tests fail.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5073) menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5073?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-5073:
-----------------------------------
Affects Version/s: (was: 7.33.0.Final)
> menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5073
> URL: https://issues.redhat.com/browse/DROOLS-5073
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.19.0.Final
> Reporter: xiaodong zhang
> Assignee: Michael Anstis
> Priority: Major
> Fix For: 7.33.0.Final
>
> Attachments: maycolumns.dmn
>
>
> Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18).
> This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 25。
> But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
> So I guess this a a performance issue, when shortage of the hardware resource, the UI will refreshed when right click the cell and caused the right-click menu gone.
> Please help to check this . Thanks a lot !
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13065) Options for reverse-proxy max-request-time and connection-idle-timeout are specified as seconds
by Ricardo Martin Camarero (Jira)
[ https://issues.redhat.com/browse/WFLY-13065?page=com.atlassian.jira.plugi... ]
Ricardo Martin Camarero updated WFLY-13065:
-------------------------------------------
Workaround Description:
Just set both options in millis (for example 60000 to set 60 seconds for {{max-request-time}}).
{noformat}
/subsystem=undertow/configuration=handler/reverse-proxy=LBProxy:write-attribute(name=max-request-time, value=60000)
{noformat}
Workaround: Workaround Exists
> Options for reverse-proxy max-request-time and connection-idle-timeout are specified as seconds
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-13065
> URL: https://issues.redhat.com/browse/WFLY-13065
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 19.0.0.Beta1
> Reporter: Ricardo Martin Camarero
> Assignee: Ricardo Martin Camarero
> Priority: Minor
>
> In the reverse-proxy configuration the options {{max-request-time}} and {{connection-idle-timeout}} are specified and managed as seconds in CLI, when they are really milliseconds in undertow.
> {noformat}
> /subsystem=undertow/configuration=handler/reverse-proxy=LBProxy:read-resource-description
> ...
> "connection-idle-timeout" => {
> "type" => INT,
> "description" => "The amount of time a connection can be idle before it will be closed. Connections will not time out
> once the pool size is down to the configured minimum (as configured by cached-connections-per-thread)",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => 60L,
> "unit" => "SECONDS",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...
> "max-request-time" => {
> "type" => INT,
> "description" => "The maximum time that a proxy request can be active for, before being killed",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => -1,
> "unit" => "SECONDS",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> ...
> {noformat}
> The class [ReverseProxyHandler|https://github.com/wildfly/wildfly/blob/master/undert...] just passes the value (no modification) to undertow and it's clearly millis in undertow, for example the [max-request-time|https://github.com/undertow-io/undertow/blob/master/core...].
> I has suffered this confusion myself doing some tests, I set 60 as the max request time, and it was too short in my env (because they are millis instead of seconds).
> We need to change description to millis to respect current configurations.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5073) menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5073?page=com.atlassian.jira.plug... ]
Michael Anstis commented on DROOLS-5073:
----------------------------------------
JIRA linked. I tested the attached file with 7.33.0.Final and the menus work fine.
> menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5073
> URL: https://issues.redhat.com/browse/DROOLS-5073
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.19.0.Final, 7.33.0.Final
> Reporter: xiaodong zhang
> Assignee: Michael Anstis
> Priority: Major
> Attachments: maycolumns.dmn
>
>
> Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18).
> This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 25。
> But this isn't happend on my new windows machine(i7 9th , GTX1660ti)
> So I guess this a a performance issue, when shortage of the hardware resource, the UI will refreshed when right click the cell and caused the right-click menu gone.
> Please help to check this . Thanks a lot !
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13113) Create 'microprofile' integration test module
by Ingo Weiss (Jira)
Ingo Weiss created WFLY-13113:
---------------------------------
Summary: Create 'microprofile' integration test module
Key: WFLY-13113
URL: https://issues.redhat.com/browse/WFLY-13113
Project: WildFly
Issue Type: Task
Components: MP Config, MP Fault Tolerance, MP Health, MP Metrics, MP OpenAPI, MP OpenTracing
Reporter: Ingo Weiss
Assignee: Radoslav Husar
Fix For: 19.0.0.Beta1
We need a place where to stick microprofile integration tests which run against a server provisioned with all microprofile integration modules. Moreover, since these modules are not in the default server configuration, we will use galleon to provision the server with fault-tolerance, jwt, openapi, etc galleon layers.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months