Application down

Discuss all problems you have with Servoy here. It might help to mention the Servoy version and Operating System version you are using

Application down

Postby ryan.m.beasley » Wed Jun 05, 2019 7:48 pm

Hello,
In the past day my servoy application that we've been hosting went down on all servers (dev and prod). They're both receiving the same error messages whenever anyone tries to connect. The application server is running fine since I'm able to hit the website and view all of the admin settings there; however, the smart client keeps timing out when it attempts to connect. This is the error message I've been getting:

Jun 05, 2019 1:43:28 PM com.servoy.j2db.util.Debug error
SEVERE: Error getting the service com.servoy.j2db.server.shared.IApplicationServer from host spcentral.us.lmco.com:1099
java.lang.NullPointerException
at com.servoy.j2db.server.rmi.tunnel.ClientTunnelRMISocketFactoryFactory.getRemoteClientSocketFactory(ClientTunnelRMISocketFactoryFactory.java:290)
at com.servoy.j2db.smart.J2DBClient.connectApplicationServer(J2DBClient.java:1923)
at com.servoy.j2db.smart.J2DBClient.startApplicationServerConnection(J2DBClient.java:1904)
at com.servoy.j2db.ClientState.applicationServerInit(ClientState.java:316)
at com.servoy.j2db.smart.J2DBClient.startupApplication(J2DBClient.java:807)
at com.servoy.j2db.smart.J2DBClient$4.run(J2DBClient.java:712)
at com.servoy.j2db.smart.J2DBClient.mainImpl(J2DBClient.java:736)
at com.servoy.j2db.smart.J2DBClient.main(J2DBClient.java:699)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.sebster.tunnel.impl.nb.createSocket(nb.java:8)
at com.sebster.tunnel.impl.gc.connect(gc.java:5)
at com.sebster.tunnel.DelegatingTunnelClient.connect(DelegatingTunnelClient.java:2)
at com.sebster.tunnel.impl.bb.connect(bb.java:3)
at com.sebster.tunnel.DelegatingTunnelClient.connect(DelegatingTunnelClient.java:2)
at com.sebster.tunnel.impl.le.<init>(le.java:11)
at com.sebster.tunnel.multiplexer.rmi.ClientMultiplexedRmiSocketFactoryProvider$1.<init>(ClientMultiplexedRmiSocketFactoryProvider.java:2)
at com.sebster.tunnel.multiplexer.rmi.ClientMultiplexedRmiSocketFactoryProvider.<init>(ClientMultiplexedRmiSocketFactoryProvider.java:11)
at com.sebster.tunnel.multiplexer.rmi.ClientMultiplexedRmiSocketFactoryProvider.<init>(ClientMultiplexedRmiSocketFactoryProvider.java:10)
at com.servoy.j2db.server.rmi.tunnel.ClientTunnelRMISocketFactoryFactory$RmiSocketFactoryProvider.<init>(ClientTunnelRMISocketFactoryFactory.java:325)
at com.servoy.j2db.server.rmi.tunnel.ClientTunnelRMISocketFactoryFactory$RmiSocketFactoryProvider.<init>(ClientTunnelRMISocketFactoryFactory.java:323)
at com.servoy.j2db.server.rmi.tunnel.ClientTunnelRMISocketFactoryFactory.createFactoryProvider(ClientTunnelRMISocketFactoryFactory.java:277)
at com.servoy.j2db.server.rmi.tunnel.ClientTunnelRMISocketFactoryFactory.getClientSocketFactory(ClientTunnelRMISocketFactoryFactory.java:300)
at com.servoy.j2db.smart.J2DBClient.exportObject(J2DBClient.java:3423)
at com.servoy.j2db.smart.J2DBClient.bindUserClient(J2DBClient.java:3395)
at com.servoy.j2db.ClientState.applicationServerInit(ClientState.java:317)
at com.servoy.j2db.smart.J2DBClient.startupApplication(J2DBClient.java:807)
at com.servoy.j2db.smart.J2DBClient$4.run(J2DBClient.java:712)
at com.servoy.j2db.smart.J2DBClient.mainImpl(J2DBClient.java:736)
at com.servoy.j2db.smart.J2DBClient.main(J2DBClient.java:699)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

We recently had a java update get pushed out, but I don't think that's why people are unable to connect since I've installing a couple different versions of java. I'm currently checking to see if any AWS server updates went out as well in the past couple days to see if something is wrong with the servers we're hosting our application on. Is there anything in these error messages I'm missing?
ryan.m.beasley
 
Posts: 41
Joined: Wed Oct 10, 2018 8:51 pm

Re: Application down

Postby ryan.m.beasley » Wed Jun 05, 2019 8:02 pm

2019-06-05 10:51:42,477 ERROR [pool-4-thread-109287] ClientManager - Error flushing message buffer to client ######## [ ]
java.rmi.ConnectException: Connection refused to host: #######; nested exception is:
java.net.ConnectException: no multiplexer found for server with id=############
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source) ~[?:1.8.0_201]
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source) ~[?:1.8.0_201]
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source) ~[?:1.8.0_201]
at sun.rmi.server.UnicastRef.invoke(Unknown Source) ~[?:1.8.0_201]
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Unknown Source) ~[?:1.8.0_201]
at java.rmi.server.RemoteObjectInvocationHandler.invoke(Unknown Source) ~[?:1.8.0_201]
at com.sun.proxy.$Proxy36.isAlive(Unknown Source) ~[?:?]
at com.servoy.j2db.server.dataprocessing.ClientProxy.Zc(ClientProxy.java:57) ~[j2dbdev.jar:8.4.0.3402]
at com.servoy.j2db.server.dataprocessing.Zq.run(Zq.java:2) [j2dbdev.jar:8.4.0.3402]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_201]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_201]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]
Caused by: java.net.ConnectException: no multiplexer found for server with id=3079a82a-ff7c-4b31-a4bd-fdbe99309dac
at com.sebster.tunnel.impl.hd.createSocket(hd.java:12) ~[networktnl.jar:?]
at com.servoy.j2db.server.rmi.tunnel.WrappingCompressingRMIClientSocketFactory.createSocket(WrappingCompressingRMIClientSocketFactory.java:28) ~[rmitnl.jar:8.4.0.3402]
... 12 more
2019-06-05 10:51:42,477 WARN [pool-4-thread-109287] ClientManager - Unregistering client after queueing timeout: ######## [ ]
ryan.m.beasley
 
Posts: 41
Joined: Wed Oct 10, 2018 8:51 pm

Re: Application down

Postby ryan.m.beasley » Thu Jun 06, 2019 12:08 am

Never mind on this. One of our internal groups changed the security group settings for one of the 1099 port on our AWS server. Issue is resolved.
ryan.m.beasley
 
Posts: 41
Joined: Wed Oct 10, 2018 8:51 pm


Return to Discuss possible Issues and Bugs

Who is online

Users browsing this forum: No registered users and 4 guests

cron