Operations Timed Out - Githubissues

objecthub-io commented 7 years ago

This error occurs sometimes on the client.

Exception reported: Operation timed out.
hub/users/main/~objecthub/home/my/~*0/it/.n/Platform/.n/Import/~*0/.n/ObjectHub_Web/.n/Screens/.n/Index___Main_Page/.n/Notification/.n/Notification__MA_/app_js/baseJs.js:90 java.lang.Exception: Operation timed out.<br />
Unknown.oM(0.js@339)<br/>
Unknown.vIb(0.js@424)<br/>
Unknown.L(0.js@341)<br/>
Unknown._.qi(0.js@472)<br/>
Unknown.zoc(0.js@226)<br/>
Unknown.p5(0.js@183)<br/>
Unknown._.Pc(0.js@32)<br/>
Unknown._.yh(0.js@14)<br/>
Unknown.eval(0.js@323)<br/>
Unknown.eval(0.js@243)<br/>
-end of stack trace
hub/users/main/~objecthub/home/my/~*0/it/.n/Platform/.n/Import/~*0/.n/ObjectHub_Web/.n/Screens/.n/Index___Main_Page/.n/Notification/.n/Notification__MA_/app_js/baseJs.js:86 Exception reported: Operation timed out.
hub/users/main/~objecthub/home/my/~*0/it/.n/Platform/.n/Import/~*0/.n/ObjectHub_Web/.n/Screens/.n/Index___Main_Page/.n/Notification/.n/Notification__MA_/app_js/baseJs.js:90 java.lang.Exception: Operation timed out.<br />
Unknown.oM(0.js@339)<br/>
Unknown.vIb(0.js@424)<br/>
Unknown.L(0.js@341)<br/>
Unknown._.qi(0.js@472)<br/>
Unknown.zoc(0.js@226)<br/>
Unknown.p5(0.js@183)<br/>
Unknown._.Pc(0.js@32)<br/>
Unknown._.yh(0.js@14)<br/>
Unknown.eval(0.js@323)<br/>
Unknown.eval(0.js@243)<br/>
-end of stack trace

Error on server

delight.scheduler.SequentialOperationScheduler@1009452a: Scheduler timed out [nx.remote.internal.connections.SingleConcurrentOperationConnection@185c88a5->forConnection:com.appjangle.database.keyvalue.network.TriggerConnection@5c199ce]
delight.scheduler.SequentialOperationScheduler@1009452a: Don't call callback since operation was cancelled and onFailure already called: nx.remote.internal.connections.SingleConcurrentOperationConnection$1@ec2e51f

Shortly after one time the server restarted (but I don't think this happens every time):

class com.appjangle.server.daemon.AppjangleServerDaemon [Tue Aug 15 05:02:30 UTC 2017]: Server in invalid state. Check class com.appjangle.server.daemon.checks.RestNodeCheck has failed

objecthub-io commented 7 years ago

Some notes:

A domain object was open, checking many times whether the domain is online
It first crashed when navigating through objects in the browser
There were also errors caused by uploading a service
The server was just recently restarted (since a new version was deployed)

stellardb commented 7 years ago

This error still occurs, there was no domain object created, there were no errors caused by uploading a service, the server was not recently restarted:

delight.scheduler.SequentialOperationScheduler@2663be77: Scheduler timed out [nx.remote.internal.connections.SingleConcurrentOperationConnection@4cbbebd2->forConnection:com.appjangle.database.keyvalue.network.TriggerConnection@83ab7ba]
delight.scheduler.SequentialOperationScheduler@493705e1: Scheduler timed out [nx.remote.internal.connections.SingleConcurrentOperationConnection@2523db4c->forConnection:com.appjangle.database.keyvalue.network.TriggerConnection@79491ccb]
delight.scheduler.SequentialOperationScheduler@1a659a: Scheduler timed out [nx.remote.internal.connections.SingleConcurrentOperationConnection@34ca7921->forConnection:com.appjangle.database.keyvalue.network.TriggerConnection@199c5641]
delight.scheduler.SequentialOperationScheduler@493705e1: Don't call callback since operation was cancelled and onFailure already called: nx.remote.internal.connections.SingleConcurrentOperationConnection$1@26affac4
delight.scheduler.SequentialOperationScheduler@1a659a: Don't call callback since operation was cancelled and onFailure already called: nx.remote.internal.connections.SingleConcurrentOperationConnection$1@4faddc8b

mxro commented 7 years ago

Another occurrence:

Wed Sep 13 11:11:10 EDT 2017 SequentialOperationScheduler/d6d13: Scheduler timed out [owner: com.appjangle.database.hooks.HookConnection@4b168fa9->main, currentOperation: com.appjangle.database.hooks.HookConnection$2@4ac7bc61]
Wed Sep 13 11:11:10 EDT 2017 java.lang.Exception: Operation timed out. (from object: com.appjangle.database.hooks.HookConnection$1@a4bd8c7)
  delight.scheduler.SequentialOperationScheduler.runIfRequired(SequentialOperationScheduler.java:143)
  delight.scheduler.SequentialOperationScheduler.schedule(SequentialOperationScheduler.java:107)
  com.appjangle.database.hooks.HookConnection.notifyChange(HookConnection.java:132)
  com.appjangle.database.internal.connections.DatabaseConnection$16.onChanges(DatabaseConnection.java:383)
  com.appjangle.database.hooks.internal.InterceptUpdatesConnection$2.onSuccess(InterceptUpdatesConnection.java:91)
  com.appjangle.database.hooks.internal.InterceptUpdatesConnection$2.onSuccess(InterceptUpdatesConnection.java:1)
  nx.remote.utils.NxServerUtils$WaitForJoin.registerResponse(NxServerUtils.java:66)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:118)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:1)
  nx.remote.utils.NxServerUtils$WaitForJoin.registerResponse(NxServerUtils.java:66)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:118)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:1)
  nx.remote.utils.NxServerUtils$WaitForJoin.registerResponse(NxServerUtils.java:66)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:118)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:1)
  nx.remote.utils.NxServerUtils$WaitForJoin.registerResponse(NxServerUtils.java:66)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:118)
  nx.remote.utils.NxServerUtils$1.onSuccess(NxServerUtils.java:1)
  com.appjangle.database.internal.connections.ConnectionForNetworkMessages$1.onSuccess(ConnectionForNetworkMessages.java:122)
  com.appjangle.database.internal.connections.ConnectionForNetworkMessages$1.onSuccess(ConnectionForNetworkMessages.java:1)
  com.appjangle.database.internal.connections.ConnectionForNetworkMessages$3.apply(ConnectionForNetworkMessages.java:298)
  com.appjangle.database.internal.connections.ConnectionForNetworkMessages$3.apply(ConnectionForNetworkMessages.java:1)
  delight.async.AsyncCommon$11.onSuccess(AsyncCommon.java:370)
  delight.async.flow.CallbackAggregator$1.onSuccess(CallbackAggregator.java:72)
  com.appjangle.database.internal.connections.ConnectionForNetworkMessages$2$1$1.onSuccess(ConnectionForNetworkMessages.java:239)
  com.appjangle.database.internal.connections.ConnectionForNetworkMessages$2$1$1.onSuccess(ConnectionForNetworkMessages.java:1)
  com.appjangle.database.keyvalue.network.NetworkServerConnection$1.onSuccess(NetworkServerConnection.java:53)
  com.appjangle.database.keyvalue.network.NetworkServerConnection$1.onSuccess(NetworkServerConnection.java:1)
  delight.scheduler.SequentialOperationScheduler$1.onSuccess(SequentialOperationScheduler.java:103)
  delight.scheduler.SequentialOperationScheduler$3$2.run(SequentialOperationScheduler.java:282)
  delight.concurrency.jre.JavaExecutor$4.run(JavaExecutor.java:83)
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  java.lang.Thread.run(Thread.java:748)
Wed Sep 13 11:11:10 EDT 2017 SequentialOperationScheduler/464d7: Scheduler timed out [owner: com.appjangle.database.hooks.HookConnection@4b168fa9->versionDb, currentOperation: com.appjangle.database.hooks.internal.VersionDb$1@abfa3f8]
Wed Sep 13 11:11:10 EDT 2017 java.lang.Exception: Operation timed out. (from object: com.appjangle.database.hooks.HookConnection$1@a4bd8c7)
  delight.scheduler.SequentialOperationScheduler.runIfRequired(SequentialOperationScheduler.java:143)
  delight.scheduler.SequentialOperationScheduler.schedule(SequentialOperationScheduler.java:107)
  com.appjangle.database.hooks.internal.VersionDb.notifyChange(VersionDb.java:45)
  com.appjangle.database.hooks.HookConnection$2.apply(HookConnection.java:129)
  delight.scheduler.SequentialOperationScheduler.executeOperation(SequentialOperationScheduler.java:216)
  delight.scheduler.SequentialOperationScheduler.executeWithTimeout(SequentialOperationScheduler.java:193)
  delight.scheduler.SequentialOperationScheduler.access$0(SequentialOperationScheduler.java:190)
  delight.scheduler.SequentialOperationScheduler$2.run(SequentialOperationScheduler.java:183)
  delight.concurrency.jre.JavaExecutor$4.run(JavaExecutor.java:83)
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  java.lang.Thread.run(Thread.java:748)
Wed Sep 13 11:11:10 EDT 2017 SequentialOperationScheduler/464d7: Don't call callback since operation was cancelled and onFailure already called: com.appjangle.database.hooks.internal.VersionDb$1@abfa3f8
Wed Sep 13 11:11:10 EDT 2017 SequentialOperationScheduler/464d7: Don't call callback since operation was cancelled and onFailure already called: com.appjangle.database.hooks.internal.VersionDb$1@2514cefd
Wed Sep 13 11:11:10 EDT 2017 SequentialOperationScheduler/d6d13: Don't call callback since operation was cancelled and onFailure already called: com.appjangle.database.hooks.HookConnection$2@5110280e

mxro commented 7 years ago

The latest error coincided with a server restart:

class com.appjangle.server.daemon.AppjangleServerDaemon [Wed Sep 13 11:11:52 EDT 2017]: Server in invalid state. Check class com.appjangle.server.daemon.checks.RestOnline has failed

stellardb / StellarDB

Operations Timed Out #100