Hi,
We've been running one of our web systems using SilverStream.
We've had this system for about 4 years and very little code has
changed.
In the last 3 months the server has been going down and produces a
java.lang.OutOfMemoryError exception.
Has anyone got any explanation as to why this is happening when little
code has changed??
One idea is that one of the function allows users have been adding new
records for 4 years and we allow users to find those records and we
have now over 130,000 records.
The find function allows users to select a criteria to narrow the
number of records returned, but could it be they are returning too
many records from the database and could that be killing the server???
If anyone has any idea of what else could be causing this then I would
appreciate it.
Regards
Simon
John - 24 Apr 2005 14:51 GMT
Have you tried to retrieve all the results yourself and see if you can
crash the server?
If yes, and it didn't crash, chances are that the server and the client
are communicating
using ObjectInput/OutputStream the wrong way and the memory usage
increases very
fast (especially now that you have more records), and no memory is GC-ed
because
the references to objects are maintained by the stream controllers.
> Hi,
>
[quoted text clipped - 22 lines]
> Regards
> Simon