[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4257:
-----------------------------------
Sprint: 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 32-34)
> DMN UX - overlay information about an entire simulation execution
> -----------------------------------------------------------------
>
> Key: DROOLS-4257
> URL: https://issues.jboss.org/browse/DROOLS-4257
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Daniele Zonca
> Assignee: Margot Menestrot
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
>
> Related to https://issues.jboss.org/browse/DROOLS-3731
> This task will cover this use case:
> - user creates a DMN model
> - user creates a Test Scenario with some scenarios
> - user executes the Test Scenario
> - user open Coverage Report
> - user wants to analyze coverage information of {color:red}the *whole* simulation{color}
> - user clicks on "a link" near global coverage information
> - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3680) Explore HA CEP design and architecture
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3680?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3680:
-----------------------------------
Sprint: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34)
> Explore HA CEP design and architecture
> --------------------------------------
>
> Key: DROOLS-3680
> URL: https://issues.jboss.org/browse/DROOLS-3680
> Project: Drools
> Issue Type: Task
> Reporter: Mario Fusco
> Assignee: Massimiliano Dessi
> Priority: Major
> Labels: HADrools
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3953:
-----------------------------------
Sprint: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37 (was: 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34)
> DMN UX - overlay validation error reporting
> -------------------------------------------
>
> Key: DROOLS-3953
> URL: https://issues.jboss.org/browse/DROOLS-3953
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png
>
>
> As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
> I want to see this kind of errors in the decisions and at diagram level.
> * As a user I want to run a validation test within the DMN editor, using the Validate toolbar action, to be able to identify elements within the graph or grids that have errors, so that I can resolve the issues.
> * As a user when I save a file (and it is validated) I want to be informed if there are any validation errors, so that I'm aware that there are issues that need to be resolved.
> * As a user when I test a rule in the Scenario tool and any scenarios fail due to a syntax errors within DMN, I need to be able to easily identify the portions of the DMN file with errors so that I can fix them.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 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 updated WFLY-11328:
-----------------------------------
Component/s: Concurrency Utilities
(was: EE)
> 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
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> 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.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
As specified in the RFE, the server is reloaded after changes;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
> As specified in the RFE, the server is reloaded after changes;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4597) Intermittent failures deploying an application with Class-Path pointing to an external jar file
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFCORE-4597?page=com.atlassian.jira.plugi... ]
Yeray Borges reopened WFCORE-4597:
----------------------------------
The solution here was incorrect; using PhaseContext.getServiceTarget() we are changing the parent of the External Module Spec service created for the external module, making it dependent on the first deployment.
Under these circumstances, if we deploy two applications and remove later the first application deployed, we will be removing the External Module Spec service, which, in turns is required for the second deployment. An example of this error is the following message:
{noformat}
[standalone@localhost:9990 /] deploy web-app-classpath-1.0.war
[standalone@localhost:9990 /] deploy web-app-classpath-2.0.war
[standalone@localhost:9990 /] undeploy web-app-classpath-1.0.war
WFLYCTL0441: Operation has resulted in failed or missing services
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.module.spec.service."deployment.external./Users/ysantana/app-libs/echo-library-1-1.0.jar".main (missing) dependents: [service jboss.modu
le.resolve.phase."deployment.web-app-classpath-2.0.war".main.1]
service module.resolved.service."deployment.web-app-classpath-2.0.war".main (missing) dependents: [service jboss.module.service."deployment.web-app-cl
asspath-2.0.war".main]
WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed
{noformat}
We have to install the ExternalModuleSpecService out of the scope of the deployment, we can use EXTERNAL_SERVICE_TARGET deployment attachment for that purpose.
> Intermittent failures deploying an application with Class-Path pointing to an external jar file
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-4597
> URL: https://issues.jboss.org/browse/WFCORE-4597
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
> Fix For: 10.0.0.Beta4
>
> Attachments: reproducer-WFCORE-4597.zip
>
>
> The deployment of an application which is using an external library configured via Class-Path manifest attribute could fail with the following error:
> {noformat}
> 13:58:32,347 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ManagementRealm")
> ]) - failure description: "WFLYCTL0441: Operation has resulted in failed or missing services
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service module.resolved.service.\"deployment.web-app-classpath-1.0.war\".main (missing) dependents: [service jboss.module.service.\"deployment.web-app-classpath-1.0.war\".main]
> WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed"
> {noformat}
> Follow up the steps to reproduce
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months