[JBoss JIRA] Created: (JGRP-1240) TCP: add physical address of peer to physical address cache (bypassing discovery)
by Bela Ban (JIRA)
TCP: add physical address of peer to physical address cache (bypassing discovery)
---------------------------------------------------------------------------------
Key: JGRP-1240
URL: https://jira.jboss.org/browse/JGRP-1240
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.11
When we use TCP, the physical address information of a peer P connecting to us should always be available !
E.g.currently, if we have A and B, and A wants to send a message to B, but doesn't have B's physical address, if A is connected to B, then we can get that information from the connection map in TCP !
We should therefore add the physical address information for B when B connects to us, or we connect to B !
Issues:
- What if B binds to address 10.1.1.1, but - when B connects to us (A: 192.16.8.1.5) - its peer address is 192.168.1.3 ? Is this possible at all ? Does the routing table force a different peer address of B: 192.168.x.x rather than 10.1.x.x ?
- Although we might be able to get the physical address of B, we don't get its logical name ! How would we do that, discovery ?
--
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
15 years, 5 months
[JBoss JIRA] Created: (JASSIST-123) Explicit class import support for compiler (not whole packages)
by Ivan Prisiazhnyy (JIRA)
Explicit class import support for compiler (not whole packages)
---------------------------------------------------------------
Key: JASSIST-123
URL: https://jira.jboss.org/browse/JASSIST-123
Project: Javassist
Issue Type: Patch
Reporter: Ivan Prisiazhnyy
Assignee: Shigeru Chiba
This is patch for MemberResolver class for Javassist 3.12.GA
It adds support for compiler to understand importing of certain classes in packages, not the whole packages.
With this patch the following code will do its job:
ClassPool x = ClassPool.getDefault();
x.importPackage("java.io.File");
Patch it self:
*** MemberResolver.java 2010-06-10 14:38:03.000000000 +0300
***************
*** 429,445 ****
}
catch (NotFoundException e) {
classPool.recordInvalidClassName(fqName);
-
- try {
- if (pac.endsWith(orgName)) {
- CtClass cc = classPool.get(pac);
- // if the class is found,
- classPool.recordInvalidClassName(orgName);
- return cc;
- }
- } catch (NotFoundException ee) {
- classPool.recordInvalidClassName(pac);
- }
}
}
}
--- 429,434 ----
--
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
15 years, 5 months
[JBoss JIRA] Created: (JGRP-1188) Probe.sh does not display matches summary on termination.
by Richard Achmatowicz (JIRA)
Probe.sh does not display matches summary on termination.
---------------------------------------------------------
Key: JGRP-1188
URL: https://jira.jboss.org/jira/browse/JGRP-1188
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4.7
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.4.8
Matched statistics are not appearing at the end of the probe.sh output
- when probe.sh, with the -match option specified, terminates, I should only see responses which contain the match string, and should see a summary line something like:
Total responses=1, 1 matches, 3 non-matches
This reflects how many responses were matched with the -match <match string> parameter.
For example:
[rachmatowicz@vmg18 bin]$ ./probe.sh -match Tomcat-Cluster
-- send probe on /224.0.75.75:7500
#1 (262 bytes): 10.16.95.19:44066 (Tomcat-Cluster)
local_addr=10.16.95.19:44066
group_name=Tomcat-Cluster
version=2.4.7.GA, cvs="$Id: Version.java,v 1.42.2.14 2009/11/03 23:15:25 rachmatowicz Exp $"
view: [10.16.95.19:44066|0] [10.16.95.19:44066]
group_addr=239.11.12.13:45577
Here, the responses were correctly matched, but no summary line is produded.
This summary line is not appearing, because a thread set up to close the multicast socket after timeout seconds is causing the multicast socket to generate an exception and return, before the control loop can be exited and the summary line printed. Moving the summary line into the exception handling code fixes the problem.
--
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
15 years, 5 months