|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I can't replicate this issue at all, it works just fine for me with 1.500. Here are some comments from various blogs and forums, please check into these on your system.
"I found we had an old smtp.jar hanging around on our classpath from back in the day. This jar file contains a SMTPMessage, SMTPOutputStream and SMTPTransport classes which must have been conflicting with the ones in mail.jar and/or activation.jar. Simply removing smtp.jar cleaned up my issues with this error."
"As others wrote before me, this error is all about having the matching pair of mail.jar and activation.jar.
At our application the problem was, we had a mail.jar in the /lib directory of our application, but no matching activation.jar. At execution the Tomcat used its own activation.jar which was obviously not the matching pair to our mail.jar. Therefore we got the exception thrown at sending the mail.
The solution which worked in the end was:
to download the newest versions of the jars,
place them into the lib directory of our application,
sort them to top-position in the build-order and rebuild the project."