You can try turning off the LDAP email, though I think the core Mailresolver will still use the LDAP email resolver.
On Fri, Jun 15, 2012 at 7:49 AM, vprasad79 <venkat.ibmi...@gmail.com> wrote: > Thanks for response. > But not sure why it getting hanged for one+ hour at this stage. > > We need URGENT help on this issue many jobs fails due to email trigger > errors though build is successful. > > > <http://jenkins.361315.n4.nabble.com/Jenkins-Jobs-hangs-at-sending-email-td4630813.html> > > Email was triggered for: Failure > Email was triggered for: Still Failing > Trigger Failure was overridden by another trigger and will not send an email. > Sending email for trigger: Still Failing > Sending email to: xxx-l...@xxx.com x...@xxx.com x...@xxx.com x...@xxxx.com > x...@xxxx.com x...@xxxxx.com > Notifying upstream projects of job completion > Notifying upstream of completion: FLO-xxxxx #382 > All downstream projects complete! > Minimum result threshold not met for join project > Finished: FAILURE > > > > > > On Thursday, 7 June 2012 23:53:15 UTC+8, slide wrote: >> >> It's trying to lookup the user in LDAP and it can't find it, the LDAP >> plugin is throwing an exception. I have a possible fix for this (at >> least catching the exception) in the works, but have not released with >> it yet. >> >> On Thu, Jun 7, 2012 at 8:34 AM, vprasad79 <venkat.ibmi...@gmail.com> >> wrote: >> > No. we use email-ext plugin. >> > >> > >> > >> > On Thursday, 7 June 2012 22:08:23 UTC+8, slide wrote: >> >> >> >> Is this with the default mailer? >> >> >> >> Sent from my Windows Phone >> >> ______________________________**__ >> >> From: vprasad79 >> >> Sent: 6/7/2012 1:56 AM >> >> To: jenkinsci-users@googlegroups.**com<jenkinsci-users@googlegroups.com> >> >> Subject: Jenkins Jobs hangs at sending email >> >> >> >> Some of our Jenkins jobs get hanged to the point where it says: >> >> >> >> Sending email for trigger: Failure >> >> >> >> Please can you help us. >> >> >> >> >> >> We are using Jenkins ver. 1.458 >> >> Following errors observed in Jenkins log >> >> >> >> WARNING: com.gmail.sikakura.**MailCommandTrigger.run() failed for >> >> MailCommander >> >> >> >> java.lang.NullPointerException >> >> >> >> at >> >> com.gmail.sikakura.**MailCommandTrigger.run(**MailCommandTrigger.java:104) >> >> >> >> >> at hudson.triggers.Trigger.**checkTriggers(Trigger.java:**259) >> >> >> >> >> at hudson.triggers.Trigger$Cron.**doRun(Trigger.java:207) >> >> >> >> at hudson.triggers.SafeTimerTask.**run(SafeTimerTask.java:54) >> >> >> >> at java.util.TimerThread.**mainLoop(Timer.java:512) >> >> >> >> at java.util.TimerThread.run(**Timer.java:462) >> >> >> >> Jun 6, 2012 8:56:30 PM >> >> hudson.security.**LDAPSecurityRealm$**LDAPUserDetailsService >> loadUserByUsername >> >> >> >> WARNING: Failed to search LDAP for username=USERx >> >> >> >> org.acegisecurity.ldap.**LdapDataAccessException: Failed to obtain >> >> InitialDirContext due to unexpected exception; nested exception is >> >> javax.naming.**InterruptedNamingException: Interrupted during LDAP >> operation >> >> >> >> at >> >> org.acegisecurity.ldap.**DefaultInitialDirContextFactor**y.connect(** >> DefaultInitialDirContextFactor**y.java:193) >> >> >> >> at >> >> org.acegisecurity.ldap.**DefaultInitialDirContextFactor** >> y.newInitialDirContext(**DefaultInitialDirContextFactor**y.java:261) >> >> >> >> at >> >> org.acegisecurity.ldap.**DefaultInitialDirContextFactor** >> y.newInitialDirContext(**DefaultInitialDirContextFactor**y.java:241) >> >> >> >> at >> >> org.acegisecurity.ldap.**LdapTemplate.execute(**LdapTemplate.java:123) >> >> >> >> >> >> > >> >> >> >> -- >> Website: http://earl-of-code.**com <http://earl-of-code.com> >> > -- Website: http://earl-of-code.com
