SOAPpy port reuse

[Maurice LING]

Hi,

I have a problem:

1. Assuming that my application is a SOAP server that uses SOAPpy,
2. I am given port 35021 for use.

What I normally do (simply) is:

functionlist = [<some exposed functions>]
import SOAPpy
server = SOAPpy.SOAPServ er((<some host>, 35021))
for func in functionlist: server.register Function(func)
server.serve_fo rever()

My question is: How can I shutdown this server and reuse port 35021 when
my functionlist changes?

Currently, after killing the python process which runs this SOAP server,
the port (35021 in this case) cannot be re-used, as though it is still
phantom-ly bounded to some process (which should have been killed).

Thanks in advance.

Cheers
maurice

[Diez B. Roggisch]

Maurice LING schrieb:

Hi,

I have a problem:

1. Assuming that my application is a SOAP server that uses SOAPpy,
2. I am given port 35021 for use.

What I normally do (simply) is:

functionlist = [<some exposed functions>]
import SOAPpy
server = SOAPpy.SOAPServ er((<some host>, 35021))
for func in functionlist: server.register Function(func)
server.serve_fo rever()

My question is: How can I shutdown this server and reuse port 35021 when
my functionlist changes?

Currently, after killing the python process which runs this SOAP server,
the port (35021 in this case) cannot be re-used, as though it is still
phantom-ly bounded to some process (which should have been killed).

It shouldn't be that way. Either you still have some process lying
around hogging the port. Or the OS needs a while to re-enable the port
for allocation. That happened to me quite a few times.

Shutting down gracefully might speed up things I guess.

Diez

[Maurice LING]

Diez B. Roggisch wrote:

Maurice LING schrieb:

>Hi,

I have a problem:

1. Assuming that my application is a SOAP server that uses SOAPpy,
2. I am given port 35021 for use.

What I normally do (simply) is:

functionlist = [<some exposed functions>]
import SOAPpy
server = SOAPpy.SOAPServ er((<some host>, 35021))
for func in functionlist: server.register Function(func)
server.serve_f orever()

My question is: How can I shutdown this server and reuse port 35021
when my functionlist changes?

Currently, after killing the python process which runs this SOAP
server, the port (35021 in this case) cannot be re-used, as though it
is still phantom-ly bounded to some process (which should have been
killed).

It shouldn't be that way. Either you still have some process lying
around hogging the port. Or the OS needs a while to re-enable the port
for allocation. That happened to me quite a few times.

Shutting down gracefully might speed up things I guess.

I am under the impression that SOAPpy.SOAPServ er.serve_foreve r() is an
"endless" loop. I had been suggested to see if there is a method of
SOAPpy.SOAPServ er (which I can call through a wrapper function in
functionlist) that can enable me to gracefully shutdown the server.

Any advice?

Thanks
Maurice

[Piet van Oostrum]

>>>>Maurice LING <ma*********@ac m.org(ML) wrote:

>MLHi,
MLI have a problem:

>ML1. Assuming that my application is a SOAP server that uses SOAPpy,
ML2. I am given port 35021 for use.

>MLWhat I normally do (simply) is:

>MLfunctionli st = [<some exposed functions>]
MLimport SOAPpy
MLserver = SOAPpy.SOAPServ er((<some host>, 35021))
MLfor func in functionlist: server.register Function(func)
MLserver.serve _forever()

>MLMy question is: How can I shutdown this server and reuse port 35021 when my
MLfunctionli st changes?

>MLCurrently, after killing the python process which runs this SOAP server,
MLthe port (35021 in this case) cannot be re-used, as though it is still
MLphantom-ly bounded to some process (which should have been killed).

This phenomenon is explained here:
http://hea-www.harvard.edu/~fine/Tech/addrinuse.html
or the Unix socket FAQ (http://www.faqs.org/faqs/unix-faq/socket/) 2.7

Normally the solution is to set the SO_REUSEADDR option in the socket (the
original one) before binding it:
s.setsockopt(so cket.SOL_SOCKET ,socket.SO_REUS EADDR,1)

However, SOAPPy does that already so it should work.
--
Piet van Oostrum <pi**@cs.uu.n l>
URL: http://www.cs.uu.nl/~piet [PGP 8DAE142BE17999C 4]
Private email: pi**@vanoostrum .org

[Gabriel Genellina]

En Sun, 18 Nov 2007 11:17:42 -0300, Maurice LING <ma*********@ac m.org>
escribi�:

Diez B. Roggisch wrote:

>Maurice LING schrieb:

>>My question is: How can I shutdown this server and reuse port 35021
when my functionlist changes?

Shutting down gracefully might speed up things I guess.

I am under the impression that SOAPpy.SOAPServ er.serve_foreve r() is an
"endless" loop. I had been suggested to see if there is a method of
SOAPpy.SOAPServ er (which I can call through a wrapper function in
functionlist) that can enable me to gracefully shutdown the server.

serve_forever is inherited from SocketServer.Ba seServer and it's just an
infinite loop calling self.handle_req uest() over and over.
You have to break out of the loop somehow and call self.server_clo se().
Something like this (untested):

def serve_forever(s elf):
while not self.some_flag_ to_indicate_it_ has_to_stop:
self.handle_req uest()
self.server_clo se()

--
Gabriel Genellina