My first thought is to run the app using NetBeans profiler. Take a
snapshot before and after doing transactions and then use the tool to
diff them and find the leak. Sounds easy but I'm fighting with
exceptions and 5 minute load times. I don't know what the heck it is
doing. I'll keep at it...
Ryan de Laplante wrote:
> Hi,
>
> I'm investigating a heap dump of GlassFish and my application that has
> recently had "out of heap space" errors twice over the last few
> weeks. I noticed that there are about 85 web session instances
> hanging around. Some are successful transactions, others incomplete
> or failed transactions. There doesn't seem to be a pattern and I know
> that thousands of other transactions have completed without leaking
> their sessions.
>
> I'm wondering if anyone has a clue what I should be looking for?
> Also, these sessions are no more than a few KB each so I can't see
> this causing my out of heap space exceptions. I'm having hard time
> knowing where to start or what to look for.
>
>
> Thanks,
> Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>