Chris,
This is very helpful. It strongly suggests the issue is memory
management, not JFreeChart.
I'd put my money on bad hardware. Every single time I've seen a
release version of a JVM fail, it's because of bad memory, CPU,
motherboard, or the combination thereof.
I recommend trying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen,
Stephen Caine wrote:
> This is very helpful. It strongly suggests the issue is memory
> management, not JFreeChart.
I'd put my money on bad hardware. Every single time I've seen a release
version of a JVM fail, it's because of bad memory, C
Ken,
This is very helpful. It strongly suggests the issue is memory
management, not JFreeChart.
Thanks,
Stephen
On Jan 23, 2009, at 2:28 PM, Ken Bowen wrote:
Just a datapoint: I have a webapp which does basic graph
construction using JFreeChart which has been running in development
m
Just a datapoint: I have a webapp which does basic graph construction
using JFreeChart which has been running in development mode on a Mac
OS X 10.5.6 under both Tomcat 5.5.26 and 6.0.18 for many months, and
has never produced such a crash.
On Jan 23, 2009, at 1:56 PM, Stephen Caine wrote:
> From: Jonathan Mast [mailto:jhmast.develo...@gmail.com]
> Subject: Re: Java Crash
>
> that is almost certainly an Apple Java issue.
Note also the excessive heap size vs installed RAM. This is guaranteed to
induce serious paging, and I don't know if the MAC OS is robust enoug
Jonathan,
that is almost certainly an Apple Java issue. If by charting, you
mean graphics, then even more so. The Java2D api on Mac still has
bugs that will crash.
I am sorry that I did not specify the charting jsp. We are using the
ones provided by CEWolf (based on JFreeChart).
Step
that is almost certainly an Apple Java issue. If by charting, you mean
graphics, then even more so. The Java2D api on Mac still has bugs that will
crash.
But you can't be certain unless you test ur webapp on a windows machine.
On Fri, Jan 23, 2009 at 11:03 AM, Stephen Caine wrote:
> All,
>
> W
