Under certain circumstances the LDAPProfileSubsystem may generate NumberFormatException because it's trying to parse an entryUSN value greater than the maximum range of an Integer.
Jan 9 19:16:51 example server: Exception in thread "profileChangeMonitor" java.lang.NumberFormatException: For input string: "2953078550" Jan 9 19:16:51 example server: at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) Jan 9 19:16:51 example server: at java.lang.Integer.parseInt(Integer.java:583) Jan 9 19:16:51 example server: at java.lang.Integer.<init>(Integer.java:867) Jan 9 19:16:51 example server: at com.netscape.cmscore.profile.LDAPProfileSubsystem.readProfile(LDAPProfileSubsystem.java:153) Jan 9 19:16:51 example server: at com.netscape.cmscore.profile.LDAPProfileSubsystem.run(LDAPProfileSubsystem.java:488) Jan 9 19:16:51 example server: at java.lang.Thread.run(Thread.java:745)
A possible solution is to use BigInteger instead of Integer.
I'm on this.
attachment pki-ftweedal-0149-Use-BigInteger-for-entryUSN.patch
Fixed in master:
Moving to 10.3 critical based upon associated bug
fix corrected the behavior when having high entryusn values in the o=ipaca ipa's dogtag backend, no more exception, and proper CA start, thanks.
Replying to [comment:4 edewata]:
Fixed in master: * 79c6d70a8434cf52f9bac8bfa0367876baccb054
Cherry-picked to DOGTAG_10_3_BRANCH:
Metadata Update from @edewata: - Issue assigned to ftweedal - Issue set to the milestone: 10.3.10
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/2699
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.