java.lang.outofmemory - but where?
java.lang.outofmemory - but where?
(OP)
Hi,
Were running a Silverstream 3.75 cluster on Win2k connecting to a MS-SQL7 DB.
My problem is that both servers in the cluster keep crashing with a java.lang.outofmemory error. Both our servers have at least 1gb of ram and are started with +Xmx1024 to allocate memory to the java heap.
We have checked all our code, queries etc and there is nothing obviously wrong. Our site gets around 50,000 page requests a day and I am starting to think Silverstream cannot handle this kind of traffic!
Any advice much appreciated
Cheers
Wilbo
Were running a Silverstream 3.75 cluster on Win2k connecting to a MS-SQL7 DB.
My problem is that both servers in the cluster keep crashing with a java.lang.outofmemory error. Both our servers have at least 1gb of ram and are started with +Xmx1024 to allocate memory to the java heap.
We have checked all our code, queries etc and there is nothing obviously wrong. Our site gets around 50,000 page requests a day and I am starting to think Silverstream cannot handle this kind of traffic!
Any advice much appreciated
Cheers
Wilbo
RE: java.lang.outofmemory - but where?
RE: java.lang.outofmemory - but where?
The solution I'm using is to restart periodically the SS service ... but I'm not very happy of this ...
RE: java.lang.outofmemory - but where?
The more details I can get, the more information I can supply to ISV support. We are determined to be able to deliver our customers a solution which can run on W2K servers, so we will be providing Novell OptimizeIt snapshots this week.
RE: java.lang.outofmemory - but where?
We are running 3.73 on W2K, though at a low traffic volume. We also experienced irregular behaviour - lock-ups, server bounces. Our solution, and I stress this may be of no use to you, was to have a scheduled object which rebooted the AGServer every night. Since then no problems. Go figure.
Cheers.
RE: java.lang.outofmemory - but where?
We managed to solve the problem by doing the following:-
1. Changing all concatenated strings to Stringbuffers.
2. Applying 1570-02.jar patch from Silverstream Support.
3. Checking the server logs for 404 errors and resolving any pages which could not be found (too many of these 404s will bring a server down very quickly).
By doing all the above, my server which lasted a couple of hours now stays stable for at least a 2 weeks.
Cheers
Wilbo
RE: java.lang.outofmemory - but where?
JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
Not sure if anybody else have similar problem. We are using jConnect 5.2 for Sybase Enterprise.
RE: java.lang.outofmemory - but where?
I am having the same issue regarding SilverStream 3.73 out of memory error. I have to restart my application servers daily to avoid server crash.
In your previous posting you gave some suggestions regarding this memory issue:
1. changing all concatenated strings to StringBuffers
I have a question regarding #1. Are you talking about append all the Strings to StringBuffers? Please provide me with some examples.
Any help would be greatly appreciative.
Thanks.
RE: java.lang.outofmemory - but where?
Have a look at: http://www.javaworld.com/javaworld/jw-03-2000/jw-0324-javaperf_p.html
Cheers.
RE: java.lang.outofmemory - but where?
Do you know where I can get the 1570-02.jar patch? I talked to Novell techincal support and they said that each patch is customer specific. I wanted to read more about this patch but I was unable to find any document on it.
Our main issue regarding memory leakage is that the application server's memory, at times with no process running, start to increase above 1 gig which in turn crash the server. I can't pin point where or why the memory would increase even though there are no processes running on the application server. As far as I know, we have one object that is triggered every 20 minutes and all it does it simple SQL query and update to database. I monitored this object daily and it doesn't seem that this is the cause of memory leakage, but I am not ruling out this object yet as being the cause.
Do you have any idea why this is happening?
RE: java.lang.outofmemory - but where?