Bug 34390

Summary:	glibc-2.2.2-7.i386 causes problem with ApacheJServ & JVM's
Product:	[Retired] Red Hat Raw Hide	Reporter:	Philip Senechal <psenechal>
Component:	glibc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED NOTABUG	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	fweimer
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-04-02 23:09:58 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 Philip Senechal 2001-04-02 23:09:54 UTC

glibc-2.2.2-7.i386 causes problem with ApacheJServ using IBM JVM v1.2.2, 
Sun's JVM v1.3, and Sun's beta JVM v1.3.1. The glibc that came on the 
Wolverine image worked fine as long as you "side-graded" to the i386 
version instead.  Running up2date and upgrading to glibc-2.2.2-7.i386 
causes an error in mod_jserv.log:

ajp12 cannot connect to 127.0.0.1

As a sidenote to this, the i686 version of the glibc (all versions) 
produces the same error. I understand this may be attributed the JVMs 
being used however.

Comment 1 Bill Nottingham 2001-04-03 04:13:52 UTC

The JDKs are broken. Set LD_ASSUME_KERNEL=2.2.5 and they should work OK.