[
https://issues.apache.org/jira/browse/COUCHDB-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Bisbee reopened COUCHDB-11:
-------------------------------
Yes, I do mean to reopen this ticket from so long ago. :)
The same mochiweb error is getting printed, but so are a bunch of erlang dumps.
A lot of the dumps aren't clearly linked to the port already being bound to.
The cause of the issue becomes non-obvious for the uninitiated and it would be
a lot nicer for the user to just have a "that port is in use" message with
couch exiting immediately.
Cheers.
> CouchDB should handle errors when opening port gracefully
> ---------------------------------------------------------
>
> Key: COUCHDB-11
> URL: https://issues.apache.org/jira/browse/COUCHDB-11
> Project: CouchDB
> Issue Type: Bug
> Reporter: Noah Slater
> Priority: Minor
>
> ATM CouchDB crashes loud and hard when it tries to open a port that is not
> available. There should be some error handling code in place that produces
> a nice message like so:
> "Could not open port %d: %s" % (port_number, message)
> Obviously, the above is written in Python - but you get the idea.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
