Error during deployment in the sandbox.

1
Hi Since yesterday i have problems when deploying in the sandbox. The modeler responds with 'Whoops, something went wrong while deploying your app to the sandbox'. However, all my changes are deployed correctly and the app is running without errors. What went wrong and what can i do to solve it? The application starts without errors on my local machine. The log shows an error on the Jetty server. 2014-09-22 19:09:11.369 WARNING - Jetty: handle failed 2014-09-22 19:09:11.369 WARNING - Jetty: java.lang.RuntimeException: Failed to put log message into the queue at com.mendix.logging.impl.LogQueue.put(LogQueue.java:60) at com.mendix.logging.impl.LogNode.trace(LogNode.java:198) at com.mendix.logging.impl.JettyLogger.debug(JettyLogger.java:37) at org.eclipse.jetty.io.nio.ChannelEndPoint.fill(ChannelEndPoint.java:254) at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.fill(BlockingChannelConnector.java:242) at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:1040) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:280) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:298) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.InterruptedException: null at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(Unknown Source) at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(Unknown Source) at java.util.concurrent.LinkedBlockingQueue.put(Unknown Source) at com.mendix.logging.impl.LogQueue.put(LogQueue.java:56) at com.mendix.logging.impl.LogNode.trace(LogNode.java:198) at com.mendix.logging.impl.JettyLogger.debug(JettyLogger.java:37) at org.eclipse.jetty.io.nio.ChannelEndPoint.fill(ChannelEndPoint.java:254) at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.fill(BlockingChannelConnector.java:242) at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:1040) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:280) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:298) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Unknown Source) 2014-09-22 19:09:28.221 INFO - Logging: Logging to file: /srv/cloud/slots/tr10000/deploy/data/log/logging.log, max size: 2048KiB, max rotation: 10 2014-09-22 19:09:28.337 INFO - Core: Mendix Runtime 5.8.1 (build 2960). Copyright © 2003-2014 Mendix bv. All rights reserved. 2014-09-22 19:09:30.109 INFO - XMPPConnector: appnode-ratash-tr10000@xs4.mendixcloud.net connected. 2014-09-22 19:09:30.121 INFO - XMPPConnector: Registered 'cp@beta.mendixcloud.net/Smack' as cloud portal contact 2014-09-22 19:09:30.195 INFO - Logging: Logging to file: /var/log/appcontainers/tr10000/m2ee.log, max size: 2048KiB, max rotation: 10
asked
1 answers
1

Hi Pieter,

I ran into the same problem today and it turned out to be the Logging module. I had set the log level to TRACE, which seems to put too much pressure on the database. Setting the log level to a different level isn't possible, the app always seems to go back to log level TRACE. Removing the Logging module has resolved this issue for me, though this is not a permanent fix.

I'm going to keep trying to fix this. If I find a solution I'll let you know!

Edit:

I think I have found the issue, it has something to do with the constant 'Level'. See this forum post for more info: https://forum.mendix.com/questions/6772/Use-of-constants-and-the-Sandbox-environment

I was able to set the logging to NONE, but anything else than that doesn't seem to work.

Guess there is nothing left to do but wait for a fix.

answered