January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9667) Change the Undertow subsystem to use io.undertow.server.DefaultByteBufferPool

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9667?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-9667: --------------------------------- Component/s: Web (Undertow) > Change the Undertow subsystem to use io.undertow.server.DefaultByteBufferPool > ----------------------------------------------------------------------------- > > Key: WFLY-9667 > URL: https://issues.jboss.org/browse/WFLY-9667 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9667) Change the Undertow subsystem to use io.undertow.server.DefaultByteBufferPool

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9667: ------------------------------------ Summary: Change the Undertow subsystem to use io.undertow.server.DefaultByteBufferPool Key: WFLY-9667 URL: https://issues.jboss.org/browse/WFLY-9667 Project: WildFly Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9666) ClassLoader leak in org.jboss.el.cache.FactoryFinderCache (Wildfly 11)

by Bruno Medeiros (JIRA)

Bruno Medeiros created WFLY-9666: ------------------------------------ Summary: ClassLoader leak in org.jboss.el.cache.FactoryFinderCache (Wildfly 11) Key: WFLY-9666 URL: https://issues.jboss.org/browse/WFLY-9666 Project: WildFly Issue Type: Bug Components: Class Loading Affects Versions: 11.0.0.Final Environment: macOS Reporter: Bruno Medeiros Assignee: David Lloyd Priority: Critical Attachments: Screen Shot 2018-01-14 at 19.32.10.png I was investigating why my class loader was leaking and after fixing all the problems within my application classes I got the leak shown in the attachment. !Screen Shot 2018-01-14 at 19.32.10.png|thumbnail! This is pretty similar with https://issues.jboss.org/browse/WFLY-3365, not sure if I should have reopened that one o raised this one, sorry if I took the wrong decision. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1735) Fetch KieSession from Kbase using session name

by Chandresh Mishra (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1735?page=com.atlassian.jira.plugi... ] Chandresh Mishra commented on DROOLS-1735: ------------------------------------------ [~mfusco] is there any update on this? > Fetch KieSession from Kbase using session name > ----------------------------------------------- > > Key: DROOLS-1735 > URL: https://issues.jboss.org/browse/DROOLS-1735 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.3.0.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > Labels: new_and_noteworthy, task > > KieSession kSession = kContainer.getKieBase("KiebaseName")).newKieSession(); > There is no method available in KieBase to get KieSession by passing the session name. > which is similar to get session from container > kSession = kContainer.newKieSession("SessionName"); > So , We can not choose a particular kieBase and KieSession at a same time by passing the name for both. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1759) Not able to load all the kieModule from classpath

by Chandresh Mishra (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1759?page=com.atlassian.jira.plugi... ] Chandresh Mishra commented on DROOLS-1759: ------------------------------------------ [~mfusco] is there any update on this issue? > Not able to load all the kieModule from classpath > --------------------------------------------------- > > Key: DROOLS-1759 > URL: https://issues.jboss.org/browse/DROOLS-1759 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final > Reporter: Chandresh Mishra > Assignee: Mario Fusco > > Hi , > I am trying to load a rules from classpath in gradle project. > It is a multi module gradle project.It has following structure. > Application > Application-rule > root > Application has compile project(':application-rule') in build.gradle. > application-rule has external dependency on common-rules . > Now when I am trying to load KieContainer from classpath in Application project. It is loading only kiebase in common-rules.jar .It is not loading kiebase in kmodule.xml present in Application-rule. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9665) HttpSession cannot be injected in distributed application

by Zoltan Laszlo Ferenci (JIRA)

Zoltan Laszlo Ferenci created WFLY-9665: ------------------------------------------- Summary: HttpSession cannot be injected in distributed application Key: WFLY-9665 URL: https://issues.jboss.org/browse/WFLY-9665 Project: WildFly Issue Type: Bug Components: CDI / Weld, EE Affects Versions: 10.1.0.Final Reporter: Zoltan Laszlo Ferenci Assignee: Martin Kouba Attachments: HttpSessionInjectionBug.zip The CDI Specification states that HttpSession should be available for injection. It also has statements about when should the bean passivation capable. The problem is that it seems the io.undertow.servlet.spec.HttpSessionImpl is not serializable, and whenever you try to inject, you get exception at passivation. I would say it's normal if it's injected into a passivating scoped bean, because the CDI specification says that the bean is passivation capable only if all it's dependencies is passivation capable. However this is the case even if it's injected in a RequestScoped bean, that shouldn't be passivated. In the sample project only the HttpSession should be passivated that is independent from the CDI. Anyway it gives an error in that case too, and doesn't store and recover the HttpSession. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1487) HTTP Digest SHA mechs missing in available mechanisms

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1487?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1487: ---------------------------- Component/s: HTTP > HTTP Digest SHA mechs missing in available mechanisms > ----------------------------------------------------- > > Key: ELY-1487 > URL: https://issues.jboss.org/browse/ELY-1487 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.2.0.Beta11 > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 1.2.0.Beta12 > > > DIGEST-SHA-256 and DIGEST-SHA-512-256 are not correctly registered: > When trying to deploy application using one of them for authentication: > {code} > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy DigestSha256MechTestCase.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./DigestSha256MechTestCase" => "java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory. > Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory. > Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory."}}}} > {code} > Problem is mechanisms are missing in output of {{ServerMechanismFactoryImpl.getMechanismNames()}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1487) HTTP Digest SHA mechs missing in available mechanisms

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1487?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1487: ---------------------------- Fix Version/s: 1.2.0.Beta12 > HTTP Digest SHA mechs missing in available mechanisms > ----------------------------------------------------- > > Key: ELY-1487 > URL: https://issues.jboss.org/browse/ELY-1487 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.0.Beta11 > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 1.2.0.Beta12 > > > DIGEST-SHA-256 and DIGEST-SHA-512-256 are not correctly registered: > When trying to deploy application using one of them for authentication: > {code} > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy DigestSha256MechTestCase.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./DigestSha256MechTestCase" => "java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory. > Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory. > Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory."}}}} > {code} > Problem is mechanisms are missing in output of {{ServerMechanismFactoryImpl.getMechanismNames()}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by John Ament (JIRA)

[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ] John Ament commented on WFLY-8488: ---------------------------------- [~rhusar] My original question about what the new configuration is for WF 11 wasn't really answered. Can you help? > Usage of JGroups JDBC_PING attempts to delete row too late > ---------------------------------------------------------- > > Key: WFLY-8488 > URL: https://issues.jboss.org/browse/WFLY-8488 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: John Ament > Assignee: Paul Ferraro > > I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. > In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by John Ament (JIRA)

[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ] John Ament reopened WFLY-8488: ------------------------------ > Usage of JGroups JDBC_PING attempts to delete row too late > ---------------------------------------------------------- > > Key: WFLY-8488 > URL: https://issues.jboss.org/browse/WFLY-8488 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: John Ament > Assignee: Paul Ferraro > > I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. > In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018