Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via MuleSoft JIRA by Andrew Perepelytsya, 1 year ago
did not receive 1 mail expected:<1> but was:<0>
via MuleSoft JIRA by Andrew Perepelytsya, 1 year ago
did not receive 1 mail expected:<1> but was:<0>
junit.framework.AssertionFailedError: did not receive 1 mail expected:<1> but was:<0>	at org.mule.providers.email.functional.AbstractEmailFunctionalTestCase.doSend(AbstractEmailFunctionalTestCase.java:114)	at org.mule.providers.email.functional.SmtpsFunctionalTestCase.testSend(SmtpsFunctionalTestCase.java:23)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:208)	at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:178)	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)