April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-459) 5.6.x: update version to 5.6.1-SNAPSHOT as 5.6.0.Final is already out

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-459?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer resolved DROOLS-459. ------------------------------------------- Resolution: Done done! > 5.6.x: update version to 5.6.1-SNAPSHOT as 5.6.0.Final is already out > --------------------------------------------------------------------- > > Key: DROOLS-459 > URL: https://issues.jboss.org/browse/DROOLS-459 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Petr Široký > Assignee: Michael Biarnes Kiefer > > The version in 5.6.x branch is still 5.6.0-SNAPSHOT, even though the 5.6.0.Final has been already released. Please update the version to 5.6.1-SNAPSHOT. > Similarly with jBPM, the version should be updated to 5.5.1-SNAPSHOT. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1819) TopologyUUID.getMachineID() returns rack id

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1819?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1819. ---------------------------- Resolution: Done > TopologyUUID.getMachineID() returns rack id > ------------------------------------------- > > Key: JGRP-1819 > URL: https://issues.jboss.org/browse/JGRP-1819 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Reporter: Dan Berindei > Assignee: Bela Ban > Fix For: 3.5 > > > The new implementation of {{TopologyUUID}} in 3.5.0.Beta2 returns the rack id instead of the machine id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1819) TopologyUUID.getMachineID() returns rack id

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1819?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1819: -------------------------------- Will be in the next release. I'm waiting for a few issues to get fixed until I'll release a Beta3 > TopologyUUID.getMachineID() returns rack id > ------------------------------------------- > > Key: JGRP-1819 > URL: https://issues.jboss.org/browse/JGRP-1819 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Reporter: Dan Berindei > Assignee: Bela Ban > Fix For: 3.5 > > > The new implementation of {{TopologyUUID}} in 3.5.0.Beta2 returns the rack id instead of the machine id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1819) TopologyUUID.getMachineID() returns rack id

by Dan Berindei (JIRA)

Dan Berindei created JGRP-1819: ---------------------------------- Summary: TopologyUUID.getMachineID() returns rack id Key: JGRP-1819 URL: https://issues.jboss.org/browse/JGRP-1819 Project: JGroups Issue Type: Bug Affects Versions: 3.5 Reporter: Dan Berindei Assignee: Bela Ban Fix For: 3.5 The new implementation of {{TopologyUUID}} in 3.5.0.Beta2 returns the rack id instead of the machine id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1151) Allow testConnection() without statistics enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1151?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1151: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1075638|https://bugzilla.redhat.com/show_bug.cgi?id=1075638] from NEW to MODIFIED > Allow testConnection() without statistics enabled > ------------------------------------------------- > > Key: JBJCA-1151 > URL: https://issues.jboss.org/browse/JBJCA-1151 > Project: IronJacamar > Issue Type: Task > Components: Core > Affects Versions: 1.0.24.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.25.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3154) Operation which require server reload should check if something was changed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3154?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3154: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 976228|https://bugzilla.redhat.com/show_bug.cgi?id=976228] from POST to MODIFIED > Operation which require server reload should check if something was changed > ---------------------------------------------------------------------------- > > Key: WFLY-3154 > URL: https://issues.jboss.org/browse/WFLY-3154 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > Description of problem: > Server reload is required even if nothing was actually changed. This could have negative impact on usability of WildFly. > Steps to Reproduce: > - start standalone > - connect to cli > - run: /subsystem=jpa:write-attribute(name=default-extended-persistence-inheritance, value=SHALLOW) > - reload server > - run: /subsystem=jpa:write-attribute(name=default-extended-persistence-inheritance, value=SHALLOW) > Actual results: > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > Expected results: > - reload is not required -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3169) Add JMX notifications for management resources

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3169?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-3169: ------------------------------ Fix Version/s: 9.0.0.CR1 > Add JMX notifications for management resources > ---------------------------------------------- > > Key: WFLY-3169 > URL: https://issues.jboss.org/browse/WFLY-3169 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.CR1 > > > Based on WFLY-266, the JMX subsystem could provide standard JMX notifications for resource registered/unregistered and changes of attributes values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-266) Add Notification support to the domain management API

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-266?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil updated WFLY-266: ----------------------------- Fix Version/s: 9.0.0.CR1 > Add Notification support to the domain management API > ----------------------------------------------------- > > Key: WFLY-266 > URL: https://issues.jboss.org/browse/WFLY-266 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 9.0.0.CR1 > > > Management resource should be able to emit notifications; clients can register listeners. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3193) upgrade Generic JMS RA to 1.0.4.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3193?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3193: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1082617|https://bugzilla.redhat.com/show_bug.cgi?id=1082617] from NEW to POST > upgrade Generic JMS RA to 1.0.4.Final > ------------------------------------- > > Key: WFLY-3193 > URL: https://issues.jboss.org/browse/WFLY-3193 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA, JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1734) Probe: restrict requests to certain clusters and/or nodes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1734?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1734: -------------------------------- Probe requests are actually dropped *at the server side* if the cluster name doesn't match > Probe: restrict requests to certain clusters and/or nodes > --------------------------------------------------------- > > Key: JGRP-1734 > URL: https://issues.jboss.org/browse/JGRP-1734 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 3.4.1, 3.5 > > > Probe.sh broadcasts requests to all reachable nodes in any cluster. The only way to restrict the reach of a probe request is to pass a time-to-live to it, but that's (a) too coarse-grained and (b) doesn't work for TCP. > We should therefore be able to define a list of clusters and a list of nodes to which we want to restrict the request. Both clusters and nodes should be simple regexps. > The filter is sent with the probe request. Nodes which don't pass the filter simply discard the request. > Example: > {noformat} > probe.sh -cluster DrawCluster,cluster-*{noformat} > This restricts the request to the {{DrawCluster}} and any cluster starting with {{cluster-}}. > {noformat} > probe.sh -nodes cluster-* > {noformat} > Sends the request only to nodes with a name starting with {{cluster}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

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 2014