Name: gm110360 Date: 11/05/2002


FULL PRODUCT VERSION :
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01)
Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

generally all 1.4.x versions & Linux

FULL OPERATING SYSTEM VERSION :kernel 2.4.10,
glibc-2.2.4-77, SuSE 7.3


A DESCRIPTION OF THE PROBLEM :
Perhaps not really a bug, but I don't think that this should
be normal:

  user@...~> ulimit -a
  ...
  virtual memory (kbytes) unlimited

  user@...~> java -version
  java version "1.4.1_01"
  Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.1_01-b01)
  Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode)

That's ok. But:

  user@...~> ulimit -a
  ...
  virtual memory (kbytes) 200000 (200MB)!!!

  user@...~> java -version
  Error occurred during initialization of VM
  java.lang.OutOfMemoryError: unable to create new native thread

200MB of virtual memory is not enough to only show the
version number of java?


REGRESSION. Last worked in version 1.3.1

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
see description

I've set the limits for users using the file
/etc/security/limits.conf, adding this line:

@users hard as 200000

EXPECTED VERSUS ACTUAL BEHAVIOR :
Is it really necessary to arise the virtual memory limit to
more than 200MB only to get version information? This is a
server where students "play" with programs using CPLEX (LP
solver) so we have to limit the virtual memory because of
erroneous programs using all memory (we had lot of system
crashes before).

ERROR MESSAGES/STACK TRACES THAT OCCUR :
see description

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER WORKAROUND :
No limits for virtual memory.
(Review ID: 166328)
======================================================================