1 Reply Latest reply on Jan 27, 2015 3:59 PM by geert1

    Remote Debug on Fuse Fabric Container


      Hi all, I need to use remote debug on my fabric container. If I use Fuse Standalone instance, I enable remote debug on 5005 port and I can attach at it using eclipse. How can I enable remote debug on single instance of fabric?





        • 1. Re: Remote Debug on Fuse Fabric Container

          Hi Luca,


          When you create a container in fabric you can specify which options should be passed to the container. This way you can set the amount of memory for instance, but you can also specify that the container should start in debug modus.

          The following Fuse CLI command would create a container with a maximum heap size of 256 MB:


          container-create-child --jvm-opts "-Xmx256m" root child


          In the Hawt.io console you'll find the "Jvm opts" option under the "Advanced" tab on the container creation page.

          Now you can also use this to pass the regular debug commands to a JVM: "-Xdebug -Xrunjdwp:transport=dt_socket,address=5001,server=y,suspend=n".

          The CLI command would then look like this:


          container-create-child --jvm-opts "-Xdebug -Xrunjdwp:transport=dt_socket,address=5001,server=y,suspend=n" root child


          The suspend=n part means that the JVM won't wait for a debugger to connect but will startup like usual. If you need to see what happens in the JVM right after it starts you can change this to suspend=y. The JVM will then block until a debugger is connected.


          Good luck!