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

MuleSoft JIRA | Steve Olson | 9 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    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!

    MuleSoft JIRA | 9 years ago | Steve Olson
    java.lang.IllegalArgumentException: Property "message" not set. One or more of them must be set
  2. 0

    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!

    MuleSoft JIRA | 9 years ago | Steve Olson
    java.lang.IllegalArgumentException: Property "message" not set. One or more of them must be set

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Property "message" not set. One or more of them must be set

      at org.mule.impl.MuleSession.<init>()
    2. org.mule.impl
      MuleSession.<init>
      1. org.mule.impl.MuleSession.<init>(MuleSession.java:104)
      1 frame
    3. org.mule.providers
      AbstractMessageReceiver.routeMessage
      1. org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:317)
      2. org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:251)
      2 frames