[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni edited a comment on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry, Alex confused you with someone else .. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Same with you as well? 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl resolved JENKINS-16746 as Not A Defect Unable to send email since Jenkins 1.500 Duplicate activation.jar in tomcat Change By: Alex Earl (22/Feb/13 1:42 PM) Status: Reopened Resolved Resolution: Not A Defect 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Hey alex try searching for find -iname *activation*.jar 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Yes, Alex. Our tomcat server had been recently deployed with another webapp which had a different version of activation.jar. I had undeployed this new application and everything is back to normal. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Ravi is this issue "fixed" for you then? 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 You can add the same options in bin/catalina.sh under the first line as: #!... JAVA_OPTS=$JAVA_OPTS" -Dmail.debug=true" ...Some copyright info... (OR) #!... JAVA_OPTS=$JAVA_OPTS:"-Dmail.debug=true" ...Some copyright info... 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry but I disagree. According to find / -name "jenkins.xml" there is no jenkins.xml on the whole filesystem. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 You can enable is in jenkins.xml with the options to the JVM. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni edited a comment on JENKINS-16746 Unable to send email since Jenkins 1.500 Note, after debugging: The issue that I faced: Had activation.jar in another webapp on same tomcat I learnt that(just now) tomcat uses common class loader(might be wrong). Hence it loaded both in to classpath/memory and created all this fuss I have undeployed the other application for now, jenkins is properly able to send email 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 If anyone has any idea what has happened. Please do share it. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Note, after debugging: The issue that I faced: Had activation.jar in another webapp on same tomcat I learnt that(just now) tomcat uses common class loader. Hence it loaded both in to classpath/memory and created all this fuss I have undeployed the other application for now, jenkins is properly able to send email 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry to bother you again with such a stupid question: But how do I enable this? I know that I have to add this line to the java arguments: -Dmail.debug=true But I don't see where. Do I have to put it under /etc/defaults/jenkins or unter /etc/init.d/jenkins? 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 The JavaMail library version didn't change in email-ext, so something must be conflicting in the classpath or something. Can you enable JavaMail debug and post the log (it will go to the Jenkins log file)? 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 I have some updates for you: I you configure smtp to send emails without SMTP-Auth it works just fine! So it must have something to do with the javamail libarys. Cause Atlassian does have the EXACT same problem in Jira and Confluence... 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry for the late response. Yes I have tried both TLS and non-TLS. Here is the error message when I use TLS: Das Versenden der E-Mail ist fehlgeschlagen javax.mail.MessagingException: Could not connect to SMTP host: exchange.hlp.de, port: 465; nested exception is: java.net.ConnectException: Connection refused at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:317) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.Mailer$DescriptorImpl.doSendTestMail(Mailer.java:499) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(Abstra
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Did you try both TLS and non-TLS? Also, can you enable debug mode in the email-ext plugin and debug mode in the JavaMail API (see http://www.oracle.com/technetwork/java/faq-135477.html#debug)? 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 find / -name "smtp.jar" came up with no result. Their is no smtp.jar on the whole system. find / -name "mail.jar" came up only with results within our jenkins workspace directory. find / -name "activation.jar" came up with results within our jenkins workspace directory and one result at this position: /usr/share/java/activation.jar I don't know if their should be a mail.jar under /usr/share/java/ but that is the only thing that got my attention. The thing is, that Atlassian have had (nearly) the same issue: https://confluence.atlassian.com/display/JIRAKB/No+authentication+mechansims+supported+by+both+server+and+client+when+Configuring+Microsoft+Exchange+SMTP+Server But I don't know if the provided solution will work here in the same way. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 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." 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni reopened JENKINS-16746 Unable to send email since Jenkins 1.500 In that case, lets just keep it open if someone wants to fix it. Change By: Ravi Teja Lokineni (12/Feb/13 12:31 PM) Resolution: Won't Fix Status: Resolved Reopened 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 René, You must not know how frustrating it is to try and develop an plugin on my own time, with no pay and have to deal with a constantly changing target for features and issues. Most plugins are geared to work with the LTS version of Jenkins just for this reason. I'm sorry you are having an issue, if you want to reopen the issue, that is fine, I probably won't be able to get to it very soon. Feel free to debug and submit a pull request if you want to. Alex 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Hi Alex, you are really funny. I already tried downgrading on my debian system: I used this syntax: apt-get install pkg=version root@hlpjenkins01:~# apt-get install jenkins=1480 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen... Fertig E: Version »1480« für »jenkins« konnte nicht gefunden werden It says that there was no such version found. It tested with other version numbers without any luck. But the really funny thing is your behaviour. There seems to be a bug, but instead of investigating the reason for this bug (not to mention fixing it) you recommend downgrading and close the ticket with the solution "won't fix". Just like the bug will went away just by itself. Sorry for inconvenience I'll find a way by my own to work around this bug. Kind Regards René 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl resolved JENKINS-16746 as Won't Fix Unable to send email since Jenkins 1.500 This won't be fixed as email-ext is developed against the LTS releases, the latest of which is 1.480.x Change By: Alex Earl (11/Feb/13 8:21 PM) Status: Open Resolved Resolution: Won't Fix 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 I would recommend downgrading, from what I have gathered, many people are having issues with 1.500. Also, email-ext is only tested with the latest LTS, so running something newer than that it is definitely possible to run into issues. 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Hello at all, we have nealry the same problem. Except that our test e-mail won't be sent either. It all started after we upgraded to Jenkins 1.500 If I try to send a test e-mail I get the following error message: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:756) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:669) at javax.mail.Service.connect(Service.java:317) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.Mailer$DescriptorImpl.doSendTestMail(Mailer.java:499) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Is there anything I can do to narrow down the problem? Kind Regards René
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 The only thing I could find on an issue like this is the following page [1]. Can you try what it says in there and see if that fixes your issue? Also, can you try enabling mail debug mode for JavaMail [2]? 1 - http://www.jguru.com/faq/view.jsp?EID=237257 2 - http://www.oracle.com/technetwork/java/faq-135477.html#debug 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Nothing was changed in the settings, everything was as-is since Jenkins 1.4xx 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.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni created JENKINS-16746 Unable to send email since Jenkins 1.500 Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 11/Feb/13 7:04 AM Description: Note: The default 'test configuration email' sent mail successfully but after build finishes the plugin is not able to send mail Stacktrace: ERROR: Could not send email as a part of the post-build publishers. javax.mail.MessagingException: IOException while sending message; nested exception is: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_34_1307232537.1360285420086" at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:308) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_34_1307232537.1360285420086" at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:877) at javax.activation.DataHandler.writeTo(DataHandler.java:302) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) ... 13 more Project: Jenkins Priority: Critical Reporter: Ravi Teja Lokineni 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.
