You can try profiling (e.g., with VisualVM) to get a better sense of
where the bottleneck is. If OpenJDK is the only thing that changed,
it's likely a performance problem was introduced somewhere in there
that affects the OpenOffice integration. If you can narrow it down,
that could certainly help to determine whether the JDBC driver can do
anything about it.
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com
