Page 1 of 1

Problems with Batch Processors - not authenticated client

PostPosted: Thu May 31, 2018 10:22 am
by s.hinrichs
Hey guys,

we have a few problems with Batch Processors. We run all of our Batch Processors on a Application Server only for Batch Processors. In the past, we didn't have any problems running these but in the last few weeks, maybe because of more and more Batchjobs, we were noticing that some shut down automatically without errorlogs. When we restart the Batch Processors in Admin Page we get following errorstack:

Code: Select all
java.lang.RuntimeException: Couldn't get remote service: 'net.stuff.servoy.busy' for a not authenticated client
     at com.servoy.j2db.server.main.Zn.getRemoteService(
     at com.servoy.j2db.ClientState.getServerService(
     at com.servoy.j2db.plugins.ClientPluginAccessProvider.getRemoteService(
     at com.servoy.j2db.plugins.ClientPluginAccessProvider.getServerService(
     at com.servoyguy.plugins.busy.BusyClientPlugin.unload(
     at com.servoy.j2db.plugins.PluginManager.flushCachedItems(
     at com.servoy.j2db.ClientState.shutDown(
     at com.servoy.j2db.server.headlessclient.SessionClient.shutDown(
     at com.servoy.j2db.server.main.Zz.shutDown(
     at com.servoy.j2db.server.servlets.ConfigServlet.Za(
     at com.servoy.j2db.server.servlets.ConfigServlet.service(
     at javax.servlet.http.HttpServlet.service(
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(
     at org.apache.tomcat.websocket.server.WsFilter.doFilter(
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(
     at org.apache.catalina.core.StandardWrapperValve.invoke(
     at org.apache.catalina.core.StandardContextValve.invoke(
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
     at org.apache.catalina.core.StandardHostValve.invoke(
     at org.apache.catalina.valves.ErrorReportValve.invoke(
     at org.apache.catalina.core.StandardEngineValve.invoke(
     at org.apache.catalina.connector.CoyoteAdapter.service(
     at org.apache.coyote.http11.Http11Processor.service(
     at org.apache.coyote.AbstractProcessorLight.process(
     at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$ Source)
     at org.apache.tomcat.util.threads.TaskThread$
     at Source)

We found out that the class is used by Servoy busy plugin. Of course, we don't use the plugin in our Batch Processors but we think Servoy using it for some stuff.

So first question: Is this error the cause that our Batch Processors shut down automatically?

And second question: We guess that there are two ways to prevent this error, adding the class 'net.stuff.servoy.busy' to servoy.application_server.trustedRemotePlugins in Admin Page or authenticating the headless Client of Batch Processor. What is best practice in this case?

Best regards, Stefan Hinrichs

Re: Problems with Batch Processors - not authenticated clien

PostPosted: Thu May 31, 2018 1:25 pm
by mboegem
Hi Stefan,

you basically answered your own question.

First of all: As you mentioned, you shouldn't use any swing components in a headless client.

On your second question: Both solutions are valid AFAIK.
1) adding it to trustedRemotePlugins, will resolve a possible future situation with other clients as well.
2) in this case authenticating your client should also work.

I'd prefer adding to trustedRemotePlugins.

Re: Problems with Batch Processors - not authenticated clien

PostPosted: Fri Jun 01, 2018 4:02 pm
by s.hinrichs
Hi Marc,
thank you for your quick response. We add the class 'net.stuff.servoy.busy' to trustedRemotePlugins and it seems to work.