On 3/8/2010 12:24 PM, [email protected] wrote:
It very much is a deployment/architecture issue. :) I shoulda
mentioned that. Sorry. It's taken longer than anticipated to
convince this client to move into a more enterprise ready architecture
(cost in a down economy). So, I am left to fend off the issues of a
production solution that is not ideal.
Thanx for the insight on the visualvm bugs. I had never looked into
it enough to find them.
They're actually JVM bugs, not VisualVM bugs.
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
