java.lang.IllegalArgumentException: Property "message" not set. One or more of them must be set

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • The text below is from the bottom of this thread: http://www.nabble.com/pop3-receiver-problem-t4646174.html (from Davide Piazza). It covers an exception that occurs when a POP3 listener has received an email, passed it to a configured filter, and the filter does not accept the email. In this situation, instead of ignoring the email and continuing, an exception is thrown. <start thread text snippets> There is a problem with the org.mule.providers.email.RetrieveMessageReceiver.handleUnacceptedFilter method because it return null and thus in the line RequestContext.setEvent(new MuleEvent(message, endpoint, new MuleSession(message, new NullSessionHandler()), synchronous)); the new MuleSession constructor gets a null message and throws this exception: Root Exception stack trace: java.lang.IllegalArgumentException: Property "message" not set. One or more of them must be set at org.mule.impl.MuleSession.<init>(MuleSession.java:104) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:317) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:251) at org.mule.providers.email.RetrieveMessageReceiver.messagesAdded (RetrieveMessageReceiver.java:143) at org.mule.providers.email.RetrieveMessageReceiver.poll(RetrieveMessageReceiver.java:305) at org.mule.providers.PollingReceiverWorker.run(PollingReceiverWorker.java:47) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:528) at java.lang.Thread.run(Thread.java:619) When the filter rejects the message new MuleSession(null, new NullSessionHandler()), synchronous) is called. That's why the exception and the ERROR log message. I think this should be handled in a different way. <end of thread snippets> Thanks to Davide Piazza for researching this!
    via by Steve Olson,
  • The text below is from the bottom of this thread: http://www.nabble.com/pop3-receiver-problem-t4646174.html (from Davide Piazza). It covers an exception that occurs when a POP3 listener has received an email, passed it to a configured filter, and the filter does not accept the email. In this situation, instead of ignoring the email and continuing, an exception is thrown. <start thread text snippets> There is a problem with the org.mule.providers.email.RetrieveMessageReceiver.handleUnacceptedFilter method because it return null and thus in the line RequestContext.setEvent(new MuleEvent(message, endpoint, new MuleSession(message, new NullSessionHandler()), synchronous)); the new MuleSession constructor gets a null message and throws this exception: Root Exception stack trace: java.lang.IllegalArgumentException: Property "message" not set. One or more of them must be set at org.mule.impl.MuleSession.<init>(MuleSession.java:104) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:317) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:251) at org.mule.providers.email.RetrieveMessageReceiver.messagesAdded (RetrieveMessageReceiver.java:143) at org.mule.providers.email.RetrieveMessageReceiver.poll(RetrieveMessageReceiver.java:305) at org.mule.providers.PollingReceiverWorker.run(PollingReceiverWorker.java:47) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:528) at java.lang.Thread.run(Thread.java:619) When the filter rejects the message new MuleSession(null, new NullSessionHandler()), synchronous) is called. That's why the exception and the ERROR log message. I think this should be handled in a different way. <end of thread snippets> Thanks to Davide Piazza for researching this!
    via by Steve Olson,
    • java.lang.IllegalArgumentException: Property "message" not set. One or more of them must be set at org.mule.impl.MuleSession.<init>(MuleSession.java:104) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:317) at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:251)
    No Bugmate found.