[JIRA] (JENKINS-6463) Builds hanging right before e-mail notifications are sent out

[cron...@gmail.com (JIRA)]

Robert Cronk commented on JENKINS-6463 Builds hanging right before e-mail notifications are sent out A few minutes later, the stack trace for that thread looks a little different but it's still hung sending email: Executor #-1 for master : executing driver-smoketest.linux #1235 "Executor #-1 for master : executing driver-smoketest.linux #1235" Id=374602 Group=main RUNNABLE at java.lang.Throwable.getStackTraceElement(Native Method) at java.lang.Throwable.getOurStackTrace(Throwable.java:608) - locked java.lang.Throwable@7b0035af at java.lang.Throwable.getStackTrace(Throwable.java:599) at org.apache.commons.logging.impl.Jdk14Logger.log(Jdk14Logger.java:89) at org.apache.commons.logging.impl.Jdk14Logger.debug(Jdk14Logger.java:114) at org.apache.commons.beanutils.BeanUtilsBean.populate(BeanUtilsBean.java:814) at org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:433) at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:251) at org.apache.commons.digester.Rule.begin(Rule.java:152) at org.apache.commons.digester.Digester.startElement(Digester.java:1361) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1340) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:741) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) at org.apache.commons.digester.Digester.parse(Digester.java:1631) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:49) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:24) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:832) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:806) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:358) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1419) at hudson.model.User.getProjects(User.java:409) at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:530) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:396) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:273) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265) at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:69) at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:600) at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:381) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:287) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) The log looks like this (hung forever - or for an hour, or for 9 hours). And yes, ours is intermittent too, so it's not just a bad email addresses: . . . Email was triggered for: Failure Sending email for trigger: Failure

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