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?

[jake_mckenna]

That makes me think that from whatever you are passing in as the entry point it is not finding the process to bind to. That table variable is only available if the entry point can find it based on the port.

[jake_mckenna]

Since this is a custom pattern you created what did you set the find process strategy to on the identification pattern?

[derekkitzelman]

I set it up as HTTP(S) and TCP as endpoint types.   I set Process strategy as listening_port.   If I add a step before my match operation and perform a get process operation, the running processes are returned in a table and the ones I'm interested in are present.

[Ankush13]

I will advise you to look for anything other than java in executable. That is way too generic and there might be other processes that you may come across with java in them. Probably and second step with another string/file is a better identification criteria