October 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5726) drools-traits module exports the wrong OSGi package in the bundle

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5726: ------------------------------------ Summary: drools-traits module exports the wrong OSGi package in the bundle Key: DROOLS-5726 URL: https://issues.redhat.com/browse/DROOLS-5726 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni should be `org.drools.traits.core` -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5725) kie-plugins-testing in droolsjbpm-integration try to resolve a 1.0.0 version of kie

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5725: ------------------------------------ Summary: kie-plugins-testing in droolsjbpm-integration try to resolve a 1.0.0 version of kie Key: DROOLS-5725 URL: https://issues.redhat.com/browse/DROOLS-5725 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni And fails after a timeout. This doesn't affect the test correctness, but it slows the build. Check also the other integration tests -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1217) Fault Injection in Service Actions

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1217?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1217: ------------------------------------- Assignee: Hayk Hovsepyan > Fault Injection in Service Actions > ---------------------------------- > > Key: SWSQE-1217 > URL: https://issues.redhat.com/browse/SWSQE-1217 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1913 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1217) Fault Injection in Service Actions

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1217?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1217: ---------------------------------- Sprint: Kiali Sprint #47 > Fault Injection in Service Actions > ---------------------------------- > > Key: SWSQE-1217 > URL: https://issues.redhat.com/browse/SWSQE-1217 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1913 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13968) Consider internal jaxb-impl module in more situations

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created WFLY-13968: ---------------------------------------------- Summary: Consider internal jaxb-impl module in more situations Key: WFLY-13968 URL: https://issues.redhat.com/browse/WFLY-13968 Project: WildFly Issue Type: Bug Components: XML Frameworks Affects Versions: 21.0.0.Final Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero Attachments: jaxb-exclusion.zip Currently the [ContextFinder.java|https://github.com/jboss/jboss-jaxb-api_spec/blob/mast...] also looks for the jaxb factories inside the module impl in two situations (to search factory JAXBContextFactory and old JAXBContext using the services). But it does not do the same when using the factory specified in a system property or inside a {{jaxb.properties}} file. The idea is making this uniform and do always the same (searching in the TCCL and then, if not found, inside the internal module impl for each specification step). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13968) Consider internal jaxb-impl module in more situations

by Ricardo Martin Camarero (Jira)

[ https://issues.redhat.com/browse/WFLY-13968?page=com.atlassian.jira.plugi... ] Ricardo Martin Camarero updated WFLY-13968: ------------------------------------------- Attachment: jaxb-exclusion.zip > Consider internal jaxb-impl module in more situations > ----------------------------------------------------- > > Key: WFLY-13968 > URL: https://issues.redhat.com/browse/WFLY-13968 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Affects Versions: 21.0.0.Final > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Attachments: jaxb-exclusion.zip > > > Currently the [ContextFinder.java|https://github.com/jboss/jboss-jaxb-api_spec/blob/mast...] also looks for the jaxb factories inside the module impl in two situations (to search factory JAXBContextFactory and old JAXBContext using the services). But it does not do the same when using the factory specified in a system property or inside a {{jaxb.properties}} file. The idea is making this uniform and do always the same (searching in the TCCL and then, if not found, inside the internal module impl for each specification step). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13941) Failed to persist session attribute with Websocket endpoints

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-13941?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-13941: ------------------------------------- [~flavia.rainone] are you working on this issue? > Failed to persist session attribute with Websocket endpoints > ------------------------------------------------------------ > > Key: WFLY-13941 > URL: https://issues.redhat.com/browse/WFLY-13941 > Project: WildFly > Issue Type: Bug > Components: Web Sockets > Affects Versions: 13.0.0.Final > Reporter: Abi Sarwan > Assignee: Flavia Rainone > Priority: Major > Attachments: mavenproject1-1.0.war > > > When WildFly is configured to persist sessions (standalone mode) during restart/redeploy and contains a websocket endpoint, a NotSerializableException is thrown: > Failed to persist session attribute io.undertow.websocket.current-connections with value [WebSocket13Channel peer /127.0.0.1:64853 local /127.0.0.1:8080[ No Receiver [] -- [] -- []]] for session xxxxxxxx: java.io.NotSerializableException: io.undertow.websockets.core.protocol.version13.WebSocket13Channel > > This start to happen in wildfly 13. The deployment works fine in wildfly 12. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (AG-149) Fix unstable test 'FlushTests#modeLeak'

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-149?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro closed AG-149. ---------------------------- > Fix unstable test 'FlushTests#modeLeak' > --------------------------------------- > > Key: AG-149 > URL: https://issues.redhat.com/browse/AG-149 > Project: Agroal > Issue Type: Bug > Components: test > Affects Versions: 1.8 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 1.9 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (AG-151) Turn on signature check on agroal-api module

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-151?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro closed AG-151. ---------------------------- > Turn on signature check on agroal-api module > -------------------------------------------- > > Key: AG-151 > URL: https://issues.redhat.com/browse/AG-151 > Project: Agroal > Issue Type: Task > Components: api, build > Affects Versions: 1.8 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.9 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (AG-143) Add s flush mode to forcefully remove leaked connections

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-143?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro closed AG-143. ---------------------------- > Add s flush mode to forcefully remove leaked connections > -------------------------------------------------------- > > Key: AG-143 > URL: https://issues.redhat.com/browse/AG-143 > Project: Agroal > Issue Type: Bug > Components: api, pool > Affects Versions: 1.8 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.9 > > > When there is a notification of a leaking connection there is no way to remove that connection from the pool. In the event of uncommon connection leaks, these will accumulate over time, eventually blocking the pool. Using the existing mechanism for flush operations, add a new mode to allow the removal of these connections. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 October 2020