It could be more effective to actually file a bug, refer to it here
for later reference and move on to the issue tracker for the diagnose/
fixing part.
-Alexis
On Apr 30, 2008, at 9:24, glassfish_at_javadesktop.org wrote:
> How quickly do the waters become muddy. This thread now has multiple
> issues posted to it, which renders it pretty much useless to anyone
> trying to actually track down and fix a bug in Glassfish.
>
> The original issue that this thread was about has nothing whatever
> to do with database connections or deadlocked threads. My
> application doesn't even hit a database. The symptoms, and hints as
> to the source of the problem are to be found in my original post at
> the top of this thread. I wish the Glassfish team luck fixing that
> issue, because I very much believe it to be a bug in Glassfish,
> unlike deadlocked threads which is more likely to be application code.
> [Message sent by forum member 'kevinmacdonald' (kevinmacdonald)]
>
> http://forums.java.net/jive/thread.jspa?messageID=272165
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>