[JBoss JIRA] Created: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
3:03 a.m.
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side
IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:35 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov updated JBMESSAGING-1020:
-----------------------------------------
Attachment: JBMESSAGING-1020.patch
Requires the JBREM-781 patch
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
1:26 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov reassigned JBMESSAGING-1020:
--------------------------------------------
Assignee: Ovidiu Feodorov (was: Tim Fox)
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
1:40 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1020:
----------------------------------------------
Created https://svn.jboss.org/repos/messaging/branches/Branch_1_0_1_SP4_JBMESSAGI...,
applied changes there, made sure it uses remoting_2_2_0_Alpha7_JBREM-781_patch
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
2:28 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1020:
----------------------------------------------
Case 00017224
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
2:29 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov closed JBMESSAGING-1020.
----------------------------------------
Resolution: Done
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:37 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=comments#action_1... ]
Ovidiu Feodorov commented on JBMESSAGING-1020:
----------------------------------------------
Patch required by case 00017224
Created https://svn.jboss.org/repos/messaging/branches/Branch_1_0_1_SP4_JBMESSAGI...,
applied changes there, made sure it uses remoting_2_2_0_Alpha7_JBREM-781_patch
Tag:
https://svn.jboss.org/repos/messaging/tags/JBossMessaging_1_0_1_SP4_JBMES...
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:37 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov updated JBMESSAGING-1020:
-----------------------------------------
Comment: was deleted
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:37 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov updated JBMESSAGING-1020:
-----------------------------------------
Comment: was deleted
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:39 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov reopened JBMESSAGING-1020:
------------------------------------------
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:41 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov updated JBMESSAGING-1020:
-----------------------------------------
Attachment: jboss-messaging.jar
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch, jboss-messaging.jar
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:43 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov updated JBMESSAGING-1020:
-----------------------------------------
Attachment: jboss-messaging-client.jar
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch, jboss-messaging-client.jar,
jboss-messaging.jar
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
3:45 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1020) JBM 1.0 series (SP4 and higher) need to be able to dynamically detect a valid client-side IP interface
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1020?page=all ]
Ovidiu Feodorov closed JBMESSAGING-1020.
----------------------------------------
Resolution: Done
Artifacts corresponding to JBossMessaging_1_0_1_SP4_JBMESSAGING_1020 (compiled with Java
1.4) attached to the case.
JBM 1.0 series (SP4 and higher) need to be able to dynamically detect
a valid client-side IP interface
------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1020
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1020
Project: JBoss Messaging
Issue Type: Patch
Components: JMS Remoting
Affects Versions: 1.0.1.SP4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Attachments: JBMESSAGING-1020.patch, jboss-messaging-client.jar,
jboss-messaging.jar
JBM 1.0 series uses a client-side remoting callback server to accept server-to-client TCP
connections. This connections are used by the JBM server to asynchronously send messages
to the client. However, for multi-homed clients, there are situations when the client
sends an incorrect IP address: InetAddress.getLocalHost().getHostAddress() returns a
different IP address than one that is visible from the server side.
The documentation suggest using "jboss.messaging.callback.bind.address" system
property to force an IP address. This approach is not satisfactory, as IP addresses on
client machines change upon reboot. The overhead of changing static configuration for each
reboot is unacceptable.
The problem stems from the fact that InetAddress.getLocalHost(), which is used by the
Messaging code as default callback server address, may not be reachable from the JMS
server, depending on the routing configuration.
The patch uses the assumption that once the direct client-to-server TCP/IP connection is
established, the client-side local address of that connection can be reached reached from
the server. To get that IP address back to the client, the Remoting protocol should be
modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only
handled by socket transports and ignored by others.
The Messaging client sends an invocation containing this primitive immediately after
connection is established. If the invocation returns a non-null result, the Messaging
client will use that IP address (presumably one of its own local interfaces) to configure
the callback server.
--
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
6886
days inactive
6893
days old
12 comments
1 participants
participants (1)
-
Ovidiu Feodorov (JIRA)