axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Vladov <vladov.ste...@gmail.com>
Subject Re: Axis2 standalone server
Date Tue, 01 Nov 2011 12:01:12 GMT
Hi Vadym,

the way I see it, currently you cannot specify an address to bind the
server socket to. The code that deals with it is
org.apache.transport.http.server.DefaultConnectionListener#run() - as
you can see it only does the following:

serversocket = new ServerSocket(port);

You may extend the default connection listener to add some socket
creation logic, but you will also have to extend the SimpleHttpServer
as there is no way to plug in another implementation of connection
listener (IOProcessor) in there...

Of course you could also file a feature request in axis2.

Regards,
Stefan

On Fri, Oct 28, 2011 at 12:00 AM, Vadym Chepkov <vchepkov@gmail.com> wrote:
> Hi,
> How would one configure axis2 standalone server to bind only to loopback
> interface?
> tomcat connector has "address" parameter, I didn't find anything similar in
> azis2.xml for org.apache.axis2.transport.SimpleAxis2Server
>
>    <!-- ================================================= -->
>     <!-- Transport Ins -->
>     <!-- ================================================= -->
>     <transportReceiver name="http"
>
>  class="org.apache.axis2.transport.http.SimpleHTTPServer">
>         <parameter name="port">8080</parameter>
>         <!-- Here is the complete list of supported parameters (see example
> settings further below):
>             port: the port to listen on (default 6060)
>             hostname:  if non-null, url prefix used in reply-to endpoint
> references                                 (default null)
>             originServer:  value of http Server header in outgoing messages
>                                         (default "Simple-Server/1.1")
>             requestTimeout:  value in millis of time that requests can wait
> for data                                (default 20000)
>             requestTcpNoDelay:  true to maximize performance and minimize
> latency                                   (default true)
>                                 false to minimize bandwidth consumption
by
> combining segments
>             requestCoreThreadPoolSize:  number of threads available for
> request processing (unless queue fills up)  (default 25)
>             requestMaxThreadPoolSize:  number of threads available for
> request processing if queue fills up         (default 150)
>                                        note that default queue never
fills
> up:  see HttpFactory
>             threadKeepAliveTime:  time to keep threads in excess of core
> size alive while inactive                  (default 180)
>                                   note that no such threads can exist
with
> default unbounded request queue
>             threadKeepAliveTimeUnit:  TimeUnit of value in
> threadKeepAliveTime (default SECONDS)                    (default SECONDS)
>         -->
>         <!-- <parameter name="hostname">http://www.myApp.com/ws</parameter>
> -->
>         <!-- <parameter name="originServer">My-Server/1.1</parameter>
>     -->
>         <!-- <parameter name="requestTimeout">10000</parameter>
>       -->
>         <!-- <parameter name="requestTcpNoDelay">false</parameter>
>         -->
>         <!-- <parameter name="requestCoreThreadPoolSize">50</parameter>
>                  -->
>         <!-- <parameter name="requestMaxThreadPoolSize">100</parameter>
>                 -->
>         <!-- <parameter name="threadKeepAliveTime">240000</parameter>
>            -->
>         <!-- <parameter
> name="threadKeepAliveTimeUnit">MILLISECONDS</parameter>            -->
>     </transportReceiver>
> Thank you,
> Vadym
Mime
View raw message