This has recently cropped up at my workplace - We have a report that runs every night and dumps a reasonable chunk of the database to a text file. The report itself is quite inefficient (it stores everything in memory until it's written to the text file, for example), but a simple switch from Geronimo 2.1.1 to Geronimo 1.1.1 results in the file taking 2 - 3 hours instead of 6 - 8 (or more!) hours. I'll be looking into this myself, trying to pinpoint if it's our fault or Geronimo's fault, but I was wondering if anyone had any ideas, or if there are any known areas where Geronimo 2.1.1 is slower than Geronimo 1.1.1? Likely places are in the XML libraries, or in the Database Pool/Connectivity from what I understand.
Any suggestions on how to investigate this would also be appreciated. I'll add in profiling code to our application in the relevant places, but I'm not sure what else I should be doing to get to the bottom of this? Thanks, - Andrew Thorburn
