Apache OpenOffice (AOO) Bugzilla – Issue 121312
Slow database access with Java 7
Last modified: 2017-05-20 09:36:07 UTC
Base becomes very slow when connected via JDBC and Java 7. There is no such problem with Java 6. OpenOffice.org 3.2 and 3.3 suffered from the same performance problem with any Java version >6.23 This problem never occurred under Windows 7 nor XP. Verified under Ubuntu Linux(32 and 64) with the following JDBC connections: 1. embedded HSQLDB 1.8 2. external HSQLDB 2.2.x 3. external H2 1.2.x
I don't use those connections but IMHO it's not unimportant which java is mentioned, Oracle or openjdk.
Both, Oracle Java7 and openjdk-7.
Have just tested AOO 4.0. There is a test-database here: https://bugs.freedesktop.org/attachment.cgi?id=63257 When I will open the table under OpenSUSE 64bit rpm and 1.7.0_21 openjdk it needs 10 seconds to show the rows on the screen. Now, when I will move to last row, it lasts 2 Minutes and 40 seconds. Same test on the same environment, only changed the jre to 1.6.0_22 SUN, the table opens immediately, moving to last row about max. 2 seconds. Don't know how I could change the Status, but it has to be changed to "Confirmed".
Setting CONFIRMED status
This issue keeps me on the very very old Java 1.6.022! Please fix this issue - it's open since months and months. I'm working with OpenSuse 12.3! Thanks
due to reporters description: platform = 'Linux' version = 'pre-3.4.0' (which is not available), thus '3.4.0'
Same problem with AOO 4.0.1.
Same problem with AOO 4.1.0 beta.
With AOO 4.0.1 the problem exists with jre 6u22 and 7u51.
This issue should get a higher priority because HSQL is virtual unusable because every data access needs 100 % CPU power over seconds/minutes. (Ubuntu 368)
> With AOO 4.0.1 the problem exists with jre 6u22 and 7u51. No, it works well with 6u22. Call Tools>Options>Java and make sure that the old JRE is checked. Click the option button, not just the list entry! Then restart the office completely including any "quick starter" (which is the most obsolete anti-feature, by the way).
There are several security updates in Java since 6.x. Because a linux distribution integrates Java in its update mechanism, for most users it is difficult to switch back to an earlier Java release without removing the actual one.
Seems the problem is gone with Java 8.
(In reply to mroe from comment #13) > Seems the problem is gone with Java 8. Indeed.
Why was this changed to Resolved/Obsolete? Java 8 is not part of our current system requirements. I'm on 4.1.1 and openJDK "1.7.0_51", and yes, I definitely experience the issue described here. I'm assuming Java 8 is a work-around by this discussion, but is "Obsolete" the right reason?
Because AOO works with Java 6 and Java 8 but not with Java 7, it seems there was a problem in Java 7, not in AOO. But if anyone know the reason, why AOO slows down with Java 7 and find a solution in the AOO code, he should reopen this issue. Otherwise I think that no developer will grab this issue. Isn't it?
Re comment 16. I understand your reasoning. I will pass on the "dev" and see what opinions are.