When my users launch Servoy Client, it takes a long time to load. I see the JAVA logo right away, it stay up for a few seconds, then goes away. About 2 minutes and 30 seconds later, the application comes up with the login prompt.
If you close the application and relaunch it, the time is significantly less.
Is there a log somewhere that will show me what it’s doing during that time? Will disabling some plugins help reduce this time? any other ideas? I’m currently using Servoy 5.2.
that’s all there is in the java console. During the long delay, there is no activity in the console, and then after about 2 minutes all of those messages start to appear in the console, then the application opens.
I have seen the problem also. Loading the login was +/- 2 minutes.
We found out that It was with users with the update of the latest version Java 7 (Client-side). It was automaticaly downloaded +/- 2 weeks ago.
We have downgraded to a previous version. This solved the long loading problem.
Will be some kind of problem with the new security options in Java 7.45.
Thanks for the input everyone. We are still on JAVA 6 update 51.
Could “warnings” within my solution contribute to the delay? I have a few hundred warning messages - “overlap betweens sliding components”, “element is outside the bounds of the form”, etc.
if you open the java preferences and in the advanced section you disable a view checks (you can also pick 1 after each other to see which one really has effect)
1> Mixed code: disable verification
2> Perform certificate revocation checks on: do not check
3> Check for certificate revocation using: Certificate Revocation Lists
Do you use some or many 3th party plugins? And if you do do you resign your self everything with your own certificate? Because if you don’t do that you have all kinds of certificates loaded in that are now checked every time.
If you just have 1 (just servoy or just your own) it is already way quicker because by default in only checks that chain.
I have 2 or 3 third party plugins. I have never resigned anything using my own certificate. I’m not sure how to do that, can you point me in the right direction?
Honestly, this problems with every Java update and the Servoy Smart clients is really disturbing.
I really don’t have many Servoy smart client users at the moment, but I’ve been working to get rid of Drupal and FileMaker applications and move them to Servoy. A while ago I gave a presentation to my bosses on how well the Servoy Smart Client (a desktop application) worked/performed in comparison with Drupal (web apps) and FileMaker.
Still, I am concerned to move all these users (40+) to Servoy. I am one-man band, and I don’t want to spend my time dealing with these issues client machine by client machine.
Have Servoy think about a global strategy on how to deal with this problem of Java updates? Should we just forget Smart Client solutions entirely? What’s the strategy here?
Not much comfort for you but I think the general feeling is that the problems with Java/Desktop apps will only get worse. Apple are doing all they can to make it difficult to use Java apps and Oracle are fighting a losing battle to plug new vulnerabilities.
Servoy have been pushing WebClient development to provide an alternative and, in the last couple of years, I have moved almost all of my existing customers away from Desktop and start all new projects as Web only. It can be difficult converting legacy solutions (I have one going back to Servoy 2.1), and WebClient does present some new challenges, but I think it is the way forward.
Clients and bosses may not like the extra costs of moving away from desktop but have to accept that the IT world is constantly changing. Five years ago Servoy Desktop Client was so much better than Filemaker etc., and the Java scene was relatively stable, but you can’t stand still so it’s either move to a different platform - I chose WebClient - or write-off time struggling to get Java WebStart to actually start
grahamg:
Five years ago Servoy Desktop Client was so much better than Filemaker etc
Five years ago we were throwing Filemaker clients on Citrix to prolong the life of those apps. That’s recently become our standard operating procedure for Servoy smart client apps. And it is the same now as back then: you know you’re on life support when you have to involve Citrix.