Servoy 4.0.1 & RHEL5 & Java 6: Hang

Classic Servoy
1

All…

After resolving my previous issue (http://forum.servoy.com/viewtopic.php?f=8&t=11116) I immediately hit another issue that resulted in Servoy hanging on startup, sometimes it would even hang my whole X server requiring a reboot to recover. The only hint was a “Xlib: unexpected async reply” message on the console. This led me to another bug 126931 – "Xlib: unexpected async reply" errors using SWT_AWT bridge under JDK 1.6 for which there appears to be no workaround other than to downgrade to Java 5. :(

I’m hoping you will be able to come up with a solution allowing the use of Servoy with Java 6 on Linux (from the bug report referenced above it doesn’t appear to be an issue specific to RHEL5 though I haven’t tested on other versions at this point.)

Thanks,
Corey

2

Yeroc:
I’m hoping you will be able to come up with a solution allowing the use of Servoy with Java 6 on Linux

Try the original JRE or JDK from Sun. I’ve had weird problems with the standard Ubuntu 1.5 JVM (and so have a number of others) that were fixed by using the original. I’ve stuck to Sun JVMs since.
I don’t know what RHEL uses, but it might be worth checking that. I’ve had no show-stopping JVM problems ever since.

There are three problems left in Suns JVM that I know of:

  • in KDE, smart client pop-up windows sometimes are initially shaded – this is nondeterministic
  • smart client pop-up windows might sometimes use the entire screen and if they do, they don’t have title bars – this is equally nondeterministic
  • minor menu bar vertical alignment issue in smart client
3

svroemisse:
Try the original JRE or JDK from Sun. I’ve had weird problems with the standard Ubuntu 1.5 JVM (and so have a number of others) that were fixed by using the original. I’ve stuck to Sun JVMs since.
I don’t know what RHEL uses, but it might be worth checking that. I’ve had no show-stopping JVM problems ever since.

I should have been clear: I am using Sun’s JDK. The bug report I linked to has further details on the issue with a link to a related bug in Sun’s bug database.

Regards,
Corey