something went wrong while deploying your app to the sandbox

0
I like to play in the sandbox... Am I to old for that? because My first Run in Sandbox gives the warning wrote in the subject. This is what is written in the logfile: 2014-06-20 12:05:38.778 INFO - Logging: Logging to file: /srv/cloud/slots/tr10026/deploy/data/log/logging.log, max size: 2048KiB, max rotation: 10 2014-06-20 12:05:38.819 INFO - Core: Mendix Runtime 5.5.0 (build 2161). Copyright © 2003-2014 Mendix bv. All rights reserved. 2014-06-20 12:05:39.838 INFO - XMPPConnector: appnode-bis-tr10026@beta.mendixcloud.net connected. 2014-06-20 12:05:39.855 INFO - XMPPConnector: Registered 'cp@beta.mendixcloud.net/Smack' as cloud portal contact 2014-06-20 12:05:40.002 INFO - Logging: Logging to file: /var/log/appcontainers/tr10026/m2ee.log, max size: 2048KiB, max rotation: 10 2014-06-20 12:05:41.659 INFO - ConnectionBus: Executing 156 database synchronization command(s)... 2014-06-20 12:05:42.022 INFO - ConnectionBus: Executing database synchronization commands finished. 2014-06-20 12:05:42.056 INFO - ConnectionBus: Database: PostgreSQL 9.2.4, name: 'dbnode-bis-db26' Driver: PostgreSQL Native Driver PostgreSQL 9.2 JDBC4 (build 1002) 2014-06-20 12:05:42.244 INFO - Core: Project company name is 'Mendix' 2014-06-20 12:05:42.244 INFO - Core: License expiration date is 'null' 2014-06-20 12:05:42.244 INFO - Core: License type is: 'Perpetual' 2014-06-20 12:05:43.347 INFO - Core: Running after-startup-action... 2014-06-20 12:05:43.364 INFO - AppCloudServices: Starting OpenId handler ... OpenIDReturnURL = https://proberen.mendixcloud.com/openid/callback; OpenIdProvider: https://mxid2.mendixcloud.com/mxid2/discover 2014-06-20 12:05:44.019 INFO - AppCloudServices: Starting OpenId handler ... DONE 2014-06-20 12:05:44.022 INFO - Core: Successfully ran after-startup-action. 2014-06-20 12:05:44.091 INFO - Core: Mendix Runtime successfully started, the application is now available. 2014-06-20 12:10:34.893 INFO - Core: Mendix Runtime is shutting down now... 2014-06-20 12:10:34.931 INFO - Core: Mendix Runtime is now shut down. 2014-06-20 12:11:06.982 WARNING - M2EE: Unsupported JVM (Java(TM) SE Runtime Environment 1.7.0_51). Use at your own risk. Please check https://world.mendix.com/display/refguide3/System+Requirements. 2014-06-20 12:11:07.292 INFO - Logging: Logging to file: /srv/cloud/slots/tr10026/deploy/data/log/logging.log, max size: 2048KiB, max rotation: 10 2014-06-20 12:11:08.059 INFO - XMPPConnector: appnode-bis-tr10026@beta.mendixcloud.net connected. 2014-06-20 12:11:08.074 INFO - XMPPConnector: Registered 'cp@beta.mendixcloud.net/Smack' as cloud portal contact 2014-06-20 12:11:08.206 INFO - Core: Mendix Runtime 4.8.3 (build 957). Copyright © 2003-2014 Mendix bv. All rights reserved. 2014-06-20 12:11:08.596 INFO - Logging: Logging to file: /var/log/appcontainers/tr10026/m2ee.log, max size: 2048KiB, max rotation: 10 2014-06-20 12:11:14.285 INFO - Core: The MxRuntime is shutting down now... 2014-06-20 12:11:14.285 INFO - Core: The MxRuntime is now stopped.
asked
2 answers
0

The error suggest that the system did not recognize the java version used. But since the current version is 1.7.0_60 it is strange that this error was generated. May be somebody from Mendix could explain this one. Have not played with the sandbox much. You could raise a support ticket for this one.

Regards,

Ronald

answered
0

Hello Jan, I see this post is two years old however it has not been closed. Please make sure that the node you are deploying is a licensed node and that you have the correct node security setting permissions. Also an attempt to deploy to another node could rule this and other troubleshooting thoughts out of the question. Please try this as well. If you have not done so already please submit a support ticket and we will look at the runtime connections, the specific cloud node connection, etc., appnode-bis-tr10026. Keep note there is a similar ticket, so other developers may have experienced the same XMPP connection issue. https://forum.mendix.com/questions/9352/Application-node-does-not-start-after-clear-environment Thanks, Michael Schlosser

answered