Synametrics Technologies

Since upgrading to version 4, some of our remote clients are getting error displayed in chrome while trying to access the system 'Communication error occured' 'ERROR: com.google.gwt.user.client.rpc substatus code exception 500 - internal server error".

I checked the logs on the server and client errors seem to coorespond with this messge: 

2017-12-16 08:24:52,977 ERROR [localhost].[/] - Exception while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException: Type 'com.synametrics.ajaxfe.client.ConfigParamHolder' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer.For security purposes, this type will not be serialized.: instance = com.synametrics.ajaxfe.client.ConfigParamHolder@5fa6885b
 at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:667)
 at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:130)
 at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter$ValueWriter$8.write(ServerSerializationStreamWriter.java:153)
 at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:587)
 at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:631)
 at com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess(RPC.java:497)
 at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:589)
 at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:333)
 at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303)
 at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373)
 at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 at java.lang.Thread.run(Unknown Source)

So far, all the remote clients with error seem to be running chrome. For them,errors have persisted for several days but I can log in with the same ID from multiple places and access and download files just fine. I see where others have successfully accessed as well. Any ideas? I have asked them to clear browser cache and waiting for response, but woudl think after the amout of time that has passed it would have corrected itself if it was the cache. Either way, this should not be happening. I am regretting my decision to upgrade to version 4 so soon after release.

Aeron,

This is a due to browser's caching an older version of JavaScripts. Have the users hold the SHIFT key while pressing F5. They may have to do this a couple of times. Once the browser fetches the new scripts, it should work fine.