Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 237993 - jre 1.6 fail's to run on RHEL 5.
jre 1.6 fail's to run on RHEL 5.
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: selinux-policy (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2007-04-26 09:52 EDT by Sandeep K. Shandilya
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-26 11:13:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
selinux alert log for a jre 1.6 app (2.56 KB, text/plain)
2007-04-26 09:52 EDT, Sandeep K. Shandilya
no flags Details

  None (edit)
Description Sandeep K. Shandilya 2007-04-26 09:52:30 EDT
Description of problem:
java apps using JRE 1.6 fail to run on RHEL5

Version-Release number of selected component (if applicable):
selinux version that ships with RHEL 5.

How reproducible:

Steps to Reproduce:
Actual results:
The java app fails to run and we have an selinux alert on dmesg
the selinux log is attached to this bugzilla

dsm_om_connsvc32d is the java app.

Expected results:
java applications should run on RHEL5.

Additional info:
Comment 1 Sandeep K. Shandilya 2007-04-26 09:52:30 EDT
Created attachment 153511 [details]
selinux alert log for a jre 1.6 app
Comment 2 Sandeep K. Shandilya 2007-04-26 10:16:26 EDT
jre 1.6 was from www.sun.com.

Is running chcon on jre 1.6 supported? are they any security implications here.
Comment 3 Daniel Walsh 2007-04-26 11:13:45 EDT
No you can make the change.  Change the context and then change use the semanage
command to change the system defaults.

This is a problem with the java libraries.

Please report it as a bug to them.

This link explains the memory detection that SELinux is doing.


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