0001038: Cannot start multiple Resin Windows services due to fixed httpd.exe socketwait port 2050 / 33660

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001038

[Resin]

minor

always

04-06-06 07:34

04-06-06 09:32

Reporter

wet745

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

3.0.18

Summary

0001038: Cannot start multiple Resin Windows services due to fixed httpd.exe socketwait port 2050 / 33660

Description

I cannot start 2 Resin services on the same Windows 2000 SP4 server. The one service runs only when the other one is not running.
When I start the 2nd service, the following message is written to jvm.log:

can't bind socket
stopping Resin (status 1)

Analysis has shown that on Windows 2000 SP4, httpd.exe uses the fixed port 2050 for the keepalive connection to its Java child process (socketwait parameter). The 2nd httpd.exe process sees the port being blocked by the first process.

The problem does not occur with httpd.exe of release 3.0.14. This version uses a free port instead of the fixed one.

On Windows 2003 Server SP1, port 33660 is used instead, but the problem is the same.

On Windows XP SP2, the problem does not occur.

Additional Information

The problem has been reported on http://www.caucho.com/support/resin-interest/0602/0051.html. [^]

Attached Files

Relationships

Notes
(0001026) ferg 04-06-06 09:32	missing memset for the sockaddr_in.

Issue History
Date Modified	Username	Field	Change
04-06-06 07:34	wet745	New Issue
04-06-06 07:36	wet745	Issue Monitored: wet745
04-06-06 09:32	ferg	Note Added: 0001026
04-06-06 09:32	ferg	Assigned To	=> ferg
04-06-06 09:32	ferg	Status	new => closed
04-06-06 09:32	ferg	Resolution	open => fixed
04-06-06 09:32	ferg	Fixed in Version	=> 3.0.19

Mantis 1.0.0rc3[^]

30 total queries executed.
26 unique queries executed.