June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-515) UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems

by ggimler (JIRA)

UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems ------------------------------------------------------------------------------------------------------------------------ Key: JGRP-515 URL: http://jira.jboss.com/jira/browse/JGRP-515 Project: JGroups Issue Type: Patch Environment: Tested on Fedora Core 6, JDK 1.5.0_10 Reporter: ggimler Assigned To: Bela Ban I'm submitting a patch for a crosstalk issue described below. I'm trying to debug a problem I'm seeing when running JGroups on the same network/machine as another application that is sending/receiving data via regular multicast (not through JGroups). I'm using version 2.4.1-SP3. My scenario is as follows... JGroups send on 228.0.0.1:50000 JGroups receive on 228.0.0.1:50000 This works fine. When I start up another application that does Sends regular multicast on 228.0.0.2:50000 Receives regular multicast on 228.0.0.2:50000 Then the JVM with the JGroups sender/receiver complains with: May 15, 2007 4:47:59 PM org.jgroups.protocols.TP handleIncomingPacket WARNING: packet from 192.168.101.133:36594 has different version (26725) from ours (2.4.1). Packet is discarded The patch is in UDP.java: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
18
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-429) Implement intelligent flow control

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-429?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-429: ------------------------------------- We should be able to specify quotas on a per user basis, so we can say producer Bob can send up to 100 msgs/sec max, for example. Also we allow automatic throttling when the queue reaches a certain size. I.e. producers block until some messages are consumed. > Implement intelligent flow control > ---------------------------------- > > Key: JBMESSAGING-429 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-429 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Fix For: 2.0.0 Beta 1 > > > We should implement an intelligent flow control mechanism so message sending can be automatically throttled when consumers are slow to prevent messages bulding up on queues/subscriptions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-703) ServerManager.startRemoting should read the configuration from XML

by Clebert Suconic (JIRA)

ServerManager.startRemoting should read the configuration from XML ------------------------------------------------------------------ Key: JBMESSAGING-703 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-703 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Priority: Optional Fix For: 1.2.1 Using the same XML configuration would be a better approach since it would validate the remoting configuration released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-855) release-admin.xml fails to create a clustered configuration based on a 4.0.5.GA-ejb3 installation

by Ovidiu Feodorov (JIRA)

release-admin.xml fails to create a clustered configuration based on a 4.0.5.GA-ejb3 installation ------------------------------------------------------------------------------------------------- Key: JBMESSAGING-855 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-855 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA release-admin.xml relies on finding ${jboss.home}/docs/examples/binding-manager/sample-bindings.xml. 4.0.5.GA-ejb3 installations seem not to have a "docs" sub-directory, so release-admin.xml fails. I've created an "artificial" one under my jboss-4.0.5.GA-ejb3 so I can get the smoke tests passing, but users will have troubles if they try to use release-admin.xml with 4.0.5.GA-ejb3. Need to coordinate with the AS team to find a proper solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-467) Sort out JBoss AS dependencies

by Ovidiu Feodorov (JIRA)

Sort out JBoss AS dependencies ------------------------------ Key: JBMESSAGING-467 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-467 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 Currently we've imported JBossAS in the lib area of our project to keep the project compiling. This is hardly an acceptable solution. The proper solution involves: 1) Deciding what JBossAS depenencies we need and getting rid of arificially dependencies 2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed in the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

4
9
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-186) Check that all TODOs and FIXMEs correspond to known JIRA tasks

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-186?page=all ] Tim Fox updated JBMESSAGING-186: -------------------------------- Priority: Minor (was: Major) > Check that all TODOs and FIXMEs correspond to known JIRA tasks > -------------------------------------------------------------- > > Key: JBMESSAGING-186 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-186 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.4.0.CR1 > > > .. and if not, create appropriate JIRA tasks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-455) CVS to SVN repository migration

by Ovidiu Feodorov (JIRA)

CVS to SVN repository migration ------------------------------- Key: JBMESSAGING-455 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-455 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-962) Fix deadlock in PointToMultipointRouter

by Tim Fox (JIRA)

Fix deadlock in PointToMultipointRouter --------------------------------------- Key: JBMESSAGING-962 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-962 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP5, 1.2.0.SP1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.SP2 Need to fix deadlock in PointToMultipointRouter - this is a similar deadlock to that in the other routers and fixed in http://jira.jboss.org/jira/browse/JBMESSAGING-505 but for some reason the fix wasn't applied to the PointToMultiPointRouter -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-760) Re-enable some bridge recovery tests after JBoss TS bug is fixed

by Tim Fox (JIRA)

Re-enable some bridge recovery tests after JBoss TS bug is fixed ---------------------------------------------------------------- Key: JBMESSAGING-760 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-760 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Renable ReconnectTest::testCrashAndReconnectDestCrashOnCommit_P and ReconnectTest::testCrashAndReconnectDestCrashOnCommit_NP after http://jira.jboss.com/jira/browse/JBTM-192 is complete. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-985) ClassCastException when using RoundRobinRouter

by Tim Fox (JIRA)

ClassCastException when using RoundRobinRouter ---------------------------------------------- Key: JBMESSAGING-985 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-985 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 When specifying RoundRobinRouterFactory for a clustered post office and when there are >0 non clustered queues, a ClassCastException will be thrown on deploy. This is due to the router not taking account of non clustered queues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
1
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 June 2007