RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1036813 - Long term memory leak when using PKCS11 and JCE exceeds 32 bit process address space
Summary: Long term memory leak when using PKCS11 and JCE exceeds 32 bit process addres...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.7.0-openjdk
Version: 6.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: Lukáš Zachar
URL: http://bugs.sun.com/view_bug.do?bug_i...
Whiteboard:
: 1133760 (view as bug list)
Depends On: 831734
Blocks: 1028966 1040049
TreeView+ depends on / blocked
 
Reported: 2013-12-02 16:37 UTC by Alon Bar-Lev
Modified: 2018-12-06 15:31 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-10 14:44:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1175903 0 None None None Never
Red Hat Product Errata RHBA-2013:1810 0 normal SHIPPED_LIVE java-1.7.0-openjdk bug fix update 2013-12-10 19:43:38 UTC
openjdk bug system JDK-6887619 0 None None None Never
openjdk bug system JDK-6927479 0 None None None Never

Description Alon Bar-Lev 2013-12-02 16:37:36 UTC
From bug#1028966 comment#26

(In reply to Andrew Haley from comment #26)
> I can confirm that the memory leak is in the PKCS11 library and is probably
> this bug:
> 
> http://bugs.sun.com/view_bug.do?bug_id=6913047
> 
> After more than 12 hours running there is no increase in memory consumption
> with PKCS11 disabled. I think this is enough to prove that PKCS11 is the
> cause of the problem.
> 
> Disabling PKCS11 is a suitable workaround for the rime being.

This is unique to rhel, as it was decided to modify default provider uses PKCS11 provider to use nss bug#831734, as result all java applications are effected.

Please also note at bug#905128 comment#7, changing default behavior of java is very sensitive and should be avoided.

Please disable the use of PKCS11 provider as default until all problems with PKCS11 provider and nss are resolved.

Comment 16 errata-xmlrpc 2013-12-10 14:44:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1810.html

Comment 17 James Livingston 2014-08-26 23:53:01 UTC
*** Bug 1133760 has been marked as a duplicate of this bug. ***


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