We are utilizing the Java crystal API to create reports in our application and when our customers run the reports in WebSphere Application Server, they end up crashing the JVM because the reports are taking far too much memory to run. Also, we are having HORRIBLE performance problems when running the reports in the JVM.
How do we figure out how to solve these issues with Crystal Reports? We cannot be the only company to have these sorts of problems.
Our setup is:
WebSphere 6.1 or 7
Platforms supported are IBM System i or Windows Server
Databases supported are IBM System i or Windows SQL Server 2005.
Some of our reports are created directly from the database and some are using POJO's as datasources. For us, it doesn't seem to matter and we still run out of memory.
Hopefully somebody can point us in the right direction.
Thank you,
Shawn