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
jon * wrote:
> > what is the significane of the exceptions coming from jserv as opposed to my
> > code as they used to before i upped the memory ? (from default 16m)
>
> nothing really. essentially, the jvm tries execute some code and it is
> failing because it doesn't have enough stack space wit
Run a profiler. Use jdk1.2 to get best results with the profilers.
optimizeit (my favorite)
jinsight <http://www.alphaworks.ibm.com> (search on jinsight)
>Running one of our servlets (which generates a report based on a bunch
>of jdbc queries), we get
>a out of memory exception
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 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 imag
> what is the significane of the exceptions coming from jserv as opposed to my
> code as they used to before i upped the memory ? (from default 16m)
nothing really. essentially, the jvm tries execute some code and it is
failing because it doesn't have enough stack space within its process to
exec
Adam Gifford wrote:
> jon * 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.
> >
> > -jon
> >
> >
>
> what is the significane of the exceptions coming from jserv a
jon * 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.
>
> -jon
>
>
what is the significane of the exceptions coming from jserv as opposed to my
code as they used to before
> 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.
-jon
To subscribe:[EMAIL PROTECTED]
To unsubscribe: [EMAI
jon * wrote:
> > Running one of our servlets (which generates a report based on a bunch
> > of jdbc queries), we get
> > a out of memory exception if the database is too large. We used to get
> > the out of memory exception in our code before we added teh -mx100m
>
> Running one of our servlets (which generates a report based on a bunch
> of jdbc queries), we get
> a out of memory exception if the database is too large. We used to get
> the out of memory exception in our code before we added teh -mx100m
> option. Now we get it in jse
Running one of our servlets (which generates a report based on a bunch
of jdbc queries), we get
a out of memory exception if the database is too large. We used to get
the out of memory exception in our code before we added teh -mx100m
option. Now we get it in jserv. We are not running out of
12 matches
Mail list logo
