Well, before I get there, I have to come up with a faster way to handle RPC
than stuffing each element and reading each off: The system I'm going
against is a large RPC application with some 200 functions. My hope is to
use sessions and threads to allow a user to page thru query results, say 20
or so at a time. The thread should keep open the RPC session and the
cursor location. The session should let me reattach a user to his/her old
query. We'll see...
Adam Gifford wrote:
>Thad Humphries wrote:
>
>> >> i forgot to mention top only reports 73m allocated by the java process.
>> >
>> >what happens with your outofmemory exceptions when you -mx200m? I bet they
>> >go away.
>>
>> I was running out of memory on my server trying to do tricks with images
>> like Hunter does in Ch. 6. I had to set -Xmx64m for one image (these 200
>> dpi image documents over which I must database info). Fearing what a
>> server would require with dozens of users accessing these documents, I
>> rewrote my servlet as an applet. That works champ.
>>
>> My next servlet adventure should be a database query system. I'm hoping
>> memory won't be such an issue.
>
>well, assuming you aren't doing reports that take 10k items and do all sorts
>of queries based on them and do other logic and stuff, i don't think it will
>be a problem. I'm just waiting for it to crash our windows users netscape /
>ie sessions. we managed to get it to return 5k of the data items, and that
>results in 5.1mb of html :) all raw data besides some table formatting stuff.
--------------------------------------------------------------------------
Thad Humphries "Microsoft... What do you want
Software Engineer (aka, Nerd) to reinstall today?"
Phone: 540/675-3015, ext. 225 - Unknown
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
