dogtagpki

#2568 Freeipa on ARM - OpenJDK vs. Oracle JDK - OpenJDK slow
Closed: wontfix Opened by wdh@dds.nl.

Closed: wontfix
Reopen Issue

Starting FreeIPA (4.4.2) using the default installation (running OpenJDK)
starting FreeIPA takes a painfull 15 minutes (afterward, it all just works
fine):

[root@rpi2 sysconfig]# time ipactl start
Starting Directory Service
Starting krb5kdc Service
Starting kadmin Service
Starting named Service
Starting ipa_memcached Service
Starting httpd Service
Starting ipa-custodia Service
Starting ntpd Service
Starting pki-tomcatd Service
Starting ipa-otpd Service
Starting ipa-dnskeysyncd Service
ipa: INFO: The ipactl command was successful
real    15m40.638s
user    0m33.095s
sys    0m1.910s

Using Oracle Java (taken from http://www.oracle.com/technetwork/java/javase/dow
nloads/jdk8-downloads-2133151.html) give a huge performance improvement:

Now, after installing Oracle Java and changing JAVA_HOME in
/etc/sysconfig/pki-tomcat to:
#JAVA_HOME="/usr/lib/jvm/jre-1.8.0-openjdk"
JAVA_HOME="/opt/jdk1.8.0_111/jre"
[root@rpi2 sysconfig]# time ipactl start
Starting Directory Service
Starting krb5kdc Service
Starting kadmin Service
Starting named Service
Starting ipa_memcached Service
Starting httpd Service
Starting ipa-custodia Service
Starting ntpd Service
Starting pki-tomcatd Service
Starting ipa-otpd Service
Starting ipa-dnskeysyncd Service
ipa: INFO: The ipactl command was successful
real    2m14.823s
user    0m33.400s
sys     0m1.730s

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

Fedora ARM 25
java-1.8.0-openjdk-headless-1.8.0.111-3.b16.fc25.armv7hl
FreeIPA 4.4.2

How reproducible:

Changing JAVA_HOME in /etc/sysconfig/pki-tomcat to:
#JAVA_HOME="/usr/lib/jvm/jre-1.8.0-openjdk"
JAVA_HOME="/opt/jdk1.8.0_111/jre"

Steps to Reproduce:

1. stop IPA (ipactl stop)
2. change JAVA_HOME
3. start IPA and measure time

Actual results:

Using Oracle JDK IPA (pki-tomcat that is) will start appr. 6 times faster

Expected results:

More or less same performance using OpenJDK

Additional info:

Test done on Rapsberry Pi 3b

Hi, thanks for trying Dogtag. Dogtag is primarily developed on Fedora and currently it's working fine with OpenJDK. Currently we don't have the resource to test/troubleshoot it on Raspberry Pi, so any contributions would be appreciated. Thanks.

ACK

Metadata Update from @wdh@dds.nl:
- Issue set to the milestone: FUTURE

Closing due to inactivity. Patches still welcome, please reopen if you have some patches you would like to share.

Thanks!

Metadata Update from @ftweedal:
- 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: wontfix

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.2 (was: FUTURE)

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/2688

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.
Metadata
None
None
None
None
Normal
None
defect
General
Community
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.