Error with getScheduledExecutor

[felipe.monroy]

Hi all,

I have noticed that several posts containing Servoy (Java) errors go unanswered, which leaves us with errors we can't fix in our applications. This makes me wonder whether the devs are constantly trying go fix these problems or they are focusing on adding new functionality instead. Don't forget we pay a annual licence, which is not cheap, therefore presence in the forums should be the minimum thing you guys should do.

We are recently testing a migration from Servoy 7.4.5 to Servoy 2023 due to one of the aforementioned errors, plus an issue with the clients getting de-registered (which apparently is fixed in one of the versions in between), however now we're encountering another error of which I'm finding zero information.

The error says:

Code: Select all

2023-04-24 10:38   ClientManagerScheduler-3-thread-26   ERROR   ClientManager   Error flushing message buffer to client 75D4779D-9B23-4309-8C38-C5925221F455       
java.lang.NullPointerException: Cannot invoke "java.util.concurrent.ScheduledExecutorService.execute(java.lang.Runnable)" because the return value of "com.servoy.j2db.ClientState.getScheduledExecutor()" is null
at com.servoy.j2db.ClientStub.closeSolution(ClientStub.java:92) ~[j2db.jar:2023.3.0.3842]
at com.servoy.j2db.server.dataprocessing.ClientProxy.Zc(ClientProxy.java:65) ~[j2dbdev.jar:2023.3.0.3842]
at com.servoy.j2db.server.dataprocessing.Zp.run(Zp.java:5) ~[j2dbdev.jar:2023.3.0.3842]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]

This is happening every single time I close the solution or logout and it's becoming very annoying.

Any insights will be appreciated. Thank you.

[mboegem]

Hi Felipe,

The forum is more community based place to ask for help, although Servoy is picking up threads regularly.
If you feel you're encountering bugs, you should consider to open a support case. (support.servoy.com)

Hope this helps

[felipe.monroy]

Thanks, but I created a ticket on their Jira like a week ago and it hasn't gotten any activity. Seems like we're paying for nothing.

[jcompagner]

how are you closing the solution?
because that exception is a close that is triggered from the server side (so admin page close or maybe a close through some client manager plugin, closing another client)

But the client is already closed, so it shouldn't get an event in the first place anymore, (server side is calling close on an already closed client thats why you get a null pointer)