Troubleshooting Microclimate Developer Tools

When troubleshooting, check the project in Microclimate to make sure the status is what you expect. If not, refer to Microclimate troubleshooting. For Microclimate Developer Tools specific problem solving tips, see the following information.


Check the logs

The logs are found in your Eclipse workspace under .metadata/.log.


Solving common problems

The following list describes common problems that might affect Microclimate Developer Tools.

Test connection fails

If the test connection fails when you are creating a new Microclimate connection, check that Microclimate is up and running. If it is not, see Microclimate troubleshooting.

Open application fails

If the application fails to load in the browser check the following:

  1. Check that the application is running and you can open the application successfully in Microclimate. For more information see Using the project view. If you cannot open the application in Microclimate, see Microclimate troubleshooting.
  2. The default browser in Eclipse might not be able to handle the content of your application. Try using a different browser by clicking on Window > Web Browser. Select a browser from the list and try to open the application again.

Debugger fails to connect

If the debugger fails to connect, you might need to increase the connection timeout:

  1. Open the Eclipse preferences and select Microclimate.
  2. Increase the debug connection timeout value and click Apply and Close.

Application stuck in Starting state

The application might be waiting for the debugger to connect. You can resolve this by right-clicking on the project in the Microclimate Explorer view and selecting Attach Debugger. If the problem occurred because the debugger failed to connect when restarting in debug mode, make sure to increase the debug connection timeout in the Microclimate preferences before trying to debug again. For more information see Debugger fails to connect.

If the debugger is connected but stopped on a ClassNotFoundException, click on the run button to get past the exception. You might need to click run several times as the exception occurs more than once. To avoid stopping on the exception in the future, open the Eclipse preferences and navigate to Java > Debug. Uncheck Suspend execution on uncaught exceptions and click Apply and Close.

If the application is not waiting for the debugger to connect, try restarting the application again. If this does not work, use the Microclimate UI to disable the application and then re-enable it.

Application does not rebuild after making a change

To start a build manually, right click on the Microclimate server in the Servers view and select Start Build. For more information see Building Microclimate projects.

Connection is not showing the correct project list

Try refreshing the connection by right-clicking on it in the Microclimate Explorer view and selecting Refresh. If this does not solve the problem, there could be an issue with Microclimate itself, see Microclimate troubleshooting.

Application is not showing the correct status

Try refreshing the application by right-clicking on it in the Microclimate Explorer view and selecting Refresh. If this does not solve the problem, there could be an issue with Microclimate itself, see Microclimate troubleshooting.