commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <>
Subject [jira] Commented: (DAEMON-12) [daemon] java fails to bind on port 80
Date Fri, 02 Jan 2009 21:39:44 GMT


Mark Thomas commented on DAEMON-12:

I have tested Tomcat 5.5.15 and the jsvc provided with that distro on the following:
- dual processor vmware image
- ubuntu 2.6.27-7-server x84_64
- Sun jdk1.6.0_11 (64 bit)

I do not see the issues reported by the OP.

Given that:
- neither Jean-Frederic nor I can reproduce this
- there are no similar reports I could find in the Tomcat bug database
- there are no similar reports I could find on the users list
this looks like a configuration issue that would be best handled on the users list.

> [daemon] java fails to bind on port 80
> --------------------------------------
>                 Key: DAEMON-12
>                 URL:
>             Project: Commons Daemon
>          Issue Type: Bug
>         Environment: Operating System: Linux
> Platform: PC
>            Reporter: Ostap Bender
>            Priority: Blocker
> Platform is Ubuntu Linux, kernel 2.6.15 amd64 smp on a dual core processor.
> When I start Tomcat with jsvc and the Http connector on port 80 java fails to
> bind on port 80. I added an extra debug statement in set_caps to tell me when
> set_caps is called. In catalina.out I see before java even tries to bind, three
> calls: the first with the value 1216, second with 1024 (CAP_NET_BIND_SERVICE)
> and the last with 0 (downgrade).
> After commenting out set_caps(0) from the jsvc-unix.c Tomcat starts ok.
> What is the reason for the downgrade happening so soon? Is it a race condition
> turned bad by the use of a multiprocessor?
> BTW, the Readme should mention that the module capabilities should be loaded.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message