#2560 [RFE] Tomcat 8.5 support
Closed: fixed 6 years ago Opened 7 years ago by tjaalton.

Debian recently switched to tomcat 8.5 which broke Dogtag. First issue that I found was that Http11Protocol is no more, need to use Http11NioProtocol. Fixing that it then fails with:

02-Dec-2016 11:26:05.270 SEVERE [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[HTTP/1.1-8443]]
 org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8443]]
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:113)
        at org.apache.catalina.core.StandardService.initInternal(StandardService.java:549)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
        at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:875)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:606)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)
Caused by: java.lang.NoClassDefFoundError: org/apache/tomcat/util/net/ServerSocketFactory
...

Looks like tomcat 8.5 breaks the build as well for both dogtag
and tomcatjss. Debian freeze is in Jan 5th, this needs to be fixed well before x-mas just to be on the safe side.


There will be no Tomcat 8.0 any longer on newer Fedora/Debian, so there's no workaround other than migrating to Tomcat 8.5.

Per CS/DS Meeting of 12/12/2016: 10.3 - critical

DISCUSSION: While it is unlikely that a solution can be Debian's January 5, 2017 deadline, there will
be an attempt to provide a solution for this issue sometime in January 2017.

Changes in master:

  • 843cbeed6ddab8f1883abce47a8c45e0fa14fc5a

This depends on JSS/Tomcat JSS enhancement to support non-blocking IO.
https://pagure.io/tomcatjss/issue/1

ACK

Reluctantly, due to time constraints and resources, I believe that this is the most appropriate milestone and priority.

Metadata Update from @tjaalton:
- Issue assigned to edewata
- Issue set to the milestone: FUTURE

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: 10.5 (was: FUTURE)

6 years ago

FYI, dogtag-pki and freeipa have been demoted on Ubuntu so that they won't block tomcat8 anymore, also means that 17.10 will not have them.

https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1716842

Metadata Update from @mharmsen:
- Issue priority set to: critical (was: blocker)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

Metadata Update from @edewata:
- Issue priority set to: critical (was: major)

6 years ago

NSS SQL database dependency for Fedora 28 will be addressed in ticket #167.

Metadata Update from @edewata:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

PKCS12 incompatibility will be addressed in ticket #2945.

The support for NIO connector will be implemented in ticket #203.

Metadata Update from @edewata:
- Issue priority set to: blocker (was: critical)

6 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.6.0 (was: 10.6)
- Issue status updated to: Closed (was: Open)

6 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2680

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata