August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2929) Cannot compile the executable model from inside JBoss EAP

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2929: ----------------------------------- Summary: Cannot compile the executable model from inside JBoss EAP Key: DROOLS-2929 URL: https://issues.jboss.org/browse/DROOLS-2929 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2916) UX design for the contextual menus

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2916?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2916: -------------------------------- Attachment: menu1.png menu2.png menu3.png > UX design for the contextual menus > ---------------------------------- > > Key: DROOLS-2916 > URL: https://issues.jboss.org/browse/DROOLS-2916 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Screen Shot 2018-08-23 at 12.34.13 PM.png, menu1.png, menu2.png, menu3.png > > > Provide the labels for the different contextual menus retrieved on right clicking the grid: > 1) click on a "header" cell > 2) click on the first cell of a row > 3) click on any other cell of a row -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2916) UX design for the contextual menus

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2916?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2916: ------------------------------------- [~danielezonca] Posted some mockups. Includes menu for Index description menu, that only offers row related actions. Question: Do we need the Template index and description columns? Or could we use those in future for the Background or etc.? !menu1.png|thumbnail! !menu2.png|thumbnail! !menu3.png|thumbnail! > UX design for the contextual menus > ---------------------------------- > > Key: DROOLS-2916 > URL: https://issues.jboss.org/browse/DROOLS-2916 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: Screen Shot 2018-08-23 at 12.34.13 PM.png, menu1.png, menu2.png, menu3.png > > > Provide the labels for the different contextual menus retrieved on right clicking the grid: > 1) click on a "header" cell > 2) click on the first cell of a row > 3) click on any other cell of a row -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10784) WeldStartCompletionService failed when optional components not installed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10784: ----------------------------------------- I don't know about the DeploymentPhaseContext.getServiceRegistry().getService(WeldBootstrapService.SERVICE_NAME) returning null thing; that seems odd. > WeldStartCompletionService failed when optional components not installed > ------------------------------------------------------------------------ > > Key: WFLY-10784 > URL: https://issues.jboss.org/browse/WFLY-10784 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 12.0.0.Final, 13.0.0.Final > Reporter: Alexander Kudrevatykh > Assignee: Matej Novotny > Attachments: arq-test.tar.xz > > > WebComponents are optional and fail in initialising it not causes fail of deployment, but when starting EAR application with included WAR fail in deployment since Wildfly 12 because WeldStartCompletionService depends on all components regardless of their type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10784) WeldStartCompletionService failed when optional components not installed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10784: ----------------------------------------- [~manovotn] Another approach you can use is DeploymentUnit.putAttachment. That allows DUPs to pass data to each other via the DeploymentUnit. So WeldSubsystemAdd could attach the WeldBootstrapService. Passing services that way feels vaguely yucky, but no more so than doing DeploymentPhaseContext.getServiceRegistry().getService(WeldBootstrapService.SERVICE_NAME). > WeldStartCompletionService failed when optional components not installed > ------------------------------------------------------------------------ > > Key: WFLY-10784 > URL: https://issues.jboss.org/browse/WFLY-10784 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 12.0.0.Final, 13.0.0.Final > Reporter: Alexander Kudrevatykh > Assignee: Matej Novotny > Attachments: arq-test.tar.xz > > > WebComponents are optional and fail in initialising it not causes fail of deployment, but when starting EAR application with included WAR fail in deployment since Wildfly 12 because WeldStartCompletionService depends on all components regardless of their type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3039) Capability requirement can be lost if two attributes on same resource reference the same capability

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3039?page=com.atlassian.jira.plugi... ] Radovan Netuka reassigned WFCORE-3039: -------------------------------------- Assignee: (was: Radovan Netuka) > Capability requirement can be lost if two attributes on same resource reference the same capability > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-3039 > URL: https://issues.jboss.org/browse/WFCORE-3039 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Darran Lofthouse > > With the following three commands the server becomes unable to boot due to a missing dependency: - > {noformat} > /subsystem=elytron:write-attribute(name=initial-providers, value=combined-providers) > /subsystem=elytron:undefine-attribute(name=final-providers) > /subsystem=elytron/aggregate-providers=combined-providers:remove > {noformat} > If however I execute :reload after the first two commands, the final command will fail correctly. > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/aggregate-providers=combined-providers:remove > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0367: Cannot remove capability 'org.wildfly.security.providers.combined-providers' as it is required by other capabilities: > capability 'org.wildfly.security.elytron' requires it for attribute 'initial-providers' at address '/subsystem=elytron'", > "rolled-back" => true > } > {noformat} > I am only listing the 'Domain Management' component as I believe the security example is just the reproducer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10784) WeldStartCompletionService failed when optional components not installed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10784: ----------------------------------------- [~manovotn] Ignore the deprecation. MSC has new API that it wanted people to use, so it deprecated the old one. But almost nothing in WildFly uses that new API, and it's not a no-thought activity to switch chunk of functionality to it; things can break when partial conversions are done. IMHO that deprecation was premature as it just scares people. That said, I'm not sure you need to do DeploymentPhaseContext.getServiceRegistry().getService(WeldBootstrapService.SERVICE_NAME). Perhaps you could just retain WeldStartCompletionService and have it depend on / inject WeldBootstrapService. But the stuff from L296-299 at https://github.com/wildfly/wildfly/pull/10795/files#diff-5437e2864026abc7... isn't necessary. In my last comment I didn't mean to imply WeldStartCompletionService shouldn't depend on anything; just that it didn't need to depend on the services that are causing this issue. > WeldStartCompletionService failed when optional components not installed > ------------------------------------------------------------------------ > > Key: WFLY-10784 > URL: https://issues.jboss.org/browse/WFLY-10784 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 12.0.0.Final, 13.0.0.Final > Reporter: Alexander Kudrevatykh > Assignee: Matej Novotny > Attachments: arq-test.tar.xz > > > WebComponents are optional and fail in initialising it not causes fail of deployment, but when starting EAR application with included WAR fail in deployment since Wildfly 12 because WeldStartCompletionService depends on all components regardless of their type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10923) Server stop blocked by DistributableSessionManager after invalidation during async request

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10923?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10923: -------------------------------- Summary: Server stop blocked by DistributableSessionManager after invalidation during async request (was: Server stop indefinitely blocked by DistributableSessionManager after invalidation during async request) > Server stop blocked by DistributableSessionManager after invalidation during async request > ------------------------------------------------------------------------------------------ > > Key: WFLY-10923 > URL: https://issues.jboss.org/browse/WFLY-10923 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Beta2 > Reporter: Aaron Ogburn > Assignee: Paul Ferraro > Attachments: servlet-async.war > > > After WFLY-10621, a DistributableSessionManager.stop hang can still occur in the following scenario. > 1. async request a starts > 2. sync request b invalidates session > 3. async request a completes > Upon completion, the async request does not unlock and throws following exception: > {code} > 16:04:58,260 ERROR [stderr] (default task-18) Exception in thread "default task-18" java.lang.RuntimeException: java.lang.IllegalStateException: WFLYCLWEBUT0001: Session 8adSKXK1li8Qo15QnaIGrd31DrB6B83jEL4blzq1 is invalid > 16:04:58,260 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.ServletContextImpl.invokeRunnable(ServletContextImpl.java:944) > 16:04:58,260 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl.onAsyncComplete(AsyncContextImpl.java:594) > 16:04:58,260 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl.access$100(AsyncContextImpl.java:71) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl$3.run(AsyncContextImpl.java:315) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl$6.run(AsyncContextImpl.java:473) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl$TaskDispatchRunnable.run(AsyncContextImpl.java:584) > 16:04:58,261 ERROR [stderr] (default task-18) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 16:04:58,261 ERROR [stderr] (default task-18) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 16:04:58,261 ERROR [stderr] (default task-18) at java.lang.Thread.run(Thread.java:748) > 16:04:58,261 ERROR [stderr] (default task-18) Caused by: java.lang.IllegalStateException: WFLYCLWEBUT0001: Session 8adSKXK1li8Qo15QnaIGrd31DrB6B83jEL4blzq1 is invalid > 16:04:58,261 ERROR [stderr] (default task-18) at org.wildfly.clustering.web.undertow.session.DistributableSession.validate(DistributableSession.java:57) > 16:04:58,261 ERROR [stderr] (default task-18) at org.wildfly.clustering.web.undertow.session.DistributableSession.getAttribute(DistributableSession.java:157) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:122) > 16:04:58,261 ERROR [stderr] (default task-18) at org.jboss.weld.context.http.HttpSessionContextImpl.checkBeanIdentifierIndexConsistency(HttpSessionContextImpl.java:98) > 16:04:58,261 ERROR [stderr] (default task-18) at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:47) > 16:04:58,261 ERROR [stderr] (default task-18) at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:23) > 16:04:58,261 ERROR [stderr] (default task-18) at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:237) > 16:04:58,261 ERROR [stderr] (default task-18) at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:152) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.core.ApplicationListeners.requestInitialized(ApplicationListeners.java:246) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl.setupRequestContext(AsyncContextImpl.java:678) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl.access$700(AsyncContextImpl.java:71) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.AsyncContextImpl$7.run(AsyncContextImpl.java:599) > 16:04:58,261 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.ServletContextImpl$2.call(ServletContextImpl.java:177) > 16:04:58,262 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.ServletContextImpl$2.call(ServletContextImpl.java:174) > 16:04:58,262 ERROR [stderr] (default task-18) at io.undertow.servlet.spec.ServletContextImpl.invokeRunnable(ServletContextImpl.java:942) > 16:04:58,262 ERROR [stderr] (default task-18) ... 8 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends

by Edoardo Vacchi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-2924: ----------------------------------- Story Points: 5 > Factor out Unit behavior to allow pluggable backends > ---------------------------------------------------- > > Key: DROOLS-2924 > URL: https://issues.jboss.org/browse/DROOLS-2924 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Labels: Stunner > > e.g.: > - rule units (Drools) > - process units (jBPM) > etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2901) Implement a recursive expression builder component

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2901?page=com.atlassian.jira.plugi... ] Gabriele Cardosi resolved DROOLS-2901. -------------------------------------- Resolution: Done > Implement a recursive expression builder component > --------------------------------------------------- > > Key: DROOLS-2901 > URL: https://issues.jboss.org/browse/DROOLS-2901 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > > Add logic/behaviour to the static expression builder component: > 1. Support infinite number of nested levels > 2. Load data from DMO -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018