This page contains an archived post to the Design Forum (formerly called the Flexible Java Forum) made prior to February 25, 2002. If you wish to participate in discussions, please visit the new Artima Forums.

Message:

outofmemory

Posted by shree on February 13, 2002 at 1:51 PM

start the java web server with the flwg option

java -Xms128m -Xmx256m ........

> > Hi !
> > I was getting similar problem on java web server 2.0 on Nt 4.0 with mysql database. I changed the heap size setting of the virtual machine and it started to work.U can also try to increase the initaial heap size of JVM by giving it the -mx argument. I think it will stop giving the outofmemory error.

> > > Hi,

> > > Did anyone come up with a solution for this problem???

> > > Regards,
> > > - Morten

> > > > Hello Everybody,
> > > > We are facing a problem of java.lang.OutOfMemory Exception.
> > > > It happens when we are continuously creating and storing object
> > > > in database(ObjectStore). Both our server and client are in java.
> > > > And the server is distributed and is exposed to the client through
> > > > an idl implemented in CORBA(OrbixWeb 3.0).
> > > > We are releasing references whereever needed.
> > > > And also calling runFinalizersOnExit(true).
> > > > Also, the error does not come when continuously large
> > > > objects(containing embedded objects) is stored in the same database
> > > > with objects formed only through jdk.
> > > > Any suggestions for the problem/where to look for the solution?
> > > > Is explicit running of garbage collector recommended(since the
> > > > article says that the design should not be such that it should
> > > > depend on the frequency at which the garbage collector runs)? If
> > > > explicitly run,can the running of java gc be speeded up?(i.e.,
> > > > can we decrease the interval at which it searches as to what to
> > > > garbage collect).