Bug 1018394 - tomcat fails to start on ipv6
Summary: tomcat fails to start on ipv6
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tomcat6
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Knox
QA Contact: tomcat-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-11 20:55 UTC by Ade Lee
Modified: 2015-11-02 00:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-20 18:35:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ade Lee 2013-10-11 20:55:19 UTC
Description of problem:

On a server on which ipv6 is enabled and ipv4 is not enabled - and the ipv4 localhost is configured in /etc/hosts, tomcat fails to start because the shutdown port will attempt to bind to the ipv4 localhost.

A better approach might be to cycle through both ipv4 and ipv6 interfaces - and only fail if neither is available.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2013-10-15 01:33:43 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 David Knox 2013-11-04 19:08:29 UTC
tomcat assumes localhost so perhaps a better solution is to use InetAddress.getLocalHost().getHostAddress()

Comment 5 David Knox 2014-10-20 18:21:31 UTC
unfortunately, tomcat6-6.0.24 hard codes 'localhost' in several places.

there has been success on ipv6-only systems when localhost is mapped to the ipv6 address.

Comment 6 RHEL Program Management 2014-10-20 18:35:48 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.