In the “login” solution/module I have my individual loginform. When I logout of the main solution by executing <security.logout> in a function, the loginform is automatically displayed as expected. But only on my internal network environment (Mac Server and Clients) and on the application server from developer. When launching a Smart Client from my customers application server, I will get a blank grey window if I’m executing a logout!?
Thomas
do you have anything errors/log in the java console?
this really shouldnt matter for smart clients that are internal or external… The login/logout is exactly the same for them
I get the error in the server log:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “log_pkey”
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1525)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1309)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:308)
at sun.reflect.GeneratedMethodAccessor226.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.servoy.j2db.Za.Za.Zf.invoke(Zf.java:15)
at $Proxy0.executeUpdate(Unknown Source)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at com.servoy.j2db.dataprocessing.Zu.Za(Zu.java:283)
at com.servoy.j2db.dataprocessing.Zu.Za(Zu.java:487)
at com.servoy.j2db.dataprocessing.Zu.access$4(Zu.java:609)
at com.servoy.j2db.dataprocessing.Zx.run(Zx.java:5)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
If SolutionBrowsing is true, the select solution dialog doesn’t close by “OK”, only when clicking “Cancel”.
thats just a server error for you log table (you should sync your pk sequences for that)
I meant the java console on the client that gets a gray screen.
For that solution dialog there are already fixes in 5.2.1
Sorry for that mistake. The Java Console on the Client says:
Exception in thread “AWT-EventQueue-0” java.lang.RuntimeException: Die Lösung konnte nicht geöffnet werden
at com.servoy.j2db.ClientState.selectSolutionToLoad(ClientState.java:442)
at com.servoy.j2db.smart.J2DBClient.selectSolutionToLoad(J2DBClient.java:1742)
at com.servoy.j2db.ClientState.handleClientUserUidChanged(ClientState.java:396)
at com.servoy.j2db.smart.J2DBClient$19$1.run(J2DBClient.java:1978)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at com.servoy.j2db.util.SwingHelper.dispatchEvents(SwingHelper.java:153)
at com.servoy.j2db.smart.J2DBClient.selectSolutionToLoad(J2DBClient.java:1740)
at com.servoy.j2db.ClientState.handleClientUserUidChanged(ClientState.java:396)
at com.servoy.j2db.ClientState.logout(ClientState.java:544)
at com.servoy.j2db.smart.J2DBClient.logout(J2DBClient.java:2846)
at com.servoy.j2db.smart.J2DBClient$23.run(J2DBClient.java:2871)
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)
When is 5.2.1 ready for download?
that error means that the application server didnt give any solutions that could be shown…
Need to investigate that, can you make a case with a simple example?
5.2.1 is most likely released within a month.
What I found out is:
If <servoy.allowSolutionBrowsing: > in the Solution Settings is true, the solution select dialog is displayed. If I select the main-solution in the dialog and click ‘OK’, the loginForm is displayed, but the solution select dialog is still in front. When I click once more the ‘OK’ button, a gray window with a rotating servoy icon is displayed and the only option is to close the servoy client. But do I click the ‘Cancel’ button, the select dialog close and I’m able to enter the loginForm.
If <servoy.allowSolutionBrowsing: > in the Solution Settings is set to false, the gray window is displayed and nothing happens.
I will try to make a small example solution with a link to it in the support system, ok?
what you describe there should already be fixed for 5.2.1