July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-705) Unicast JGroups

by Bela Ban (JIRA)

Unicast JGroups --------------- Key: JGRP-705 URL: http://jira.jboss.com/jira/browse/JGRP-705 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Investigate use of JGroups for point-to-point communication, as a replacement for java.net{Server}Socket. E.g. Channelch=new JChannel(); ch.connect(null); // null means p2p -- 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

13 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-1318) JMX notifications for view changes, connect/disconnect events

by Bela Ban (JIRA)

JMX notifications for view changes, connect/disconnect events ------------------------------------------------------------- Key: JGRP-1318 URL: https://issues.jboss.org/browse/JGRP-1318 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12.2, 3.1 Emit JMX notifications for various JGroups events, e.g. - view changes - channel connected / disconnected / closed - local address set -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-998) AUTH / FixedMembershipToken: pattern matching and match against logical names

by Bela Ban (JIRA)

AUTH / FixedMembershipToken: pattern matching and match against logical names ----------------------------------------------------------------------------- Key: JGRP-998 URL: https://jira.jboss.org/jira/browse/JGRP-998 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 #1 Use pattern matching to match hosts against senders, using regular expressions. #2 Provide matching of logical names in addition to physical addresses -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-1337) ConnectionMap: getConnection() can be a bottleneck

by Bela Ban (JIRA)

ConnectionMap: getConnection() can be a bottleneck -------------------------------------------------- Key: JGRP-1337 URL: https://issues.jboss.org/browse/JGRP-1337 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.1 When multiple threads call TcpConnectionMap.Mapper.getConnection() to different target addresses, and some of those addresses are down, then the threads unnecessarily compete for the same lock, therefore socket creations to targets which are up might get delayed by socket creations to targets which are down. SOLUTION: move the actual creation of a socket out of the lock scope NOTE: getConnection() may not even need to acquire the lock as the calling code already acquired it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JGRP-1316) MPING doesn't always bind to correct interface address

by Daniel Noguerol (JIRA)

MPING doesn't always bind to correct interface address ------------------------------------------------------ Key: JGRP-1316 URL: https://issues.jboss.org/browse/JGRP-1316 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Reporter: Daniel Noguerol Assignee: Bela Ban MPING's bindToInterfaces method doesn't take the stack type into consideration. It iterates through all interfaces and addresses but binds to the first address on each interface -- which may not be the correct one based on Util.getIpStackType(). See Workaround Description for workaround solution that worked for me. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JGRP-1174) Logging: follow logging conventions

by Bela Ban (JIRA)

Logging: follow logging conventions ----------------------------------- Key: JGRP-1174 URL: https://jira.jboss.org/jira/browse/JGRP-1174 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 https://docspace.corp.redhat.com/docs/DOC-30217 Requires code to be published, which can be copied over to JGroups (no JAR dep) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1203) test for missing xa-datasource properties

by Stefano Maestri (JIRA)

test for missing xa-datasource properties ----------------------------------------- Key: AS7-1203 URL: https://issues.jboss.org/browse/AS7-1203 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
6
0 / 0

[JBoss JIRA] Created: (JBAS-8222) Common approach to extension properties

by Brian Stansberry (JIRA)

Common approach to extension properties --------------------------------------- Key: JBAS-8222 URL: https://jira.jboss.org/browse/JBAS-8222 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Various elements in the domain models schema will include generic <properties> elements. David LLoyd described such an element as "the last ditch thing where we can add in stuff for support etc. without changing the schema." We need to document and clarify what the users can expect in terms of forward compatibility for content they include in such an element. And then ensure it's applied consistently across the various schema we'll be using. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JGRP-1320) NAKACK: display the combined size of all messages in the retransmission tables

by Bela Ban (JIRA)

NAKACK: display the combined size of all messages in the retransmission tables ------------------------------------------------------------------------------ Key: JGRP-1320 URL: https://issues.jboss.org/browse/JGRP-1320 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Optional Fix For: 2.12.2, 3.1 - Add a JMX method to dump the size of all messages in all NakReceiverWindows - Add a JMX attribute to dump the combined sizes of *all* messages of all NakReceiverWindows The size could be payload only, or Message.size() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1389) Log API dependencies should be included automatically in deployments

by David Lloyd (JIRA)

Log API dependencies should be included automatically in deployments -------------------------------------------------------------------- Key: AS7-1389 URL: https://issues.jboss.org/browse/AS7-1389 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: David Lloyd Fix For: 7.0.1.Final The following log APIs should be included by deployments by default: * {{org.slf4j}} * {{org.apache.commons.logging}} * {{org.log4j}} These dependencies should override the deployment's versions of these libraries unless explicitly excluded by {{jboss-deployment-structure.xml}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011