You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2005/08/29 05:33:08 UTC
[jira] Created: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
reply to EPR for in two channel is hard coded to 127.0.0.1
----------------------------------------------------------
Key: AXIS2-185
URL: http://issues.apache.org/jira/browse/AXIS2-185
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: client-api
Reporter: Thilina Gunarathne
I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=comments#action_12320797 ]
Srinath Perera commented on AXIS2-185:
--------------------------------------
yes I agree, let us set the server address
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=comments#action_12320703 ]
Srinath Perera commented on AXIS2-185:
--------------------------------------
The reply to EPR in the two channel cases is special, becouse here user ask axis2 to start Axis2 server and do the two channel invocation. In that case axis2 is in full control and host is 127.0.0.1.
If you need to have a differant server user the In-OnlyMEPClient not InOutMepClient
I purpose to close this
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=comments#action_12320377 ]
Thilina Gunarathne commented on AXIS2-185:
------------------------------------------
Also the EPR set contains the wsa address with the operation name..
Is this the expected behavior (In the case we are setting up the listener service with the [service name of the calling service+operation name] as the new service name , which is highly confusing)
<wsa:ReplyTo xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <wsa:Address>http://127.0.0.1:6060/axis/services/ActivationCoordinatorPortType/CreateCoordinationContextOperation</wsa:Address>
</wsa:ReplyTo>
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=comments#action_12322704 ]
Eran Chinthaka commented on AXIS2-185:
--------------------------------------
I fixed this by just removing the hard coded value and calling InetAddress.getLocalHost().getHostAddress()
I know this is still 1 problem when the same machine contains multiple network interfaces. I hope the fix is good, at least for the time being.
Can some one please help to resolve this for multiple network interface, or can we simply resolve this issue with the current fix ?
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
Posted by "Sanjiva Weerawarana (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=comments#action_12320709 ]
Sanjiva Weerawarana commented on AXIS2-185:
-------------------------------------------
Hi Srinath!
Even in the simple case where Axis2 is in full control, the other end may not (and is often not) on the same machine. ReplyTo 127.0.0.1 will have weird effects in that case :).
So the naiive response would be "ah no problem, I'll get my IP address and send that".
Well, its much tougher than that to solve for the general case (and pretty much impossible):
- machine could have multiple network interfaces and you may need to get the right one for the IP routing to work
- that's simple compared to the real problem: NAT (network address translation). Suppose the client is behind a box which is NAT'ing .. then you're literally toast because there's pretty much no way to figure out what address to give to the other side so that messages can be routed back to you. The same kind of problem could occur with any kind of proxy/firewall in the middle.
Ah but there's (partial) hope for the future .. can you say .. Synapse? ;-). Yes, with an intermediary it could re-write parts of the SOAP envelope to fix stuff like that. Obviously you can't handle every case .. if the headers are signed then you can't change them and then basically you are screwed.
The deeper problem here is that we're embedding a network level bit of info (the IP addr) inside an application message. This is not a new problem - even CORBA has it (any time you pass an IOR as piece of data you get this same issue), but NAT is a recent development/adoption and so its much more likely to be a real problem than before.
So for now, I suggest the simple solution of taking the IP address of the server and using that instead of 127.0.0.1; that will clearly handle a larger class of scenarios than the current approach does. Is that class big enough? Probably not, but I'm not sure how one would handle the NAT case.
Sanjiva.
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
Posted by "Aleksander Slominski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=comments#action_12320778 ]
Aleksander Slominski commented on AXIS2-185:
--------------------------------------------
For NAT, mobile clients, fire walled clients etc the solution is to provide external service that will act as an endpoint that client can advertise in EPR ReplyTo/FaultTo. One such service with pull capability (so clients can access their messages even when client is behind firewall) is open-source free WS-MsgBox - both design and code available at http://www.extreme.indiana.edu/xgws/msgbox/
also for content dispatch i think that this can work very well with "ultra-lightweight" ESB that is a pure-dispatcher as long as it supports HTTP/SOAP/RPC and async SOAP/WS-Addressing - that is our experience and we wrote a paper about its design and testing it long-distance, long-latency haul (USA-France): http://www.extreme.indiana.edu/xgws/dispatcher
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-185) reply to EPR for in two channel is
hard coded to 127.0.0.1
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-185?page=all ]
Ruchith Udayanga Fernando resolved AXIS2-185:
---------------------------------------------
Resolution: Fixed
Fixed in r360248
> reply to EPR for in two channel is hard coded to 127.0.0.1
> ----------------------------------------------------------
>
> Key: AXIS2-185
> URL: http://issues.apache.org/jira/browse/AXIS2-185
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Thilina Gunarathne
>
> I found the reply to EPR in non blocking two channel case is harcoded to 127.0.0.1.
> IMHO this will cause mal functioning of the axis2 server when it's deployed in some where else other than the local machine....
> Pls correct me if I'm wrong...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira