| title | category | tags |
|---|---|---|
Debug Java Actions Remotely |
Monitoring & Troubleshooting |
To debug the Java actions used in a Mendix microflow, you need to make some configuration changes to the way you start the Mendix runtime. This how-to will explain how to manage this.
This how-to will teach you how to do the following:
- Edit the server configuration
- Configure remote debugging
None.
In this section, you will learn how to configure the security at the prototype/demo level. Be aware that this level of security is only applicable for development/demo purposes. This level is available for the quick development of demo applications. It simulates security without the more complex configuration of data access. When deploying to the Mendix cloud, production security is mandatory.
To edit the server configuration with extra JVM parameters, follow these steps:
-
Open the project settings.
-
Edit the configuration.
-
Go to the Server tab on the Edit Configuration editor and add the following line to the Extra JVM parameters field:
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005
-
Next, start your application in Mendix.
In your Java IDE, you need to configure remote debugging. This screenshot shows the configuration in IntelliJ:
- Start the debugger.
- Place some breakpoints in your Java code.
- Start debugging.
- How to Find the Root Cause of Runtime Errors
- How to Clear Warning Messages in Mendix
- How to Test Web Services Using SoapUI
- How to Monitor Mendix using JMX
- How to Log Levels
- How to Debug Microflows
- How to Debug Java Actions
- How to Common Mendix SSO Errors
- How to Debug Microflows Remotely
- How to Get Started with Nexus Maven Repository Manager
- How to Use Eclipse to Debug Your Tomcat Web Application
- How to Profile Mendix Using JProfiler