Memory Problem

[neha gowda]

Hi All,

Our functional requirement is to fetch around 50,000 records from the Database, form an xml of these records
and flush it through an outputstream using the servlet.
The data is then displayed in an Excel sheet.

We are using Websphere 5.0 .In the server side we have a session bean which fetch the records and holds them in a value object.
This works fine for around 15000 records.

But if the data exceeeds,

But while returning from the EJB , we get the following exception.
[10/7/04 15:41:07:969 IST] 732afa74 SystemErr R java.rmi.RemoteException: CORBA NO_MEMORY 0x4942f984 No; nested exception is:
org.omg.CORBA.NO_MEMORY: Unable to write value : null minor code: 4942F984 completed: No


We are aware of the fact that this is because of huge data.We tried retrieving chunks of data, instead of retrieving full, at a time.But this doen't help.

Any idea, regarding the above problem would be of great help.

[Shailesh Chandra]

try increasing heap memory size of websphere.
hope this will solve your problem.
Already a very good thread is going on heap memory in this forum

[neha gowda]

Hi,

I tried increasing the heap memory , but, It did not solve the problem. :-(



regards
Neha

[Shailesh Chandra]

I have no idea about your prob ..

but 15000 is for value object is too much.

did you try cacherowset..............its recommendation in j2ee design patterns if data trasfer is high try to use cacherowset.

any way try to look other forums also for your problem.

regards...............

[neha gowda]

We could solve this problem by changing the JVM settings.
We have used the following settings now.

Java VM arguments (Generic JVM Arguments)
-Xms256m -Xmx1024m

Also by setting the Initial HeapSize = 256
And Max Heap Size = 1024

[Shailesh Chandra]

but as u said change in heap memory was not working earlier.

is there something additional ??

any way atleast your problem is solved

[neha gowda]

Hi,

There was some mistake in setting the Heap.
One of the team members crossed checked and rectified it.
Nothing additional.
Thanks for the Help Mr. Shailesh.

Have a great day!

Neha

[samou Mouloud]

we cannot say anything: use Tivoli performance viewer or launch your server with -verbosegc and analyze the log.
If you have a stack overflow error in your trace, try increasing max thread stack size with -Xss=1 or 2M
Mouloud

[Shailesh Chandra]

I agree Tivoli helps lot to analyse various aspect in application...