Is anyone having trouble with Java 6_18? I’m getting I.T. reports from a client (quoted below) of difficulty launching – “forever spinning donut”…
Version 18 does have a bug. If I install version 17, delete those folders, and then open Servoy, everything reinstalls and it works great. Then, if I install version 18, Servoy keeps working in the profile I’m in. In other profiles, even new ones, the donut just spins and spins. It’s very strange and I think it has something to do with the %appdata%\sun folder in the existing profile, but it’s not worth pursuing. Since version 17 works across profiles using the fix I outlined, I’m just going to use it until the next update or two comes out.
Sorry about the confusion.
Sent: Thursday, January 21, 2010 6:05 PM
After I spoke with you earlier I tried using Java 6, version 17 on a different machine and Servoy exhibited the exact same symptoms as version 18 did. I wanted to bang my head on the desk. After extensive troubleshooting, I found that I needed to delete two folders to get Servoy to work again in an existing profile.
Delete %userprofile%.servoy and %appdata%\sun.
After entering the users credentials, Servoy accesses the Sun folder to make magic happen. It seems that if all of the old versions of Java are uninstalled from the machine and then the newest version is installed, the Javaw.exe process throws up on itself and you get a spinning donut. Simply deleting the folders above causes the Servoy and Sun folders to be recreated in the users profile and Servoy works again.
This fix works for both version 6 update 17 and 18!
One other interesting fact… This is only a problem for existing profiles/users. If a new user logs into the computer, he or she would be able to use Servoy without needing to delete these folders because they’re created correctly the first time they login.
There was some bug in a previous version of Java that had impact on Servoy.
You wrote couple of months ago that this will be fixed in update 18.
Is that bug fixed now?
I haven’t checked the bug in java 1.6_18 yet, but we also had problems with clients that have upgraded to 1.6_18
All of them, got the spinning logo, of the Servoy client, but after that, the spinning logo disappears, and the screen stays grey.
tried several times, to start the client, but still the same.
In all cases, just clearing the java-cache en downloading the client again, fixed the problem.
According to my client, clearing the Java cache worked only temporarily. The next time you logon/restart you have trouble again. That was when we gave up and went back to 6 17
ahh now i suddenly see problems, because of our own servers constantly updating to the latest 5.1 server.
it seems that if you update a server and that update only updates jars X and Y but not Z
then webstart also will only download X and Y because those are changed. But it seems that webstart suddenly has problems then with the signed jars… it says that Z is not the same as X
But that should be just the case…
When you clear the cache, then will webstart download X,Y and Z and then it wont complain…
This is at least what i think happens, i am not sure, But for everybody that also has problems with 6u18 what is the error in the java console when you start webstart? Does it have references to classes that are not signed correctly?
i guess the difference is which one you update and from what…
if you update a server from version 9 to 10 then many jars are not changed
but if you do it from 1 to 10 then almost everything is changed.
something like that i guess could be it.
but is jai_imageio.jar signed? that one isnt in core i think. Or is that one signed by sun itself. Maybe you just should remove the signing (i think we did that some time ago for our plugin)
i made some changes in the 5.1 code base (so will be in the next build of 5.1)
This will result in if 1 jar file changes for the client all core jar files will be reported as updated and will be transfered to the client.
Locally this seem to fix the problem, i can update various jars and the client always loads.
So if people can test if it also works for them in the next build of 5.1 then i can also back port this to older versions.
I have a client running on Servoy 4.1.0 build-651. They recently updated the JRE to Java 6 update 18 and on load of the solution got a grey screen.
I rebuilt the solution with the java 6 update 18 in Eclipse (setting the jre version). Upgraded the development server to have the latest jre environment. I cleared the java cache for the user and did a download of the solution and got the following error:
Java Web Start 1.6.0_18
Using JRE version 1.6.0_18-b07 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\jdcunha
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
0-5: set trace level to <n>
----------------------------------------------------
INFO - Debug - Starting Servoy from C:\Program Files\Mozilla Firefox
INFO - Debug - Servoy 4.1.0 build-651 on Windows XP using Java 1.6.0_18
INFO - Debug - About to attempt auto proxy detection under Java version:1.6.0_18-b07
INFO - Debug - Using failover proxy detection...
INFO - Debug - Plugin Proxy Config List Property: null
INFO - Debug - No configured plugin proxy list
INFO - Debug - webstart: proxyHost=null proxyPort=null
Feb 22, 2010 4:59:45 PM com.sebster.tunnel.impl.hc a
INFO: jcifs library found; NTLM support enabled
Feb 22, 2010 4:59:45 PM com.sebster.tunnel.impl.hc a
INFO: using direct connection
Exception in thread "AWT-EventQueue-0" sun.misc.ServiceConfigurationError: javax.imageio.spi.ImageOutputStreamSpi: Provider com.sun.media.imageioimpl.stream.ChannelImageOutputStreamSpi could not be instantiated: java.lang.IllegalArgumentException: vendorName == null!
at sun.misc.Service.fail(Unknown Source)
at sun.misc.Service.access$200(Unknown Source)
at sun.misc.Service$LazyIterator.next(Unknown Source)
at javax.imageio.spi.IIORegistry.registerApplicationClasspathSpis(Unknown Source)
at javax.imageio.spi.IIORegistry.<init>(Unknown Source)
at javax.imageio.spi.IIORegistry.getDefaultInstance(Unknown Source)
at javax.imageio.ImageIO.<clinit>(Unknown Source)
at com.servoy.j2db.util.ImageLoader.getSize(ImageLoader.java:251)
at com.servoy.j2db.dataui.Zsc.<init>(Zsc.java:32)
at com.servoy.j2db.dataui.AbstractScriptLabel.Za(AbstractScriptLabel.java:318)
at com.servoy.j2db.dataui.AbstractScriptLabel.setIcon(AbstractScriptLabel.java:68)
at com.servoy.j2db.dataui.AbstractScriptLabel.setMediaIcon(AbstractScriptLabel.java:171)
at com.servoy.j2db.dataui.ComponentFactory.createGraphicalComponent(ComponentFactory.java:323)
at com.servoy.j2db.dataui.ComponentFactory.createComponentEx(ComponentFactory.java:493)
at com.servoy.j2db.dataui.ComponentFactory.createComponent(ComponentFactory.java:581)
at com.servoy.j2db.dataui.Zcc.Za(Zcc.java:370)
at com.servoy.j2db.dataui.Zcc.Za(Zcc.java:51)
at com.servoy.j2db.FormController.Za(FormController.java:978)
at com.servoy.j2db.FormController.Za(FormController.java:595)
at com.servoy.j2db.FormManager.Zf(FormManager.java:192)
at com.servoy.j2db.FormManager.Za(FormManager.java:443)
at com.servoy.j2db.FormManager.Zd(FormManager.java:221)
at com.servoy.j2db.FormManager.Za(FormManager.java:73)
at com.servoy.j2db.SwingFormManager.Za(SwingFormManager.java:85)
at com.servoy.j2db.Zhb.run(Zhb.java:3)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.IllegalArgumentException: vendorName == null!
at javax.imageio.spi.IIOServiceProvider.<init>(Unknown Source)
Do I need to upgrade them Servoy 5.1 in order to access the smart client using JRE 1.6 update 18 or am I missing something?
Thanks Johan – This worked for us in 3.5.8 and 3.5.10 as well (two servers on those two versions), without even restarting the service. But restart of service or not, it required deleting the java cache to get it to work in smart client. Is there any way to avoid this, as we have many machines all over Seattle and the surrounding areas running this software? We’d rather not go to each workstation to clear the java cache, but will if necessary.
a restart of the application server should trigger an update on the client for that jar.
Because we then generate different version in the jnlp file.
Is “servoy.fastClientStartup” enabled on the admin pages? Then this could cause a bit more caching on the client side.
Also if you start a client after a server restart, close it and then start it again, does that help? (then webstart should really have seen there was a updated jar)