In order to troubleshoot this, we would like you to ask for 2 extra bits of information:
- a log file
- a thread dump, taken when the progress bar has just stalled
For the the thread dump, you can use jps to determine the PID for the process (the relevant process is called "Main") and then use jstack <pid> to get a thread dump for that process. That should give us some insights into what the container is doing at the moment where it stalls.
This could be related to https://ops4j1.jira.com/browse/PAXWEB-537 or https://ops4j1.jira.com/browse/PAXWEB-548 - the former is fixed in Pax Exam 1.1.13, so you could give that a try to see if it fixes your problem.
To upgrade your container to Pax Web 1.1.13
- stop the container and remove the data folder
- edit the system/org/apache/karaf/assemblies/features/standard/2.3.0.fuse-71-047/standard-2.3.0.fuse-71-047-features.xml file
change the version in every mvn: url for pax-web you find in this file, e.g. mvn:org.ops4j.pax.web/pax-web-api/1.1.9 becomes mvn:org.ops4j.pax.web/pax-web-api/1.1.13
If you start the container again afterwards, you should see pax-web 1.1.13 show up in the bundles list when you do an "osgi:list -t 0 | grep pax". If that doesn't fix your problem yet, we might have to wait a few more days for 1.1.14 to become available and then give it another go with that one.