Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 843789, 2 years ago
via GitHub by Ausskothar
, 2 months ago
Negative delay.
via Eclipse Bugzilla by steve.robenalt, 1 year ago
via GitHub by gvagenas
, 2 years ago
Negative delay.
java.lang.IllegalArgumentException: delay < 0: -1012	at java.util.Timer.schedule(Timer.java:454)	at io.socket.client.Manager.reconnect(Manager.java:544)	at io.socket.client.Manager.onclose(Manager.java:524)	at io.socket.client.Manager.access$1500(Manager.java:20)	at io.socket.client.Manager$6.call(Manager.java:377)	at io.socket.emitter.Emitter.emit(Emitter.java:117)	at io.socket.engineio.client.Socket.onClose(Socket.java:812)	at io.socket.engineio.client.Socket.onError(Socket.java:773)	at io.socket.engineio.client.Socket.access$900(Socket.java:31)	at io.socket.engineio.client.Socket$4.call(Socket.java:318)	at io.socket.emitter.Emitter.emit(Emitter.java:117)	at io.socket.engineio.client.Transport.onError(Transport.java:72)	at io.socket.engineio.client.transports.WebSocket.access$500(WebSocket.java:28)	at io.socket.engineio.client.transports.WebSocket$2$5.run(WebSocket.java:150)	at io.socket.thread.EventThread$2.run(EventThread.java:80)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)