Discovery Pattern Debug Step - Failure

[derekkitzelman]

I have created a new discovery pattern for Mule Services.   In the first step, I am attempting a Match operation on the $process.executable Contains "java".   When testing the step in debug mode, I get a "Debug Step -   Failure" dialog with the following message:

Debug failed, switched back to the failed step.

Please check the step for a wrong input.

Error Message:

Debug run failed

I am able to communicate with the endpoint and have the appropriate credentials configured, as the Get Process operation returns running processes.   Any ideas?

[derekkitzelman]

I just though of another question:

When performing Identification for HTTP(S) entry point type(s), does debug utilize the SSH port or does it utilize 80/443?

[jake_mckenna]

For the first question i am not sure what might be causing that. A screen shot might help.

For the second questions the HTTP identification will first utilize the port 22 to get to the host and based on the entry point it will look for a process on using 80/443 to bind the process variable to for use in the patterns.

[glennpinto]

If you are in debug mode, to the right you should see the value of that variable, $process.executable. Is it identified to the right with a value that contains java? Are you spelling it correctly? You can drag any variable from the right pane to the field in the match statement to avoid typos if need be. Yes a screen shot would be helpful.

[derekkitzelman]

Everytime I attempt to run in debug mode, it swtches from process to endpoint.

Pre Debug:

In debug mode: