Hi Raymond, #1 immediately sounds good to me. If 250,000 isn't enough, or still causes Out Of Memory, then #3 seems like the next be course of action.
-Paul [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Dans, Raymond AVAYA (CAR:9D30) Sent: December 22, 2009 12:42 PM To: sipX developers Subject: [sipX-dev] XX-6521 : Exception produced and javacore files aredumped when tried to view the Jasper Reports after soak test I've been working on XX-6521 and came to the conclusion that the issue is really not in Jasper Reports but, in fact the Out Of Memory is occuring because sipXconfig attempts to read all of the CDR records that fit the start/end date criteria. In "normal" cases, this is not an issue but the running of the soak test produced over 1 million CDR records in about 3 days. Attempting to read all of these records in via the Historical records link or the Reports will cause the Out Of Memory condition. There may a few different type of solutions to try and resolve this with varying dregrees of effort. 1. Limit the number of records read in - This is by far the simplest solution as it simply involves using the LIMIT capability of SQL. I've done some tests on sipXconfig and we can handle around 250,000 records. I tried 300,000 and this produced the Out Of Memory. 2. Change the amount of heap space for the sipXconfig JVM - Currently it looks like we use the default maximum heap size for JVMs is 128 Mb. We could increase this but it would have to be by at least 4 times (i.e. 512 Mb) to possibly get 1 million records and I'm sure we would still need to limit the number of records read in. 3. Configure sipXconfig such that only a limited number of records are kept in memory and retrieved in blocks. - Not sure if this is possible (via the setFetchSize in JDBC) given that most of this is hidden by Spring or wether this will work with Reports or not. I would like to implement #1 immediately as I think a limit of 250,000 records is more than sufficient for the majority of cases and that truly this is way way more than most systems need. Any objections/comments? Raymond Dans | Software Engineer| Avaya | 3500 Carling Avenue| Ottawa, Ontario K2H-8E9| Voice/Fax/Mobile: 613-763-3941/613-763-7742 | [email protected] Intelligent Communications avaya.com <http://www.avaya.com/> [ Please consider the environment before printing this email ]
<<ic_logo.jpg>>
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
