Hi Shan,
You say:
"i have created a folder callled ycDebug
and a folder called rfolder1
and a flow service callled reciveAutoMail "
… if this is the case, then the receive service you should configure is actually:
Global service : ycDebug.rfolder1:reciveAutoMail
Did you mean you created a package ‘ycDebug’ and a folder ‘rfolder1’?
You can copy/paste the service name from Developer to make sure the parameter in the email listener is 100% the same.
More hints:
Debug in java services can be tricky. System.err.println(…) will dump the output to stdout, and if you’re after something quick and dirty then this is often good enough for prototyping.
Try invoking a flow service instead where you can savePipelineToFile. This will remove some of the troubleshooting complexities from your scenario involving an invoked java service.
You can enable enhanced logging on the Integration Server where you are configuring this email listener (and thereby remove the need to ‘guess’ what the problem is) by using the HTML administration console Settings > Logging; move the log level to 8 or 10 and enable the following facility: 0068 Email Listener. This will log more detail to the Server log.
The Error log may already have information on the problem.
NOTE: Remember to re-enable all facilities when you’re finished since this filtering affects the entries written to the server log - it’s quite common to think the server isn’t started simply because someone has changed the logging levels so you don’t see the ‘Initialization completed’ message.
Regards,
Adrian
#webMethods#webMethods-General#Integration-Server-and-ESB