axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajith Ranabahu <ajith.ranab...@gmail.com>
Subject Re: [Axis2] The listener port for dual transport channel
Date Sat, 14 Jan 2006 08:13:29 GMT
Hi,
We actually have such a mechanism (to get the next port if the specified
port is bound already). is it not functioning ?

On 1/14/06, Dong Liu <edongliu@gmail.com> wrote:
>
> Editing axis2.xml is a way to solve that in some static situations. In
> cases that the listened ports of the server are very dynamic, we need to
> consider that what if the predefined port, say 6060, is reserved at the very
> moment of message transport. To make sure the message will be delivered, the
> send should try other port(s). The logic could be
> first try to connect using 6060
> if not successful, try 6060+1, and continue
>
> Cheers,
>
> Don
>
> On 1/13/06, Davanum Srinivas < davanum@gmail.com> wrote:
> >
> > edit axis2.xml
> >
> > On 1/13/06, Dong Liu < edongliu@gmail.com> wrote:
> > > Hi, folks,
> > >
> > > I guess 6060 is currently the default listen port for the callback
> > when
> > > using dual transport channel (options.setUseSeparateListener(true)).
> > > However, exceptions would appear when 6060 has been listened by other
> > > application already. In such case, how to change the port to listen?
> > Can we
> > > have other *robust* mechanism to determine the listening port?
> > >
> > > Cheers,
> > >
> > > Don
> > >
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
>


--
Ajith Ranabahu

Mime
View raw message