[
https://issues.apache.org/jira/browse/DAEMON-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668950#action_12668950
]
Adrian Woodhead commented on DAEMON-12:
---------------------------------------
I can confirm that, as mentioned in the e-mail thread, commenting out the
following lines in unix/native/jsvc-unix.c resolves the issue:
{noformat}
if (set_caps(0)!=0) {
log_debug("set_caps (0) failed");
return(4);
}
{noformat}
(lines 503-506 in 1.0.1 source).
It would be great if a solution to this could be found and incorporated into a
future release.
> [daemon] java fails to bind on port 80
> --------------------------------------
>
> Key: DAEMON-12
> URL: https://issues.apache.org/jira/browse/DAEMON-12
> 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.
