java.lang.IllegalArgumentException: usergrid.cluster_name property must be set.

Google Groups | Hamza Bouzidi | 5 months ago
  1. 0

    sergrid.cluster_name property must be set.

    Google Groups | 5 months ago | Hamza Bouzidi
    java.lang.IllegalArgumentException: usergrid.cluster_name property 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
  3. 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
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    terms weights

    Google Groups | 1 year ago | Al
    java.lang.IllegalArgumentException: *-luceneindexpath must be set.*

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      usergrid.cluster_name property must be set.

      at org.apache.usergrid.persistence.core.guice.SettingsValidationCluster.<init>()
    2. org.apache.usergrid
      CommonModule.configure
      1. org.apache.usergrid.persistence.core.guice.SettingsValidationCluster.<init>(SettingsValidationCluster.java:17)
      2. org.apache.usergrid.persistence.core.guice.CommonModule.configure(CommonModule.java:99)
      2 frames