socket.error: (98, 'Address already in use')

[falbriard]

Dear colleagues,

Trying to setup a socket handler running on the port 25 (inbound SMTP). This process runs fine under Windows. After porting the Jython code to a Linux, I get the following error message at the start-up of the process:

 File "/opt/jython/Lib/socket.py", line 795, in listen
 raise _map_exception(jlx)
  socket.error: (98, 'Address already in use')  

Looks like a previously running code left the port open. Any hints how to fix this error in the socket handler or how to reset the port?
Thanks in advance for advice and feedback.

Regards,
Claude

Claude Falbriard
Developer
AMS Hortolândia / SP - Brazil
phone:    [phone]
cell:         [phone]
e-mail:    claudef@...
blog:        https://w3.tap.ibm.com/weblogs/inovarMF/

Project CallOwn Blue      


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Jython-users mailing list
Jython-users@...
https://lists.sourceforge.net/lists/listinfo/jython-users

[Alan Kennedy-2]

[claude]
> Trying to setup a socket handler running on the port 25 (inbound SMTP).
> This process runs fine under Windows. After porting the Jython code
> to a Linux, I get the following error message at the start-up of the
> process:
>
>     File "/opt/jython/Lib/socket.py", line 795, in listen
>     raise _map_exception(jlx)
>      socket.error: (98, 'Address already in use')  
>
> Looks like a previously running code left the port open. Any hints
> how to fix this error in the socket handler or how to reset the port?

You can see what ports are open, and the state they are in, by using netstat: I think the flags you need on Linux are

netstat -f inet

On windows, use "netstat -ano".

That should tell you if the port is already open by some other process, what that process ID is, and whether it is in a CLOSE state, etc.

If the port is not actually open from another process, is it possible that this is a permissions problem?

I think you need to be running as root to open ports < 1024 on linux.

Alan.


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Jython-users mailing list
Jython-users@...
https://lists.sourceforge.net/lists/listinfo/jython-users