axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: AXIS2: fixing client sockets used
Date Thu, 24 Mar 2011 15:24:32 GMT
If I understand your requirement correctly, you would like Axis2 to
bind the local side of the HTTP connection to a fixed port (using
Socket#bind [1]). This is not supported for two reasons:

1. Axis2 uses commons httpclient which AFAIK doesn't support this.
2. The tuple (src IP, src port, dst IP, dst port) must be unique for a
each TCP connection. Binding to a fixed port would mean that you could
open at most one connection to the destination. This is generally not
what you want for HTTP.



On Thu, Mar 24, 2011 at 06:37, Bhat B, Niranjan (NSN - IN/Bangalore)
<> wrote:
> Hi Axis2 users,
> I have been asked to fix the socket used by the axis2 stubs (which is
> random currently )to a fixed socket.
> Details:
> Everytime my axis2 client stubs tries to contact the webservice( again
> running on axis2) it opens a random port on the client IP on which it
> sends request to the server IP and a fixed server port.
> I want to fix this random port on the client IP to a fixed port, so that
> my product can be hardened.
> Also I am running this client from within Tomcat6 as a web application.
> regards,
> Niranjan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message