The error message "Component bundles are not loaded" means that your project.jar (the jar containing java action class files and java action registration code) was not built correctly. The two main causes of this error are:

1. Compilation error(s) in a Java action. In that case you get an error message in the Modeler as well, when trying to run your project. Pressing "Proceed" in that case will lead to the "Component bundles are not loaded" error message.
2. If you use 5.5.0 with the experimental "run optimizations" enabled ("Edit" -> "Preferences" -> "Enable run optimizations"), this error can also occur in certain situations . This has been fixed in 5.6.2, so you can either upgrade to 5.6.2 or disable the "run optimizations" (as Thijs suggested) to solve this.

Hope this helps to resolve your problems.

Edit: The "Proceed" button is not there anymore in the latest Modeler version, you can only click "Close" when Java action compilation fails. In Eclipse you can probably get the error message if you ignore compilation errors in java source.

Edit: One other cause of this error message could be something like a static initializer in a userlib class, which is triggered during runtime startup. You should have another error message above this one in your console though, which shows the stacktrace of that error.

This error is back. I'm using version 5.14.0 and I still get it.

Last night the issue occurred again. I tried restarting and also checking / installing new windows updates, both did not work. But installing a windows update took long time so I decide to plug in the laptops power so the CPU would be maximized. I also thought let's try running the app now.  And yes, it started!

Model version: 6.10.2. I tested 2 different branches.

Laptop: Lenovo Thinkpad P51

I unplugged the power, ran again.. ‘components bundles are not loaded’ !

Plugged the power, ran app again and it started just fine. I tested this several times. Seems to do the trick. 

Power unplugged: ‘components bundles are not loaded’.

Power plugged: App starts just fine!

In my case, adding different (versions of) App Store components in the past had made a mess of the userlib folder. Several libraries were added twice or even more times, sometimes with different version numbers. I ended up removing the following JARs:

antisamy-1.4.4.jar
com.springsource.org.apache.commons.httpclient-3.1.0.jar
com.springsource.org.apache.commons.lang-2.5.0.jar
commons-email-1.3.1.jar
commons-lang-2.6.jar
jsch-0.1.46.jar
org.apache.commons.lang3.jar

because the following JARs made them obsolete:

antisamy-1.5.3.jar
commons-httpclient-3.1.jar
org.apache.commons.lang3-3.1.0.jar
commons-email-1.4.jar
org.apache.commons.lang3-3.1.0.jar
jsch-0.1.48.jar
org.apache.commons.lang3-3.1.0.jar

(Technically, lang & lang3 are different libraries, but they’re so similar that it was easy to change the few references which remained.)

Hi,

I'm using 5.3.2 now and I still have the same problem.

I no longer received this error once I upgraded to 5.6.

Mine works now too. I had the same error when starting the applicaton through the mendix service console. What solved it i guess was creating a deployment package over and over and eventually found the deployment package being much larger than the previous. Updated with that one and it worked..

In Mx5.5.0, disable the 'run optimizations' (Preferences, General) and it should work.

This error has appeared in MX Runtime 5.19 (Build: 5730)

Had this issue for second time now in Mendix 6.10.2.  Clean deployment Directory didn't work, restarting my laptop did work for me. 

I’ve seen that the error always occurs (for me) 45 seconds after startup. I don’t know about how Felix / OSGi is designed, but it makes sense to have some kind of timeout during startup. That would explain why cleaning up the userlib folder helps (see my other answer) but not always. Using a (virtual) machine with more resources might help too.

I was hoping that there would be some framework configuration property to extend this timeout period, but I could not find anything in the documentation: https://felix.apache.org/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html

This article might contain some more pointers towards a final solution: http://apache-felix.18485.x6.nabble.com/How-to-improve-the-start-time-of-Apache-Felix-td5004833i20.html

In my case, killing tsvncache.exe did the trick. I found the culprit using Process Explorer (from Microsoft Sysinternals) and search for the name of the folder that contains my Mendix projects. See also https://serverfault.com/a/1980.

In my case, killing tsvncache.exe did the trick. I found the culprit using Process Explorer (from Microsoft Sysinternals) and search for the name of the folder that contains my Mendix projects. See also https://serverfault.com/a/1980.

In my case, killing tsvncache.exe did the trick. I found the culprit using Process Explorer (from Microsoft Sysinternals) and search for the name of the folder that contains my Mendix projects. See also https://serverfault.com/a/1980.

In my case, killing tsvncache.exe did the trick. I found the culprit using Process Explorer (from Microsoft Sysinternals) and search for the name of the folder that contains my Mendix projects. See also https://serverfault.com/a/1980.