Bug 175268

Summary: Missing symlinks from java-1.4.2-ibm-devel cause tomcat5 installation to fail
Product: [Retired] Red Hat Application Server Reporter: Carsten Clasohm <clasohm>
Component: tomcatAssignee: Fernando Nasser <fnasser>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 16:50:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Carsten Clasohm 2005-12-08 12:38:17 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Description of problem:
When installing tomcat5 from the Application Server channel, the %post script relies on /usr/lib/jvm-exports/java to exist. When using the java-1.4.2-ibm from the RHEL4 Extras channel, this path does not exist, resulting in a broken Tomcat installation.


Version-Release number of selected component (if applicable):
tomcat5-5.5.9-1jpp_5rh

How reproducible:
Always

Steps to Reproduce:
1. Install java-1.4.2-ibm-1.4.2.2-1jpp_10rh
2. Install tomcat5-5.5.9-1jpp_5rh


Actual Results:  During installation, you will get this error message:

/usr/bin/build-jar-repository: error: JVM_LIBDIR /usr/lib/jvm-exports/java does not exist or is not a directory
error: %post(tomcat5-5.5.9-1jpp_5rh.noarch) scriptlet failed, exit status 5

When you try to start the tomcat5 service, you will get this error message:

/usr/bin/rebuild-jar-repository: error: JVM_LIBDIR /usr/lib/jvm-exports/java does not exist or is not a directory


Expected Results:  The path /usr/lib/jvm-exports/java should be created by one of the packages that tomcat5 requires.


Additional info:

Installing the package java-1.4.2-ibm-devel-1.4.2.2-1jpp_10rh and then reinstalling tomcat5 fixes this problem, as java-1.4.2-ibm-devel provides a symbolic link for /usr/lib/jvm-exports/java. Either this symlink should be moved into java-1.4.2-ibm, or the package requirements of tomcat5 should be changed  to include java-1.4.2-ibm-devel.