1

Update 2022-08-25 09:31 CST Relative to Tim’s comments the timeout error is not a load error, it is a reoccuring runtime error. It can happen when an animation is to end but goes to slow motion and no host/client errors are shown. Also, now something is going wrong randomly with “Get Location” not working during a nanoflow. I had considered this being related to timed events but the timestamps are inconsistent with the delay/recheck times. Effort: 2 days-no resolution found.  Includes both being rebooted. Update 2022-08-21 11:13 CDT Today’s new fun unexplained of an unmodified routine that was working yesterday but now is not .  status.mendix.com reports All Systems Operational (wish Studio Pro would provide a popup of status vs having to go to URL that was unknow until someone kindly mentioned it) An error occurred while executing On change at LogIn.LogIn_40_Register_Verify_Email.textBox7: Internal server error<------what the heck does that mean?  Which server?  Studio Pro Local Host or External Mendix Server? Nanoflow stack:  "Call microflow: EmailCustom.SendRegistrationVerificationEmail" in nanoflow "EmailCustom.SendRegistrationVerificationEmailNanoflow" Current page: LogIn.LogIn_40_Register_Verify_Email Stack: http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:1124:5436 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:1124:5516 A@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:1079:233 f@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:117:155 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:117:864 k@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:122:536 x@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:122:934 callImmediates@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:122:3023 value@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:2847 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:1023 value@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:2539 value@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:993 value@[native code] value@[native code] This could potentially be related to change in dynamic processing logic data.  Would have been nice to have a credit card function buillt in.  Custom Effort: 1 Month Update 15:41 CDT Yes indeed, failure was due to a change in custom dynamic processing logic data (soft coding vs hard coding) as it does not appear to be a built in mx function like most ERP systems…...like SAP.     Additionally: Failed to synchronize object '5348024559269464': unable to find object. To prevent data loss, the changes have been stored under 'System.SynchronizationError' with id '42784196460890383'.  <---------What object and why could it not be found?  Did parameters cause failure?  Client was online.  This has occured often during proof of concept.  Perhaps I’ve got a (insert word) design or the only one putting everything through the wringer washer.   Another goody that just happened: mx login “suggested” the “import” learning path that might have been handy a month ago.  So, I’m thinking, “what’s the timestamp of this creation?”, click on link, and whallah link failure: (Thank goodness Barry Gibb and Olivia Newton-John just came on to raise the spirit) -------------- Update 2022-08-19 22:43 CDT Apparently I am the lucky dog who’s data was in the words of Aerosmith “Living On The Edge” Reduced Item Master 5,000 rows to reduce random failures. Something needs to be done about physical vs virtual memory? It makes no sense on why the number of rows in an entity should affect Make It Native 9 Load time and random failures. Is this a design oversight of not using memory DASD paging? Debug continues to fail on breakpoints within 10 seconds. This is like J.D. Edwards World A7.3.1 when it was so buggy that customers had a fit and didn’t become solid like a rock until major overhaul A7.3.3 Ever since 1994 it stayed solid as a rock, they learned a great lesson (not including the Transportation Module that was not developed in Denver, Colorado-rumor has it was developed in Kanata.  No offense to the neighbors up north)   Effort: +1 days with overtime --------------------- Update 2022-08-19 10:49 CDT Another goody that happens irregularily.  On top of Synchronize Unsynchronized objects complaining about not able to be done while one is in process/simultaneously ?one step at a time?. --------------------- Update 2022-08-19 10:09 CDT Todays new goody-no errors logged ----------------------------------------- Update 2022-08-19 07:49 CDT The instabilities are driving me crazy.  Now today a brand new Make It Native 9 error on client popped up ONCE and could not get a screen shot of it before app collapsed.  Something to the effect of blah blah blah Make Native 9 has a bug blah blah blah  wait until fix blah blah blah on top of previously working Nanoflow that have not been modified are failing. i.e. An error occurred while executing nanoflow data source for widget Customer.Customer_900_Customer_Preferences_Edit.listView6: undefined Nanoflow stack:  "Retrieve Customer.(proprietary name) from database" in nanoflow "Customer.Nanoflow (proprietary name)" Nanoflows running: Nanoflow 1: Administrator.Nanoflow_(proprietary name)_Retrieve_Single Stack:  "Retrieve LogIn.(proprietary name) from database" in nanoflow "Administrator.Nanoflow_(proprietary name)_Retrieve_Single" Nanoflow 2: Customer.Nanoflow_(proprietary name) Stack:  "Retrieve Customer.(proprietary name) from database" in nanoflow "Customer.Nanoflow_(proprietary name)_Search" Current page: Customer.Customer_900_Customer_Preferences_Edit Stack: http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:1210:1444 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:1210:1566 y@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:12:587 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:12:1892 y@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:12:587 o@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:12:1068 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:12:1240 f@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:117:155 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:117:864 k@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:122:536 x@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:122:934 callImmediates@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:122:3023 value@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:2847 http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:1023 value@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:2539 value@http://192.168.0.143:8083/index.bundle?platform=android&dev=false&minify=true&app=com.mendix.developerapp.mx9&modulesOnly=false&runModule=true:61:993 value@[native code] value@[native code] --------------------------------------------------------------------- Studio Pro 9.16.1 Native/JDK-11.0.15.1-Make It Native 9 AGAIN continues irregularly failures/close during initial run load & during processing  -No host console information given -No client information/errors given It appears the FIRST initial run fails 99% of the time and subsequent runs process until certain pages/functions are executed then fails/closes-no audit trail Also, debug closes within 10 seconds of a breakpoint execution while attempting to inspect variable Possibly related: ?30 Minute Timed Event?-highly doubtful Effort: 2 Days Anyone else experiencing this?   Still might relate to what Tim has mentioned but is strange the failures are irregular.  i.e. One console error given related to timeout: -------- com.mendix.systemwideinterfaces.MendixRuntimeException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30004/30000 ms     at com.mendix.util.classloading.Runner$.withContextClassLoader(Runner.scala:23) Caused by: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30004/30000 ms     at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:221)     at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:623)     at java.base/sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:341)     at java.base/sun.nio.cs.StreamEncoder.close(StreamEncoder.java:161)     at java.base/java.io.OutputStreamWriter.close(OutputStreamWriter.java:258)     at com.mendix.util.using.Using$.using(Using.scala:8)     at com.mendix.modules.debugger.internal.DebuggerHandler.doProcessRequest(DebuggerHandler.scala:66)     at com.mendix.external.connector.MxRuntimeConnector.$anonfun$processRequest$1(MxRuntimeConnector.scala:50)     at com.mendix.external.connector.MxRuntimeConnector.$anonfun$processRequest$1$adapted(MxRuntimeConnector.scala:50)     at com.mendix.util.classloading.Runner$.withContextClassLoader(Runner.scala:20)     at com.mendix.external.connector.MxRuntimeConnector.processRequest(MxRuntimeConnector.scala:50)     at com.mendix.basis.impl.MxRuntimeImpl.processRequest(MxRuntimeImpl.scala:229)     at com.mendix.m2ee.appcontainer.server.handler.RuntimeServlet.service(RuntimeServlet.scala:32)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)     at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1665)     at org.eclipse.jetty.websocket.servlet.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:170)     at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:202)     at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1635)     at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:527)     at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)     at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1571)     at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1378)     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)     at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484)     at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1544)     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)     at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1300)     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)     at org.eclipse.jetty.server.Server.handle(Server.java:562)     at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)     at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)     at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:319)     at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)     at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:412)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:381)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:268)     at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:138)     at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:407)     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:894)     at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1038)     at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.util.concurrent.TimeoutException: Idle timeout expired: 30004/30000 ms     at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166)     at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:108)     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)     at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)     at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)     at java.base/java.lang.Thread.run(Thread.java:834)  

asked 2022-08-19

2 answers