October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2210) fix message endpoint isDeliveryTransacted

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-2210: --------------------------------- Summary: fix message endpoint isDeliveryTransacted Key: WFLY-2210 URL: https://issues.jboss.org/browse/WFLY-2210 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 8.0.0.Alpha4 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Blocker Fix For: 8.0.0.Beta1 The org.jboss.as.ejb3.inflow.MessageEndpointService#isDeliveryTransacted method is checking the transaction attribute of the method using the MethodIntf.BEAN while it should use the MethodIntf.MESSAGE_ENDPOINT type. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1713) MERGE3: view in header is too big in large clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1713?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1713. ---------------------------- Resolution: Done > MERGE3: view in header is too big in large clusters > --------------------------------------------------- > > Key: JGRP-1713 > URL: https://issues.jboss.org/browse/JGRP-1713 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.4 > > > In MERGE3, as a response to a VIEW_REQ, a VIEW_RSP contains the entire view (not a delta view), and because this is returned in the header, we might run into the same issue as in https://issues.jboss.org/browse/JGRP-1710. > SOLUTION: > Move the view carried with a VIEW_RSP into the message body and add FRAG2 over the transport to fragment this message. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-281) no reevaluation of 'from collect' is performed

by Richard Bourner (JIRA)

[ https://issues.jboss.org/browse/DROOLS-281?page=com.atlassian.jira.plugin... ] Richard Bourner updated DROOLS-281: ----------------------------------- Attachment: Drools6FromCollectIssue.zip Maven Eclipse project demonstrating the issue with 2 rules and 1 unit test. > no reevaluation of 'from collect' is performed > ---------------------------------------------- > > Key: DROOLS-281 > URL: https://issues.jboss.org/browse/DROOLS-281 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Reporter: Richard Bourner > Assignee: Mark Proctor > Priority: Critical > Attachments: Drools6FromCollectIssue.zip > > > Using Drools 6.0.0.CR4, a problem has been found related to reevaluation of a condition that contains a 'from collect' statement. > A unit test is provided demonstrating the issue using 2 rules. This unit test works fine using 6.0.0.Beta2. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-281) no reevaluation of 'from collect' is performed

by Richard Bourner (JIRA)

Richard Bourner created DROOLS-281: -------------------------------------- Summary: no reevaluation of 'from collect' is performed Key: DROOLS-281 URL: https://issues.jboss.org/browse/DROOLS-281 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR4 Reporter: Richard Bourner Assignee: Mark Proctor Priority: Critical Using Drools 6.0.0.CR4, a problem has been found related to reevaluation of a condition that contains a 'from collect' statement. A unit test is provided demonstrating the issue using 2 rules. This unit test works fine using 6.0.0.Beta2. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Headers: data in some headers might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1714: --------------------------- Description: Similar to JGRP-1710 and JGRP-1713, investigate headers which might become too big, and move their contents into the message body. Check all headers which contain * a view * a digest * a list of members Candidates: * {{PingHeader}}. Probable solution: move {{PingHeader.PingData}} from the header to the message body was:Similar to JGRP-1710 and JGRP-1713, investigate {{PingHeader}}. Probable solution: move {{PingHeader.PingData}} from the header to the message body > Headers: data in some headers might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Similar to JGRP-1710 and JGRP-1713, investigate headers which might become too big, and move their contents into the message body. Check all headers which contain > * a view > * a digest > * a list of members > Candidates: > * {{PingHeader}}. > Probable solution: move {{PingHeader.PingData}} from the header to the message body -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Headers: data in some headers might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1714: --------------------------- Comment: was deleted (was: Investigate headers which might become too big, and move their contents into the message body. Check all headers which contain * a view * a digest * a list of members) > Headers: data in some headers might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Similar to JGRP-1710 and JGRP-1713, investigate headers which might become too big, and move their contents into the message body. Check all headers which contain > * a view > * a digest > * a list of members > Candidates: > * {{PingHeader}}. > Probable solution: move {{PingHeader.PingData}} from the header to the message body -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Headers: data in some headers might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1714: --------------------------- Summary: Headers: data in some headers might be too large in big clusters (was: Discovery: data in PingHeader might be too large in big clusters) > Headers: data in some headers might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Similar to JGRP-1710 and JGRP-1713, investigate {{PingHeader}}. Probable solution: move {{PingHeader.PingData}} from the header to the message body -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Discovery: data in PingHeader might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1714: -------------------------------- Investigate headers which might become too big, and move their contents into the message body. Check all headers which contain * a view * a digest * a list of members > Discovery: data in PingHeader might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Similar to JGRP-1710 and JGRP-1713, investigate {{PingHeader}}. Probable solution: move {{PingHeader.PingData}} from the header to the message body -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1714) Discovery: data in PingHeader might be too large in big clusters

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1714?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1714: --------------------------- Fix Version/s: 3.5 (was: 3.4) > Discovery: data in PingHeader might be too large in big clusters > ---------------------------------------------------------------- > > Key: JGRP-1714 > URL: https://issues.jboss.org/browse/JGRP-1714 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > Similar to JGRP-1710 and JGRP-1713, investigate {{PingHeader}}. Probable solution: move {{PingHeader.PingData}} from the header to the message body -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-276?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-276: ------------------------------------------------ Richard Bourner <rbourner(a)redhat.com> made a comment on [bug 1012933|https://bugzilla.redhat.com/show_bug.cgi?id=1012933] A little precision: it appears that the problem occurs only with Phreak algo in Stream mode. In the unit tests I created, I had not included the reteoo JAR, so it was redirected to Phreak without my noticing. Bottom line: out of 4 unit tests, only 1 fails now. > Stream mode with CR4-Pre1 generates rules looping > -------------------------------------------------- > > Key: DROOLS-276 > URL: https://issues.jboss.org/browse/DROOLS-276 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Environment: Drools 6.0.0.CR4-Pre1 > Reporter: Richard Bourner > Assignee: Mark Proctor > Priority: Blocker > Attachments: Drools6Stream.zip > > > When in STREAM mode, our rules are looping because of an update. > The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- 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, 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 2013