Azure deployment JVM error

Hi, I followed the 'How to deploy a mendix app on Azure' but when after unpacking the deployment package and trying to start the application in m2ee I get the following error: m2ee(MxAdmin): start INFO: Trying to start the MxRuntime... CRITICAL: Unable to determine JVM startup parameters. Traceback (most recent call last): File "/usr/bin/m2ee", line 1069, in <module> cli.cmdloop() File "/usr/lib/python2.7/", line 142, in cmdloop stop = self.onecmd(line) File "/usr/lib/python2.7/", line 221, in onecmd return func(arg) File "/usr/bin/m2ee", line 67, in do_start self._start() File "/usr/bin/m2ee", line 131, in _start if not self.m2ee.start_appcontainer(): File "/usr/lib/python2.7/dist-packages/m2ee/", line 86, in start_appcontainer if not self.runner.start(): File "/usr/lib/python2.7/dist-packages/m2ee/", line 130, in start ' '.join(cmd)) TypeError: can only join an iterable ERROR: Starting the JVM process did not succeed... m2ee(MxAdmin): create_admin_user WARNING: The application process needs to be running to create a user object in the application. I used the BYOL Mendix VM deployment package on Azure. The uploaded app was build with MX6.3.1 Does somebody know how to set the correct configuration for this to run? The sample application that is already present in the model_upload directory works fine after downloading the correct runtime for this. As requested, here is the yaml file: for advanced configuration, check out `zless /usr/share/doc/m2ee-tools/examples/full-documented-m2ee.yaml.gz` mxnode: download_runtime_url: m2ee: app_name: Gonzo Test App (Change app_name in /srv/app/m2ee-config.yaml) app_base: /srv/app/ admin_port: 9000 admin_listen_addresses: ",::1" admin_pass: unsafe-password-for-local-access-only runtime_port: 8000 runtime_listen_addresses: ",::1" pidfile: /home/MxAdmin/.m2ee/ javaopts: [ "-Xmx512M", "-Xms512M", "-Dfile.encoding=UTF-8", "", ] database_dump_path: '/srv/app/data/database' model_upload_path: '/srv/app/data/model-upload' logfile: /srv/app/data/log/out.log logging: - type: file name: FileSubscriber autosubscribe: INFO # File to log to. filename: /srv/app/data/log/out.log max_size: 10485760 max_rotation: 10 mxruntime: ApplicationRootUrl: ScheduledEventExecution: ALL MicroflowConstants: # put microflow constants in here # Module.Constant: value DatabaseType: PostgreSQL DatabaseHost: "" DatabaseName: mendixdb DatabaseUserName: mendixdb DatabasePassword: mendixpassword ConnectionPoolingMaxActive: 50 ConnectionPoolingMaxWait: 10000 ConnectionPoolingMaxIdle: 50 ConnectionPoolingMinIdle: 5 ConnectionPoolingNumTestsPerEvictionRun: "-10" ClientQueryTimeout: 70 LogMinDurationQuery: 10000 SessionTimeout: 600000 Thanks, Gonzo
2 answers

If you upgrade m2ee-tools this will be fixed, we will release new virtual machine images with this fix included.

You can run

sudo - su

to get a root prompt.

Then the following three commands:

echo "deb jessie main contrib non-free" > /etc/apt/sources.list.d/mendix.list
apt-get update
apt-get dist-upgrade

Follow the dialog by mostly answering "yes" to the questions. In the process, the python-m2ee and m2ee-tools packages should be upgraded.

After this, run "exit" to get back to the normal user prompt. Then try deploying via m2ee again and this problem should be solved.


The error message you are getting is something I would expect to see when the yaml configuration file hasn't been formatted correctly. Could you share the yaml file with us so we can help you review this?

Remember white spaces (indentation), the - character, and quotes are really important since they make up the format. I would guess in this example you are either missing a - or the indentation of a list of properties is incorrect.
Please confirm your format against this specification: