Okay, actually I figured it out.
IBM db2 was configured without enough application connections and
application heap. So the DB was running out of memory and valid
connections, not orion.
It is my impression that each servlet has at least 1 connection to the
database, is this correct if I use pooled connections?
Jeff
Oguz Kologlu wrote:
>
> Jeff,
>
> You would need to have a very large page to cause an out of memory error.
> Out of memory errors are generally related to overflows due to eg infinite
> loops. You should check your code first.
>
> Also I've found IBM's JVM a lot more helpful with error messages. You might
> want to try it out.
>
> Oz
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of El Jeffo
> Sent: Monday, 22 October 2001 7:06 AM
> To: Orion-Interest
> Subject: ApplicationHeap
>
> I just wanted to know, if orion serves pages from a servlet that complains
> about not enough memory in the application heap, is it just a
> "java" option where I do on a solarios java 1.3.1 :
>
> java -Xmx128M -Xms48m -jar orion.jar
>
> to increase from the defaults of -Xmx64m -Xms2m
>
> that's 64meg max, 2 meg start
>
> or are there other orion options I missed?
>
> Much thanks!
>
> Jeff
S/MIME Cryptographic Signature
