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:45:07 UTC
[jira] Commented: (AXIS2-185) reply to EPR for in two channel is hard coded to 127.0.0.1
[ 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