April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-87) Remove Postgres installation from Hawkular Services Installation

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-87: ---------------------------------------- Summary: Remove Postgres installation from Hawkular Services Installation Key: HAWKULARQE-87 URL: https://issues.jboss.org/browse/HAWKULARQE-87 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Michael Foley In Foreman Hostgroups and Scripts which installs Hawkular Services, from ZIP or docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-86) Adjust REST API Client in MgmtSystem

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-86: ---------------------------------------- Summary: Adjust REST API Client in MgmtSystem Key: HAWKULARQE-86 URL: https://issues.jboss.org/browse/HAWKULARQE-86 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Move all Hawkular Inventory REST API calls into Hawkular Metrics. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-85) Inventory goes into Metrics

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-85: ---------------------------------------- Summary: Inventory goes into Metrics Key: HAWKULARQE-85 URL: https://issues.jboss.org/browse/HAWKULARQE-85 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Hawkular Inventory will not exist anymore, it will be moved into Hawkular Metrics. So Hawkular Services will not contain Inventory anymore. Action items are in subtasks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8579) Topic messages are sent to all shared non-durable subscription participants

by Scott Van Wart (JIRA)

[ https://issues.jboss.org/browse/WFLY-8579?page=com.atlassian.jira.plugin.... ] Scott Van Wart commented on WFLY-8579: -------------------------------------- I attached a maven project that builds an ear for deployment. Run wildfly with standalone.<bat|sh> --server-config=standalone-full-ha.xml, deploy, and access http://localhost:8080/leak-web/rest/test?message=Hi and watch the logs for each of TestTopicListener1 and TestTopicListener2. > Topic messages are sent to all shared non-durable subscription participants > --------------------------------------------------------------------------- > > Key: WFLY-8579 > URL: https://issues.jboss.org/browse/WFLY-8579 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Scott Van Wart > Assignee: Jeff Mesnil > Attachments: duplicate-shared.zip > > > I have two MDBs with a subscription to a topic. The same clientId and a subscriptionName are specified in the activation config properties for each MDB. subscriptionDurability is omitted (defaulted to NonDurable). > When I send a single message to this topic, both MDBs receive the message. According to JSR 343, 8.3.2 Shared non-durable subscriptions: > bq. A non-durable shared subscription is used by a client that needs to be able to > share the work of receiving messages from a non-durable topic subscription > amongst multiple consumers. A non-durable shared subscription may > therefore have more than one consumer. *Each message from the subscription will be delivered to only one of the consumers on that > subscription.* > Setting the subscriptionDurability property to Durable works as expected (each message is delivered to only one consumer in that subscription). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8579) Topic messages are sent to all shared non-durable subscription participants

by Scott Van Wart (JIRA)

[ https://issues.jboss.org/browse/WFLY-8579?page=com.atlassian.jira.plugin.... ] Scott Van Wart updated WFLY-8579: --------------------------------- Attachment: duplicate-shared.zip > Topic messages are sent to all shared non-durable subscription participants > --------------------------------------------------------------------------- > > Key: WFLY-8579 > URL: https://issues.jboss.org/browse/WFLY-8579 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Scott Van Wart > Assignee: Jeff Mesnil > Attachments: duplicate-shared.zip > > > I have two MDBs with a subscription to a topic. The same clientId and a subscriptionName are specified in the activation config properties for each MDB. subscriptionDurability is omitted (defaulted to NonDurable). > When I send a single message to this topic, both MDBs receive the message. According to JSR 343, 8.3.2 Shared non-durable subscriptions: > bq. A non-durable shared subscription is used by a client that needs to be able to > share the work of receiving messages from a non-durable topic subscription > amongst multiple consumers. A non-durable shared subscription may > therefore have more than one consumer. *Each message from the subscription will be delivered to only one of the consumers on that > subscription.* > Setting the subscriptionDurability property to Durable works as expected (each message is delivered to only one consumer in that subscription). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8579) Topic messages are sent to all shared non-durable subscription participants

by Scott Van Wart (JIRA)

Scott Van Wart created WFLY-8579: ------------------------------------ Summary: Topic messages are sent to all shared non-durable subscription participants Key: WFLY-8579 URL: https://issues.jboss.org/browse/WFLY-8579 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.1.0.Final Reporter: Scott Van Wart Assignee: Jeff Mesnil I have two MDBs with a subscription to a topic. The same clientId and a subscriptionName are specified in the activation config properties for each MDB. subscriptionDurability is omitted (defaulted to NonDurable). When I send a single message to this topic, both MDBs receive the message. According to JSR 343, 8.3.2 Shared non-durable subscriptions: bq. A non-durable shared subscription is used by a client that needs to be able to share the work of receiving messages from a non-durable topic subscription amongst multiple consumers. A non-durable shared subscription may therefore have more than one consumer. *Each message from the subscription will be delivered to only one of the consumers on that subscription.* Setting the subscriptionDurability property to Durable works as expected (each message is delivered to only one consumer in that subscription). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1525) [GSS](6.4.z) Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus

by Alessandro Lazarotti (JIRA)

Alessandro Lazarotti created DROOLS-1525: -------------------------------------------- Summary: [GSS](6.4.z) Expired events don't allow a rule belonging to an inactive group to fire even when the group regain focus Key: DROOLS-1525 URL: https://issues.jboss.org/browse/DROOLS-1525 Project: Drools Issue Type: Bug Components: core engine Reporter: Alessandro Lazarotti Assignee: Mario Fusco Fix For: 7.0.0.CR2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1524) Events are not expired if not used in any rule

by Jochen Welle (JIRA)

Jochen Welle created DROOLS-1524: ------------------------------------ Summary: Events are not expired if not used in any rule Key: DROOLS-1524 URL: https://issues.jboss.org/browse/DROOLS-1524 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final Environment: Drools 6.5 / 7.0.0-SNAPSHOT in STREAM mode Reporter: Jochen Welle Assignee: Mario Fusco Attachments: EventWithoutRule.java, EventWithoutRuleTest.java Events which are inserted into the engine but not referenced in any rule are not expired. The event is created as Java class with Role and Expires annotations. The behavior is the same with versions 6.5 and 7.0.0-SNAPSHOT. If I insert an object with event annotations I expected the engine to manage its lifetime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2670) list-add doesn't work for nested list of child attribute

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2670?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-2670: ------------------------------------- Error handling should be more forgiving here. It should first check for result as it does now, but if it doesn't find it, it should be more pragmatic and check if expression as such is valid, which can be done by checking if attribute that is not present in result is even present in attribute description. Looking at the code, it looks like this kind of regression as we have now was introduced when we moved to always all :read-resource before writing back changed attribute. and :read-attribute has different mechanics, where error reporting like this kind a makes sense, but when doing write-attribute you don't care if "middle" parts of expression are not yet defined in the model, they should just be added. > list-add doesn't work for nested list of child attribute > -------------------------------------------------------- > > Key: WFCORE-2670 > URL: https://issues.jboss.org/browse/WFCORE-2670 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > Priority: Critical > > The list-add doesn't work for a child of an attribute as in the example below > Add a dir-context first > {code} > /profile=full/subsystem=elytron/dir-context=dir2:add(url="ldap://test") > {code} > Add a ldap-realm > {code} > /profile=full/subsystem=elytron/ldap-realm=foobar2:add(dir-context=dir2,identity-mapping={rdn-identifier=test}) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => {"main-server-group" => {"host" => {"master" => {"server-one" => {"response" => { > "outcome" => "success", > "response-headers" => {"process-state" => "reload-required"} > }}}}}} > } > {code} > This is the command to add the item to the list > {code} > /profile=full/subsystem=elytron/ldap-realm=foobar2:list-add(name=identity-mapping.new-identity-attributes,value={name=key2,value=["val1","val2"]}) > { > "outcome" => "failed", > "result" => undefined, > "server-groups" => undefined, > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1080) Allow authorization identity to be specified as a Principal

by David Lloyd (JIRA)

David Lloyd created ELY-1080: -------------------------------- Summary: Allow authorization identity to be specified as a Principal Key: ELY-1080 URL: https://issues.jboss.org/browse/ELY-1080 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.1.0.Beta37 The authorization identity is the identity that the user intends to run as. By allowing the identity to be specified as a Principal, the anonymous identity can be given, which is a way of directly selecting anonymous authentication. The existing methods which specify the authorization identity as a string can map to a NamePrincipal. Mechanism selection can also take the authorization ID into account. This also aligns with the run-as logic on the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 April 2017