javax.mail.MessagingException: There are 51 comments already against the issue [] which exceeds the configured default: 50

JIRA | Francis Martens (iDalko) | 6 years ago
  1. 0

    In order to test if JEMH-258 and JEMH-265 in the latest 0.9.5.1 plugin version, I have created a test environment JIRA, version 4.1.2 build 531. Now here is my emh-ecr.properties file content: {code} # This is an example of the configuration file that can be used with EMH, # to refer to it, follow instructions on http://confluence.atlassian.com/x/CIIKCg # and set 'options' along the lines 'configFile=emh.properties' # # This represents a minimal configuration, options can be enabled as required #------------------------- # Default options for the handlers # # If supplied, will be used where emails cannot get their reporter identified, if left unspecified, emails will not be processed defaultReporterUsername=ecr@*****.com # If the default is used, this field indicates how it should be applied. Default is false. Setting true would then cause sender email address # lookups resulting in perhaps a real Jira user to be ignored. #defaultReporterOverridesDerivedReporter=true # If set, inbound issues will _always_ get assigned to someone, checking first the Component Owner, then the Lead #enableAutomaticIssueAssignee=true # If enabled, will assign the full email address of the initiator to the given custom field, # enabling registered/non-registered jira users to receive notifications IF further event handling code # is in place to use this custom field value # assignNonJiraUsersOriginalEmailAddressToCustomField=somefield # assignJiraUsersOriginalEmailAddressToCustomField=someotherfield ## ## Global Defaults ## # Mandatory entry defaultIssueType=ECR # Mandatory entry defaultPriority=4 # Mandatory entry defaultIssueLinkType=relates # If set, will be used as subject text, the reduce risk of unwanted issue rejections defaultSummary=The sender did not provide a summary # If set, will allocate inbound issues to the nominated IF no project could otherwise be identified, # for instance, if projectAutoAssign (the [name] part from the TO: addressee [name]@someco.com), was unable to find a matching project key, # this project would be used as a fallback, preventing issues getting 'stuck' # project defaultProject=ECR # If the project is the default project and no valid component is set, this will be applied #defaultComponent=inbox # Default Custom Field Values # During issue creation _only_ it is possible to check for these values *in the absence of any duplicate directives in the email, that always take precendence* # Multiple values or Cascade Select values can be provided, are comma delimited (no spaces, eg x,y,z) # Keys are URLEncoded, meaning for example that the SPACE character becomes a + # Keys are case sensitive # Keys must be prefixed with 'defaultCF.' # eg: defaultCF.Carbon+Copy=andy # Default Workflow Field Values # Specifies a default workflow advance that will be applied to new issues if defined #defaultWorkflowAdvance=Start # During workflow transitions, some fields are needed, some can be derived from the existing issue (eg assignee), some need to be set (eg resolution) # Like CustomField values above, keys are urlencoded. # eg: defaultWorkflowField.resolution=fixed defaultWorkflowField.resolution=fixed ## ## Project specific defaults, taking precedence over global defaults ## ## (i) only keys listed below are implemented ## ## Specifying a CSV regexp set of email addresses/domains for a given project KEY will, in the absence of a specific directive, set the project to be that KEY, rather than use the global default #projectDefault.ABC.domainFromMatches=fromtest@noplace.com #projectDefault.XYZ.domainAddresseeMatches=project-[a-z]*@jira.myco.net # # Worklog defaults # # If set will ensure that so long as no overriding role is provided, that worklog comments will be created with this role for visibility #defaultWorklogSecurityRole=Developers # Alternatively, you can set a default Group. NOTE: defaultWorklogSecurityRole and defaultWorklogSecurityGroup are mutually exclusive, first *valid* one tested wins. #defaultWorklogSecurityGroup=your-special-group #----------------- # Debug - Print the mail out in the server logs to figure out problems # example: debugPrintEmail=true #debugPrintEmail=true # # Default due date format, see http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html for format examples # any provided dueDateFormat would override this # defaultDueDateFormat=dd/MMM/YYYY #------------ # Misc Config # # Strict Jira Permissions, this is here to make some peoples configurations a little less strict, # by default, strict permissions are applied, eg for managing watchers, you need the MANAGE_WATCHERS permission, # but if you do that, you will give that permission in the UI also. Enabling this option with a 'false' value # will cause such permissions to be not checked for, the default behaviour is 'true'. # #strictJiraPermissions=false # # JEMH-116, provide a CSV (ie mulitple values possible) regexp matching JEMH inbound email addresses that users use to get mail into JEMH/Jira, # enabling all TO: / CC: addresses to be scanned for: # a) 'projectAutoAssign' purposes # b) removal of erroneous entries that would otherwise be possibly processed with cc: # jemhAddresseeRegexps=[a-z|A-Z|0-9|_|-]*@jira.myco.net # # Enable this to add an indicator at the top of a mail which processor handler the mail # indicateWhichProcessorProcessedMail=true # # Enable this to enable an indicator at the head of each email for # indicateEmailDetailsForAnonymousIssueCreation=true #------------ #If enabled will cause the outbound mail queue to flush whenever a comment is received or an issue processed # #autoFlushMailQueue=true # If this option is enabled, it will allow the user associated with the email sender to be used for security checks, enabling simplified security setup of target projects. # useEmailSenderForSecurityChecks=true ## Messages marked as Bulk handling, values are [forward|delete|ignore] #bulk=forward # If using a case sensitive DB, need to define the userid Case for matching otherwise EXACT matches will be needed # Values: toLower|toUpper #forceUserIdCase=toLower # User will be created only if a valid ID can be found , users will not be created with the source email address. # example: createUsers=true #createUsers=true # # When creating users, how should their ID's be formatted? # # values : # 'name' [NAME]@someplace.com (NOTE - collisions possible, needs more work to do NAME0, NAME1 upcounting etc. # 'email' [name@someplace.com] # 'alternate' (NOTE this delegates ID retrieval to custom retrievers, the 'default' will return full email address # # NOTE: if commented out, the default is to use the emailaddress [name@someplace.com] # example: createUsersIDFrom=email #createUsersIDFrom=email # # regexp list, setup this with regexps matching from: address domains, to enable 'limited' account creation # eg .*@(dolby\..*) #createUsersIDFromEmailDomainWhitelist=.*@dolby.co.uk,.*@dolby.com # # regexp list, setup email addresses that you will never create from, possibly per domain. # eg sales@atlassian.com #createUsersIDFromEmailBlacklist=sales@dolby.com # # If set, all pre-existing users found will be checked for membership of this group. You would do this, for instance with an LDAP # user repository where not everyone is a jira user / member of 'jira-users'. It won't however create the users. # #autoJoinGroup=jira-users # # Enable removal of empty whitespace liens introduced with some mail systems, eg Lotus # value given will cause at most 'n' empty lines to be removed before considering content for processing # eatEmptyBodyLinesMax=2 #-------------- # # Aliases # # You can use the following to provide shortcuts to defined directives, the 'alias.' is a required prefix, the text between the prefix and the = sign # defines the key that users would use, the value following the equals will equate to a key, and if another = sign is given, the next value will be used as a value for that key. # # Eg alias.fixed=wl.status=closed # Eg alias.bug=issueType=bug # This means a user can use @fixed only which will be interpreted as @wl.resolution=fixed # # (i) By _not_ shortening commands by default JEMH is less likely to confuse a custom field with a directive # alias.close=workflow=close alias.reopen=workflow=reopen alias.start=workflow=start #-------------- # Notifications # # # Notify users if 'createUsers' is true and they have just been created notifyUsers=false #What to do with the email after F A I L E D processing (can't handle) deleteEmail=false # # By default, JEMH will discern the correct event type, if you only comment, it will comment, if you update it will update, # but if you comment and update? well, JEMH counts up how many updated fields there are and the biggest one wins. # If however you want to always trigger a comment event irrespective of what event is normally generated.... # # Ensure Comment event is fired _if_ a comment is provided (ie, ignore other changes, eg files attached, directives applied) # #updatesWithCommentsAlwaysTriggerCommentEvent=true # If set true, will revert to using IssueUpdated events for all inbound change notifications. # In 0.9.2+ the correct event will be picked based on the information provided, falling back to the default IssueUpdated when multiple kinds of data are detected #useGenericEventType=true #---------------------- # CreateHandler options # # Only pull email for a given address, allows one mailbox to hold multiple email addresses (but requires one additional config file or parameter _per_ account) # NOTE: this is not a regexp, its a case insensitive string that gets compare to the To: address of mail # (i) as of 0.9.4, this field is multi value (comma separated) and can optionally be a regexp. #catchEmail=inbox@jira.myco.net, [a-z]*-jira@someplace.com #get the project key from the to: address projectAutoAssign=false #------- # If you arent using ldap for your Jira, comment out the lines: alternateIDLookupClassList and domainEquivalency # # If specified, will be used to lookup a userid from an email address, defult is using LDAP lookup # example: alternateIDLookupClassList=com.javahollic.jira.emh.engine.LDAPAlternateUserIDLookup #alternateIDLookupClassList=com.javahollic.jira.emh.engine.LDAPAlternateUserIDLookup # if email addresses are found, a CSV list of domains are considered 'the same' for ID resolution # example: domainEquivalency=dolby.co.uk:dolby.com #domainEquivalency=dolby.co.uk,dolby.com # List of packages to look for email processors, the default package contails full issue creation support, CVS support and atlassian default handlers. Only classes that are subclasses of AbstractFieldProcessor will be used. emailFieldProcessorPackageList=com.javahollic.jira.emh.processor # # If uncommented and set appropriately, will only allow a subset of available field processors to be executed (procPri>=lowerLimit and procPri<=upperLimit). This allows for example, the default atlassian format to be used by setting # upper and lower limits to MAXINT (2147483647) # # MailFormNg format priority: 1000 # AtPrefix format priority: 1100 # CSV format priority : 10000 # Atlassian 'default' processing priority: MAXINT (2147483647) #emailFieldProcessorPriorityLowerLimit=1000 #emailFieldProcessorPriorityUpperLimit=10000 # Notify users on creation of issues (this is SEPARATE to standard Jira issue notifications and is specific to issues created by EMAIL) # valid values: none|nonjira|jira|all #notifyUsersOnIssueCreation=all # By default, JEMH sourced notifications will use the configured Jira from: email address. # If either of the following are specified they will override the jira defaults # #customEmailFromAddress=jemh@myco.net #customEmailFromName=JEMH Mail Handler #---------------------- # CommentHandler options # When people reply to Jira mails that end up in the EMH mailserver, the quoted content of those mails can be stripped, or not (but this makes issues bigger and bigger and less readable) # example: stripQuotes=true stripQuotes=false # Optional, after quote stripping, allow the possibility to apply a regexp against the remaining text to filter out included content from a reply # NOTE: cant test this yet #IGNORE- not implemented - bodyRegexp=((.*)^----------------[-]*.*) #---------------------- # CC Handling # # # Enable to include all users successfully found via their given email address as watchers to the given issue # NOTE: Jira project security must allow this to happen, EMH will apply checks for watchers - must be able to MODIFY_WATCHERS by default in order to update watchers, # see 'strictJiraPermissions' to loosen this requirement # # example: addWatchersFromCC=true # ccHandling=toWatcher|toCustomField # (i) as of 0.9.4, either value or both values can be used (comma separated) #ccHandling=toWatcher # this value is only applicable if ccHandling is 'ccHandling=toCustomField', the CC users are converted to user types and added to target field, # the named CF needs to be able to handle multiple User object, like the Multi User Picker (MultiUserCF Type) #ccHandlingTargetCustomFieldName=Carbon Copy # If enabled will use allow shortcut names to be be given for workflow arguments, eg # for a workflow name of "Start Progress", if enabled, "start" would map accordingly. Naturally this only works # if there are _no_ duplicate first words. useFirstWordOnlyWorkflowNameMatch=true #-------------------------------- # Blacklist / Whitelist / Greylist # # Whitelist, comma separated list of addresses that will only be processed. # If set, no other domains/accounts will succeed (implying auto-blacklist of other domains), the blacklist can be used to further restrict within the whitelisted domains # If not set, all address will pass #example: whitelistSenders=(.*)@(.*)yourco.net,postmaster@yourco.com #whitelistSenders=(.*)@(.*)yourco.net,postmaster@yourco.com # Blacklist, comma separated list of addresses that will not be touched, and will be automatically forwarded # Blacklisted addresses will not be processed and will be forwarded on to the 'forward' address (ie probably an admin) # example: blacklistSenders=spammaker@yourco.net #blacklistSenders=mailer-daemon@googlemail.com,spammaker@yourco.net # stop people replying to the default email address that generates reports... #blacklistRecipients=noreply-jira@yourco.net # Defaults true. If set to false, causes blacklisted mails to not be forwarded, dropping _all_ of them. Possibly useful for high volume environments # example: silentlyDropBlacklistMatches=true #silentlyDropBlacklistMatches=true # Greylist, comma separated list of addresses that might get blocked depending on the subject # example: greylistSenders=postmaster@yourco.net #greylistSenders=postmaster@yourco.net,(.*)@yourco(.*) # used to identify a bounced email, can be mulitple CSV regexps # example: greylistSendersSubjectRegexps=Delivery to the following recipients failed,(.*)Delivery Status Notification [:(:]Failure[:):](.*),Out of Office Auto(.*) #greylistSendersSubjectRegexps=Delivery to the following recipients failed,(.*)Delivery Status Notification [:(:]Failure[:):](.*),Out of Office Auto(.*) # if specified, will be used to identify an email address that a bounce message relates to, # a single regexp should be enough for most orgs with 'one' postmaster address and response format. # NOTE: capture group '1' is expected to have user@domain , you get this by ensuring the first outer set of # brackets wraps that content, eg ((.*)@(.*)) # example: greylistRelatedUserBodyRegexp=[ ]*to:[ ]((.*)@(.*))$ #true=[ ]*to:[ ]((.*)@(.*))$ # If set true, will cause greylist matches, for example, due to disabled users that Jira cannot stop mail going to, from being silently eaten, rather # than being forwared to the sysadmin # exampe: silentlyDropGreylistSubjectMatches=true #silentlyDropGreylistSubjectMatches=true ## ## Additional Field Processors ## ## ## NAGIOS ## ## From email regexp #fp.nagios.fromEmailAddressRegexps=nagios@.* ## use standard atlassian date formats, eg 1w, 2d, 1w2d, etc. #fp.nagios.unresolvedIssueMatchTimeLimit=1d ## if a "fp.nagios.project" value is supplied, it will used, irrespective of 'defaultProject' or KEY@someplace.com related project identification mechanisms #fp.nagios.project=NAG #fp.nagios.components=unknown ## User to create the issue as #fp.nagios.reporter=admin ## Issue workflow, eg resolve/fixed ## see https://thepluginpeople.atlassian.net/wiki/display/JEMH/JEMH+Usage+Guide#JEMHUsageGuide-Workflow ## NOTE: single word workflow action matches (instead of 'Resolve Issue') requires uncommenting the #useFirstWordOnlyWorkflowNameMatch=true option #fp.nagios.resolvedWorkflowAction=resolve #fp.nagios.resolvedWorkflowResolution=fixed ## optionally override hintOgram delivery address #fp.nagios.overrideHintOgramEmailAddress=root@localhost ## ## Related phrases ## to make this usable these are the rules: ## 1. the _first_ phrase is the 'all good' phrase, which will be used to trigger issue closure ## 2. WHITESPACE is important, if the message doesnt starts with 'OK ', use 'OK ', not 'OK' which may match with OKAI printer for example... ## #fp.nagios.relatedPhrases.1=OK,WARNING,UNKNOWN,CRITICAL #fp.nagios.relatedPhrases.1.priority.WARNING=major #fp.nagios.relatedPhrases.1.priority.UNKNOWN=major #fp.nagios.relatedPhrases.1.priority.CRITICAL=critical #fp.nagios.relatedPhrases.2=UP,DOWN #fp.nagios.relatedPhrases.2.priority.DOWN=major ## most of the message will be the same, but must also check for variations of Notification Type #fp.nagios.notificationTypes=PROBLEM,RECOVERY ## If a service-OK message (index [0] match on relatedPhrase.x values) arrives but no related message could be found, ## perhaps due to time bounding through fp.nagios.unresolvedIssueMatchTimeLimit, if defined, this flag will cause such harmless messages to be auto-closed # #fp.nagios.autoCloseOrphanOkMessages=true ## ## XML (Servlet) ## ## As the servlet has no 'service' interface, the fp.xxxxx fields serve as specific overrides for that context from the rest of the content herein ## The path to get the servlet is for example: http://localhost:8080/plugins/servlet/JemhServlet # Enable the service at all, lack of field = disabled # (i) Under development #fp.servlet.enabled=true {code} The content of my emails are like this: {noformat} issueType: ECR reporter: asdf Serial Number: 123 Current Item (ECR): 123 Replacing Item (ECR): 123 Reason (ECR): Unknown Manufacturer Code Importance: low Description: asdf Unknown Manufacturer Code - asdf - 123 {noformat} The subject of the email is: "Unknown Manufacturer Code - asdf - 123" To: eric.salonen@ambientia.fi From: ECR@*****.com This is an extract from the log files, because it cant create issues from the emails: {code} 2010-08-19 17:18:51,218 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.EMHIssueHandler] ==== CUT ===== 2010-08-19 17:18:51,218 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.EMHIssueHandler] Jira Version = 2.0.4 (B uild:#413 - 29-04-2010) 2010-08-19 17:18:51,218 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.EMHIssueHandler] Unhandled MessagingExc eption occurred during processing, location=com.javahollic.jira.emh.service.EMHI ssueHandler.runProcessor(EMHIssueHandler.java:483). Likely this is a BUG: Unabl e to process message, body was null. from: [Ljavax.mail.internet.InternetAddress ;@9fa95c, subject: Drawing or Datasheet Missing - asdf - Product 123 2010-08-19 17:18:51,250 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.EMHIssueHandler] To: eric.salonen@tracke rs.fi From: ECR@****.com Cc: Bcc: --b1_f1825d19ce98bb6a3dc93ab4def1ad15 Content-Type: text/plain; charset = "iso-8859-1" Content-Transfer-Encoding: 8bit issueType: ECR reporter: asdf Serial Number: Product 123 Current Item (ECR): 123 Replacing Item (ECR): 123 Reason (ECR): Drawing or Datasheet Missing Importance: low Description: asdf Drawing or Datasheet Missing - asdf - Product 123 --b1_f1825d19ce98bb6a3dc93ab4def1ad15 Content-Type: text/html; charset = "iso-8859-1" Content-Transfer-Encoding: 8bit <p>issueType: ECR <br />reporter: asdf <br />Serial Number: Product 123 <br />Current Item (ECR): 123 <br />Replacing Item (ECR): 123 <br />Reason (ECR): Drawing or Datasheet Missing <br />Importance: low <br />Description: asdf <br />Drawing or Datasheet Missing - asdf - Product 123 <br /></p> --b1_f1825d19ce98bb6a3dc93ab4def1ad15-- 2010-08-19 17:18:51,250 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.EMHIssueHandler] ==== CUT ===== javax.mail.MessagingException: Unable to process message, body was null. from: [ Ljavax.mail.internet.InternetAddress;@9fa95c, subject: Drawing or Datasheet Miss ing - asdf - Product 123 at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssue Handler.java:483) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssu eHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage( CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailF etcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceCo ntainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:4 8) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.j ava:516) 2010-08-19 17:18:51,250 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.EMHIssueHandler] Rethrowing exception: U nable to process message, body was null. from: [Ljavax.mail.internet.InternetAdd ress;@9fa95c, subject: Drawing or Datasheet Missing - asdf - Product 123 javax.mail.MessagingException: Unable to process message, body was null. from: [ Ljavax.mail.internet.InternetAddress;@9fa95c, subject: Drawing or Datasheet Miss ing - asdf - Product 123 at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssue Handler.java:483) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssu eHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage( CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailF etcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceCo ntainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:4 8) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.j ava:516) 2010-08-19 17:18:51,250 JiraQuartzScheduler_Worker-1 ERROR ServiceRunner eric .salonen@ambientia.fi [jira.emh.service.CreateOrCommentHandler] Unandled Messagi ngException: Unable to process message, body was null. from: [Ljavax.mail.intern et.InternetAddress;@9fa95c, subject: Drawing or Datasheet Missing - asdf - Produ ct 123 javax.mail.MessagingException: Unable to process message, body was null. from: [ Ljavax.mail.internet.InternetAddress;@9fa95c, subject: Drawing or Datasheet Miss ing - asdf - Product 123 at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssue Handler.java:483) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssu eHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage( CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailF etcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceCo ntainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:4 8) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.j ava:516) javax.mail.MessagingException: Unable to process message, body was null. from: [ Ljavax.mail.internet.InternetAddress;@9fa95c, subject: Drawing or Datasheet Miss ing - asdf - Product 123 at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssue Handler.java:483) at com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssu eHandler.java:125) at com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage( CreateOrCommentHandler.java:67) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailF etcherService.java:189) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceCo ntainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:4 8) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.j ava:516) {code} Now what is going on? What am I missing? :)

    JIRA | 6 years ago | Eric Salonen
    javax.mail.MessagingException: Unable to process message, body was null. from: [ Ljavax.mail.internet.InternetAddress;@9fa95c, subject: Drawing or Datasheet Miss ing - asdf - Product 123
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    RE: [XNAT Discussion] gmail as smtp

    Google Groups | 4 years ago | Rick Herrick
    javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first. gb7sm63942610qab.12
  4. 0

    Problems in SendMail

    Oracle Community | 1 decade ago | 843830
    javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. javax.mail.MessagingException

      There are 51 comments already against the issue [] which exceeds the configured default: 50

      at com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor()
    2. com.javahollic.jira
      CreateOrCommentHandler.handleMessage
      1. com.javahollic.jira.emh.service.EMHIssueHandler.runProcessor(EMHIssueHandler.java:585)
      2. com.javahollic.jira.emh.service.EMHIssueHandler.handleMessage(EMHIssueHandler.java:127)
      3. com.javahollic.jira.emh.service.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:67)
      3 frames
    3. com.atlassian.jira
      ServiceRunner.execute
      1. com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:189)
      2. com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
      3. com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
      3 frames
    4. quartz
      SimpleThreadPool$WorkerThread.run
      1. org.quartz.core.JobRunShell.run(JobRunShell.java:191)
      2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
      2 frames