May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-199) Python Client Support Route Rule

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-199: ---------------------------------- Summary: Python Client Support Route Rule Key: SWSQE-199 URL: https://issues.jboss.org/browse/SWSQE-199 Project: Kiali QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1574) Test resources should be in directory structure by test package

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1574?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1574: ---------------------------------- Priority: Minor (was: Major) > Test resources should be in directory structure by test package > --------------------------------------------------------------- > > Key: ELY-1574 > URL: https://issues.jboss.org/browse/ELY-1574 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > A lot of elytron tests have their resources directly in src/test/resources directory, but they should be nested by package of the test - like src/test/resources/org/wildfly/security/ldap. > Shared resources like ca/ica should not be affected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10320) Upgrade artemis from 1.5.x to 2.x.x

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFLY-10320?page=com.atlassian.jira.plugin... ] Martyn Taylor moved WFWIP-29 to WFLY-10320: ------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-10320 (was: WFWIP-29) Component/s: JMS (was: Artemis) (was: JMS) Target Release: (was: 7.2.0.GA) > Upgrade artemis from 1.5.x to 2.x.x > ----------------------------------- > > Key: WFLY-10320 > URL: https://issues.jboss.org/browse/WFLY-10320 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: feature-branch-blocker > > As the summary of this Jira hints, this is an umbrella Jira for tracking all issues related to the upgrade of Artemis component from version 1.x to 2.x. > The issues were identified after running tests against following pull request - https://github.com/wildfly/wildfly/pull/10641 > This PR integrates Artemis 2.4.0 in WildFly master branch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1574) Test resources should be in directory structure by test package

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1574?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1574: --------------------------------------- Dropping the priority a little as this will make porting between branches harder. > Test resources should be in directory structure by test package > --------------------------------------------------------------- > > Key: ELY-1574 > URL: https://issues.jboss.org/browse/ELY-1574 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > A lot of elytron tests have their resources directly in src/test/resources directory, but they should be nested by package of the test - like src/test/resources/org/wildfly/security/ldap. > Shared resources like ca/ica should not be affected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10139) Upgrade ActiveMQ Artemis to 1.5.5-011

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10139?page=com.atlassian.jira.plugin... ] Jeff Mesnil reassigned WFLY-10139: ---------------------------------- Assignee: Jeff Mesnil > Upgrade ActiveMQ Artemis to 1.5.5-011 > ------------------------------------- > > Key: WFLY-10139 > URL: https://issues.jboss.org/browse/WFLY-10139 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Lin Gao > Assignee: Jeff Mesnil > > https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10139) Upgrade ActiveMQ Artemis to 1.5.5-011

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10139?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10139: ------------------------------- Component/s: JMS > Upgrade ActiveMQ Artemis to 1.5.5-011 > ------------------------------------- > > Key: WFLY-10139 > URL: https://issues.jboss.org/browse/WFLY-10139 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Lin Gao > Assignee: Jeff Mesnil > > https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10319) NameBinding annotations on resources are ignored in subresources

by Javier Estevez Sanchez (JIRA)

Javier Estevez Sanchez created WFLY-10319: --------------------------------------------- Summary: NameBinding annotations on resources are ignored in subresources Key: WFLY-10319 URL: https://issues.jboss.org/browse/WFLY-10319 Project: WildFly Issue Type: Bug Affects Versions: 12.0.0.Final Reporter: Javier Estevez Sanchez Assignee: Jason Greene The following JAX-RS resource exposes two resources via a GET operation: /demo and /demo/subresource. The first one via a sub-resource method, the latter via a sub-resource locator. Additionally, a response filter is binded to the JAX-RS resource class to modify the response. From the JAX-RS 2.0 spec, §6.5.2 Name Binding: {quote} Binding annotations that decorate resource classes apply to all resource methods defined in them. {quote} However, the binding annotation is not applying to the sub-resource locator method. This happens when the name binding annotation is on the resource class or on the sub-resource locator method. Annotating the sub-resource class or the method within works as expected, though. Below is the code needed to reproduce this issue: {code:java|title=The resource and subresource} @DemoNameBinding @Produces(MediaType.APPLICATION_JSON) @Path("/demo") public class DemoResource { @GET public String getDemoValue() { return "A value"; } @Path("/subresource") public DemoSubResource getSubResource() { return new DemoSubResource(); } public class DemoSubResource { @GET public String getDemoValue() { return "A value"; } } } {code} {code:java|title=The filter} @Provider @DemoNameBinding public class SomeFilter implements ContainerResponseFilter { @Override public void filter(ContainerRequestContext requestContext, ContainerResponseContext responseContext) { responseContext.setEntity("A filtered value"); } } {code} {code:java|title=The binding} @NameBinding @Target({ElementType.TYPE, ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) public @interface DemoNameBinding { } {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1199) Memory leak in KieScanner

by Joni Niemi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1199?page=com.atlassian.jira.plugi... ] Joni Niemi commented on DROOLS-1199: ------------------------------------ > Is this issue fixed in version 6.5.0.Final? No. > Memory leak in KieScanner > ------------------------- > > Key: DROOLS-1199 > URL: https://issues.jboss.org/browse/DROOLS-1199 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Viacheslav Krot > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > I'm not sure, but it seems there is a memory leak in KieScanner, not in scanner directly, but somewhere in plexus used internally. > If you start KieScanner with version = LATEST, start it with interval say 1 second and sample memory with visualvm (or any other), you can watch number of instances org.eclipse.sisu.plexus.* growing over time. And they cannot be garbage collected - memory root is timer thread. This happens in drools 6.4.0, in 6.3.0 this issue was absent. > Eventually application fails with OOM. > As a workaround we call KieScanner#scan manually in a separate thread pool that is recreated from time to time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3795) Read Feature Description doesn't return ObjectAttributeDefinition capabilities

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3795?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3795: ------------------------------------------ When fixing this please check lists and maps containing ObjectAttributeDefinition (i.e. ObjectListAttributeDefinition and ObjectMapAttributeDefinition.) > Read Feature Description doesn't return ObjectAttributeDefinition capabilities > ------------------------------------------------------------------------------ > > Key: WFCORE-3795 > URL: https://issues.jboss.org/browse/WFCORE-3795 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Alpha4 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > ObjectAttributeDefinition are described as features but their required capabilities are not displayed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10318) Use Galleon to build WildFly full distributions

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-10318?page=com.atlassian.jira.plugin... ] Alexey Loubyansky updated WFLY-10318: ------------------------------------- Summary: Use Galleon to build WildFly full distributions (was: Use Galleon to build Wild full distributions) > Use Galleon to build WildFly full distributions > ----------------------------------------------- > > Key: WFLY-10318 > URL: https://issues.jboss.org/browse/WFLY-10318 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Switch from the current feature-pack-based provisioning to Galleon and WildFly Galleon plugins. > Create galleon feature packs as Maven artifacts and use them to produce the thin and fat servlet, full and other testsuite distributions. > The legacy servlet and full feature-packs should still be built. They could still be used to produce the legacy builds and distributions by activating Maven profiles. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018