Servoy Forum

Hi Rob,

I tried the solution in a real server-smartclient as you suggested and it works
I hope there's an explanation for why it does longer works on developer

I opened a case about that, what should I do?

Thank you for your support

This will be fixed in Servoy 5.2.2

The problem was caused by a threading difference in smart client and web client/smart client in developer

Rob

Ok nice, Thank you for the information

Hi Rob,

I tried the submitted sample solution in 5.2.1+ from latest SVN source (so containing your fix - rev 1031) and found that although it is now running fine in Smart client, this is still not working in web client.

In Web client, I ran into that Exception:

Code: Select all

Exception in thread "pool-5-thread-1" org.apache.wicket.WicketRuntimeException: There is no application attached to current thread pool-5-thread-1
   at org.apache.wicket.Application.get(Application.java:179)
   at com.servoy.j2db.server.headlessclient.SessionClient.unsetThreadLocals(SessionClient.java:645)
   at com.servoy.j2db.server.headlessclient.SessionClient$3.afterExecute(SessionClient.java:1252)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)

Which is obviously in a Runnable, but I'm not sure where it is called from.

Also after a try in web client (and the above exception occuring), relaunching Smart client and trying again fail to call the queued method (although the login works) anymore.

Any idea?

Patrick,

The exception is a different issue, not caused by my fix.
This is fixed in next release as well.

Thanks,

Rob

Great. Thanks Rob!