April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11829) Support messaging clusters (Artemis Clusters) behind http load balancers.

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11829?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet updated WFLY-11829: ------------------------------------- Labels: CD17 (was: ) > Support messaging clusters (Artemis Clusters) behind http load balancers. > ------------------------------------------------------------------------- > > Key: WFLY-11829 > URL: https://issues.jboss.org/browse/WFLY-11829 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 16.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Labels: CD17 > > Support EAP messaging clusters (Artemis Clusters) behind http load balancers. > by disabling automatic topology updates on clients. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Mario Fusco reopened DROOLS-1540: --------------------------------- > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1540: -------------------------------- Affects Version/s: 7.20.0.Final > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1540: -------------------------------- Sprint: 2019 Week 20-22 > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3950) Add drl example to Summit demo app

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3950?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3950: -------------------------------- Story Points: 2 > Add drl example to Summit demo app > ---------------------------------- > > Key: DROOLS-3950 > URL: https://issues.jboss.org/browse/DROOLS-3950 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3884) Prepare a Drools on Quarkus presentation

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3884?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-3884. --------------------------------- Resolution: Done > Prepare a Drools on Quarkus presentation > ---------------------------------------- > > Key: DROOLS-3884 > URL: https://issues.jboss.org/browse/DROOLS-3884 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3950) Add drl example to Summit demo app

by Mario Fusco (Jira)

Mario Fusco created DROOLS-3950: ----------------------------------- Summary: Add drl example to Summit demo app Key: DROOLS-3950 URL: https://issues.jboss.org/browse/DROOLS-3950 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10813) OutOfMemory error when trying to display resource adapters in web console

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-10813?page=com.atlassian.jira.plugin... ] Harald Pehl commented on WFLY-10813: ------------------------------------ [~obludik] Are there any updates? > OutOfMemory error when trying to display resource adapters in web console > ------------------------------------------------------------------------- > > Key: WFLY-10813 > URL: https://issues.jboss.org/browse/WFLY-10813 > Project: WildFly > Issue Type: Bug > Components: Management, Web Console > Affects Versions: 10.0.0.Final, 13.0.0.Final > Reporter: Helena Knyttlová > Assignee: Harald Pehl > Priority: Minor > Attachments: standalone-full-ha.xml > > > We have about 25 resource adapters set through CLI. When I want to display them in web administration console it kills the whole wildfly server - server is not responding and after several minutes it ends up with OutOfMemory error and server must be restarted. We've seen this issue since wildfly 10 (it was the first version we used). With only a few resource adapters it is not happening. > Memory settings: JAVA_OPTS="-Xms512m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > The error which appeared on WidlFly 13.0.0.Final: > {panel:title=Log} > ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("read-resource-description") failed - address: ([ > ("subsystem" => "resource-adapters"), > ("resource-adapter" => "AppAdapter"), > ("connection-definitions" => "cp-host") > ]): java.lang.OutOfMemoryError: Java heap space > at java.util.HashMap.resize(HashMap.java:704) > at java.util.HashMap.putVal(HashMap.java:629) > at java.util.HashMap.put(HashMap.java:612) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.clone(ModelNode.java:1867) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:180) > at org.jboss.dmr.ObjectModelValue.copy(ObjectModelValue.java:169) > at org.jboss.dmr.ModelNode.set(ModelNode.java:693) > at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler$ReadResourceDescriptionAssemblyHandler.execute(ReadResourceDescriptionHandler.java:618) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1404) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.jboss.as.controller.ModelControllerImpl$$Lambda$490/414756260.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$491/367363594.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$790/1228674018.run(Unknown Source) > {panel} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11846) Deployment classloader leak on EE Concurrency managed threads

by Martin Perina (Jira)

[ https://issues.jboss.org/browse/WFLY-11846?page=com.atlassian.jira.plugin... ] Martin Perina commented on WFLY-11846: -------------------------------------- [~dfediuck] > Deployment classloader leak on EE Concurrency managed threads > ------------------------------------------------------------- > > Key: WFLY-11846 > URL: https://issues.jboss.org/browse/WFLY-11846 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 16.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Critical > Fix For: 17.0.0.Beta1 > > Attachments: Screenshot 2019-03-13 at 20.21.19.png > > > A followup to WFLY-11678, managed threads have another deployment CL leak, which happens due to parent thread having a reference to it in its AccessControlContext. When a thread is created it inherits parent's AccessControlContext. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6143) Global EJB Server Side Interceptors Configuration

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-6143?page=com.atlassian.jira.plugin.... ] Tomasz Adamski edited comment on WFLY-6143 at 4/29/19 11:48 AM: ---------------------------------------------------------------- @HaraldPehl the draft is ready. I will open PR today. This would require reviews but I hope the management model will stay unchanged. was (Author: tomekadamski): @HaraldPehl the draft is ready. I will open PR today. This would require reviews but I hope the management model will stay. > Global EJB Server Side Interceptors Configuration > ------------------------------------------------- > > Key: WFLY-6143 > URL: https://issues.jboss.org/browse/WFLY-6143 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > > Ability to configure global server side interceptors (container interceptors) and specify their order via the JBoss profile xml. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019