September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5478) Upgrade Infinispan to 5.1.7.Final

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-5478: ----------------------------------- Summary: Upgrade Infinispan to 5.1.7.Final Key: AS7-5478 URL: https://issues.jboss.org/browse/AS7-5478 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.3.Final (EAP) We will probably need a component upgrade in Infinispan incorporating changes in Dan's branch to resolve JBPAPP-9658/AS7-5381 and possibly AS7-5442. Last release is 5.1.6.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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-5499) Upgrade HornetQ to 2.2.19.Final-build2

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5499: -------------------------------- Summary: Upgrade HornetQ to 2.2.19.Final-build2 Key: AS7-5499 URL: https://issues.jboss.org/browse/AS7-5499 Project: Application Server 7 Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.1.3.Final (EAP) this version of HornetQ depends on Netty 3.2.2.Final and corresponds to HornetQ 2.2.19.Final minus HORNETQ-819 -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Tom Fonteyne commented on AS7-5403: ----------------------------------- I'd go for your proposal with the "enable" step - sounds like an acceptable & good solution to me. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Joe Wertz > > Adding modcluster via the CLI fails. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-246) Configure Jboss loadbalancing in Window 2008 R2

by Buntha Ly (JIRA)

Buntha Ly created JBWEB-246: ------------------------------- Summary: Configure Jboss loadbalancing in Window 2008 R2 Key: JBWEB-246 URL: https://issues.jboss.org/browse/JBWEB-246 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cluster Environment: Window Server 2008 R2 configured as clustering and loadbalancing Reporter: Buntha Ly Assignee: Remy Maucherat Priority: Critical Hi Everyone, I am very new with Jboss. Could you please share me some document to configure and set up Jboss loadbalancing in Window 2008 R2 configure as clustering? Thanks -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-4140) Change distribution of -Dmcast through testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-4140?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4140: ------------------------------------- Ondro Can you resubmit and link the PR now? Or is there some outstanding issue? > Change distribution of -Dmcast through testsuite > ------------------------------------------------ > > Key: AS7-4140 > URL: https://issues.jboss.org/browse/AS7-4140 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 7.1.2.Final (EAP) > > > Please change present behavior. > We need to define only one property -Dmcast (for ex., the name doesn't matter now) as command line parameter - this multicast address is needed to be distributed to every subsystem which manages any multicast communication. It is needed to be unique in every subsystem - JGroups, HornetQ etc. because we must avoid to interfere each other => port assignation must be unique for every a such component. > This change is needed in both - IPV4 and IPv6... -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-892) IronJacamar 1.1.0.Beta2

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-892: ------------------------------------- Summary: IronJacamar 1.1.0.Beta2 Key: JBJCA-892 URL: https://issues.jboss.org/browse/JBJCA-892 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta2 Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3620) Conditional named consequences

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3620: ------------------------------------ Summary: Conditional named consequences Key: JBRULES-3620 URL: https://issues.jboss.org/browse/JBRULES-3620 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Implement named consequence like in the following example: rule R1 A() do[t1] B() then // default consequence executed with both A() and B() then[t1] // named consequence on A() end In this example, when a match for A() is found, the consequence named t1 is scheduled on the agenda and then the LHS pattern matching evaluation continues as per normal looking for a join with B() and eventually scheduling also the default consequence. The named consequence activation can be optionally guarded by a condition like in: A() if (condition) do[t1] B() Here the named consequence t1 is activated only if the boolean condition (expressed on the last pattern before the if, A() in this case) evaluates to true. The conditional named consequence invocation can be also breaking, i.e. can block any further pattern matching when the condition is satisfied like in: A() if (condition) break[t1] B() Note that the use of a breaking named consequence without any condition like in: A() break[t1] B() doesn't make sense (and should generate a compile time error) because the join with B() shouldn't be reachable. Using one or more if/else it is also possible to have multiple nested conditions like in the following example: A() if (condition1) do[t1] else if (condition2) do[t2] else break[t3] B() -- 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

13 years, 8 months

1
6
0 / 0

[JBoss JIRA] (JGRP-1484) SEQUENCER and merge-views broken

by David Hotham (JIRA)

David Hotham created JGRP-1484: ---------------------------------- Summary: SEQUENCER and merge-views broken Key: JGRP-1484 URL: https://issues.jboss.org/browse/JGRP-1484 Project: JGroups Issue Type: Bug Affects Versions: 3.0.10 Reporter: David Hotham Assignee: Bela Ban Here's a new way in which putting SEQUENCER below GMS is broken. Start with A having view B|4 [B,A], while B, C and D all have view B|7 [B,C,D]. Now we start a merge, in which B is coordinator. B creates the view C|8 [C, D, A, B]. (I've opened a pull request saying that B surely shouldn't issue a view where the ViewID says that C was the creator. But I think that this is incidental, and not key to the bug that I'm reporting here). Now B sends INSTALL_MERGE_VIEW to B (a coordinator) and A (a merge participant, per Util.determineMergeParticipants). B gets this first and broadcasts the new view to [B, C, D]. In particular, B is now not a coordinator. Then A gets the INSTALL_MERGE_VIEW, and it too tries broadcasting the new view. SEQUENCER gets involved, and forwards the broadcast to B (as the coordinator in the old view). B discards this; it's no longer a coordinator. So the new view is not installed at A. All future broadcasts from A are forwarded to B, who discards them. The group is fractured, and none of A's broadcasts are delivered. I'm not sure what the right fix would be. I wonder whether things should be arranged so that in a merge: - coordinators behave as today, broadcasting the new view to their own sub-groups - but mere participants do not do this: they should just have the new view installed on them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
32
0 / 0

[JBoss JIRA] (AS7-5364) Allow WebService deployments as OSGi bundles

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5364: ----------------------------------- Summary: Allow WebService deployments as OSGi bundles Key: AS7-5364 URL: https://issues.jboss.org/browse/AS7-5364 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Web Reporter: Thomas Diesler Fix For: 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] (JBRULES-3618) Unexpected behaviour when using expression in duration-attribute

by Wannes Kerckhove (JIRA)

Wannes Kerckhove created JBRULES-3618: ----------------------------------------- Summary: Unexpected behaviour when using expression in duration-attribute Key: JBRULES-3618 URL: https://issues.jboss.org/browse/JBRULES-3618 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.4.0.Final Environment: Microsoft Windows 7 Enterprise, Eclipse Juno IDE Reporter: Wannes Kerckhove Assignee: Mark Proctor In some cases the duration-attribute for a rule doesn't behave as would be expected when an expression is used to indicate the duration time (i.e. it triggers too late). When replacing the expression with the equivalent literal value, the rule triggers correctly. -- 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

13 years, 8 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 September 2012