com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11

Pentaho BI Platform Tracking | Philip Panelli | 4 years ago
  1. 0

    Y2xpY2sgb24gdGhlIGxpbmsgcHJvdmlkZWQgYmVsb3cNCjxicj48YSBocmVmPSJodHRwOi8vd3d3 Mi5wcmludGFibGUuY29tL2xvZ2luLmFzcCI+DQoJaHR0cDovL3d3dzIucHJpbnRhYmxlLmNvbS9s b2dpbi5hc3ANCjwvYT4= ) A11 OK FETCH completed. A12 FETCH 1 (BODY.PEEK[HEADER.FIELDS (Mail Header(Name))]) A12 BAD Command Argument Error. 11 IMAP DEBUG: IMAPProtocol noop A13 NOOP A13 OK NOOP completed. ERROR 28-11 16:03:28,652 - Email messages input - Unexpected error ERROR 28-11 16:03:28,653 - Email messages input - org.pentaho.di.core.exception.KettleException: Error adding values to row! A12 BAD Command Argument Error. 11 at org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:326) at org.pentaho.di.trans.steps.mailinput.MailInput.processRow(MailInput.java:69) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50) at java.lang.Thread.run(Thread.java:662) Caused by: javax.mail.MessagingException: A12 BAD Command Argument Error. 11; nested exception is: com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11 at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:737) at org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:306) ... 3 more Caused by: com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11 at com.sun.mail.iap.Protocol.handleResult(Protocol.java:343) at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:1055) at com.sun.mail.imap.protocol.IMAPProtocol.peekBody(IMAPProtocol.java:1025) at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:722) ... 4 more DEBUG 28-11 16:03:28,653 - Email messages input - Closing connection ... DEBUG 28-11 16:03:28,653 - dummy - Signaling 'output done' to 0 output rowsets. DEBUG 28-11 16:03:28,653 - Email messages input - Closing folder [INBOX] ... A14 CLOSE INFO 28-11 16:03:28,654 - dummy - Finished processing (I=0, O=0, R=0, W=0, U=0, E=0) A14 OK CLOSE completed. DEBUG: added an Authenticated connection -- size: 1 DEBUG 28-11 16:03:28,655 - Email messages input - Folder [] was closed. A15 LOGOUT * BYE Microsoft Exchange Server 2010 IMAP4 server signing off. A15 OK LOGOUT completed. DEBUG: IMAPStore connection dead DEBUG: IMAPStore cleanup, force false DEBUG: IMAPStore cleanup done DEBUG 28-11 16:03:28,656 - Email messages input - Connection closed. INFO 28-11 16:03:28,656 - Email messages input - Finished processing (I=0, O=0, R=0, W=0, U=0, E=1) INFO 28-11 16:03:28,656 - /PrintabletestEmailScrape - /PrintabletestEmailScrape INFO 28-11 16:03:28,656 - /PrintabletestEmailScrape - /PrintabletestEmailScrape DEBUG 28-11 16:03:28,656 - /PrintabletestEmailScrape - Looking at step: Email messages input DEBUG 28-11 16:03:28,678 - /PrintabletestEmailScrape - Looking at step: dummy

    Pentaho BI Platform Tracking | 4 years ago | Philip Panelli
    com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11
  2. 0

    Y2xpY2sgb24gdGhlIGxpbmsgcHJvdmlkZWQgYmVsb3cNCjxicj48YSBocmVmPSJodHRwOi8vd3d3 Mi5wcmludGFibGUuY29tL2xvZ2luLmFzcCI+DQoJaHR0cDovL3d3dzIucHJpbnRhYmxlLmNvbS9s b2dpbi5hc3ANCjwvYT4= ) A11 OK FETCH completed. A12 FETCH 1 (BODY.PEEK[HEADER.FIELDS (Mail Header(Name))]) A12 BAD Command Argument Error. 11 IMAP DEBUG: IMAPProtocol noop A13 NOOP A13 OK NOOP completed. ERROR 28-11 16:03:28,652 - Email messages input - Unexpected error ERROR 28-11 16:03:28,653 - Email messages input - org.pentaho.di.core.exception.KettleException: Error adding values to row! A12 BAD Command Argument Error. 11 at org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:326) at org.pentaho.di.trans.steps.mailinput.MailInput.processRow(MailInput.java:69) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50) at java.lang.Thread.run(Thread.java:662) Caused by: javax.mail.MessagingException: A12 BAD Command Argument Error. 11; nested exception is: com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11 at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:737) at org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:306) ... 3 more Caused by: com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11 at com.sun.mail.iap.Protocol.handleResult(Protocol.java:343) at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:1055) at com.sun.mail.imap.protocol.IMAPProtocol.peekBody(IMAPProtocol.java:1025) at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:722) ... 4 more DEBUG 28-11 16:03:28,653 - Email messages input - Closing connection ... DEBUG 28-11 16:03:28,653 - dummy - Signaling 'output done' to 0 output rowsets. DEBUG 28-11 16:03:28,653 - Email messages input - Closing folder [INBOX] ... A14 CLOSE INFO 28-11 16:03:28,654 - dummy - Finished processing (I=0, O=0, R=0, W=0, U=0, E=0) A14 OK CLOSE completed. DEBUG: added an Authenticated connection -- size: 1 DEBUG 28-11 16:03:28,655 - Email messages input - Folder [] was closed. A15 LOGOUT * BYE Microsoft Exchange Server 2010 IMAP4 server signing off. A15 OK LOGOUT completed. DEBUG: IMAPStore connection dead DEBUG: IMAPStore cleanup, force false DEBUG: IMAPStore cleanup done DEBUG 28-11 16:03:28,656 - Email messages input - Connection closed. INFO 28-11 16:03:28,656 - Email messages input - Finished processing (I=0, O=0, R=0, W=0, U=0, E=1) INFO 28-11 16:03:28,656 - /PrintabletestEmailScrape - /PrintabletestEmailScrape INFO 28-11 16:03:28,656 - /PrintabletestEmailScrape - /PrintabletestEmailScrape DEBUG 28-11 16:03:28,656 - /PrintabletestEmailScrape - Looking at step: Email messages input DEBUG 28-11 16:03:28,678 - /PrintabletestEmailScrape - Looking at step: dummy

    Pentaho BI Platform Tracking | 4 years ago | Philip Panelli
    com.sun.mail.iap.BadCommandException: A12 BAD Command Argument Error. 11
  3. 0

    - Use attached transformation to reproduce. - Make sure that the email configuration is complete and test the connection. I removed my credentials. - Make sure that the "Mail Header(Name)" is in the field list. See attached screen shot. - Perform a preview on 10 rows - it will take a lot longer with the default of 1000. This exception occurs- I removed redundant logging info for readability: Unexpected error : org.pentaho.di.core.exception.KettleException: Error adding values to row! A9 BAD Command Argument Error. 11 at org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:314) at org.pentaho.di.trans.steps.mailinput.MailInput.processRow(MailInput.java:63) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:40) at java.lang.Thread.run(Thread.java:619) : Caused by: javax.mail.MessagingException: A9 BAD Command Argument Error. 11; nested exception is: : com.sun.mail.iap.BadCommandException: A9 BAD Command Argument Error. 11 : at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:707) : at org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:294) : ... 3 more : Caused by: com.sun.mail.iap.BadCommandException: A9 BAD Command Argument Error. 11 : at com.sun.mail.iap.Protocol.handleResult(Protocol.java:296) : at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:1005) : at com.sun.mail.imap.protocol.IMAPProtocol.peekBody(IMAPProtocol.java:975) : at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:692) : ... 4 more

    Pentaho BI Platform Tracking | 5 years ago | Sean Flatley
    com.sun.mail.iap.BadCommandException: A9 BAD Command Argument Error. 11
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    We're trying to create/comment issues from e-mail. We set up an Exchange 2007 account and mailbox, defined the IMAP mail server, defined create issue/comment service for one of our projects. However, when we send an e-mail to the mailbox, we got the following error: {color:red} com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11{color} Our Jira version: Enterprise Edition, Version: 3.13.2-#335 Our Exchange Server version: Exchange 2007 Update Rollup 5 Here are the JIRA log and the captured wireshark messages: *Jira log:* 2009-02-24 16:24:31,628 JiraQuartzScheduler_Worker-3 ERROR [service.services.mail.MailFetcherService] Create Issue/Comment Service - debitcards[10010]: {color:red} Exception: A4 BAD Command Argument Error. 11;{color} nested exception is: com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11 javax.mail.MessagingException: A4 BAD Command Argument Error. 11; nested exception is: com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11 at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:624) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:175) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:56) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:61) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) *Wireshark messages:* * OK Microsoft Exchange Server 2007 IMAP4 service ready A0 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+ A0 OK CAPABILITY completed. A1 AUTHENTICATE PLAIN A1 OK AUTHENTICATE completed. A2 LIST "" INBOX * LIST (\Marked \HasNoChildren) "/" INBOX A2 OK LIST completed. A3 SELECT INBOX * 1 EXISTS * 0 RECENT * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent) * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags * OK [UIDVALIDITY 895] UIDVALIDITY value * OK [UIDNEXT 8] The next unique identifier value A3 OK [READ-WRITE] SELECT completed. A4 FETCH 1 (BODY.PEEK[HEADER.FIELDS (Message-ID)]) {color:red} A4 BAD Command Argument Error. 11{color} A5 NOOP A5 OK NOOP completed. A6 CLOSE A6 OK CLOSE completed. A7 LOGOUT * BYE Microsoft Exchange Server 2007 IMAP4 server signing off. A7 OK LOGOUT completed. Is it a bug? Or is there a way to overcome this error? Thanks in advance. Serkan.

    Atlassian JIRA | 8 years ago | Serkan Soykan
    com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11
  6. 0

    Jira fails to create or comment on issues when using a Exchange Server 2007 with turkish locale. The logs will present an exception like: {noformat} JiraQuartzScheduler_Worker-3 ERROR [service.services.mail.MailFetcherService] Create Issue/Comment Service - ...[...]: Exception: A4 BAD Command Argument Error. 11; nested exception is: com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11 javax.mail.MessagingException: A4 BAD Command Argument Error. 11; nested exception is: com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11 at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:624) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:175) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:56) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:61) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) {noformat} The communication with exchange looks like: {noformat} * OK Microsoft Exchange Server 2007 IMAP4 service ready ... A4 FETCH 1 (BODY.PEEK[HEADER.FIELDS (Message-ID)]) A4 BAD Command Argument Error. 11 A5 NOOP A5 OK NOOP completed. A6 CLOSE A6 OK CLOSE completed. A7 LOGOUT * BYE Microsoft Exchange Server 2007 IMAP4 server signing off. A7 OK LOGOUT completed. {noformat} This seems to be due to the problems converting the 'i' character in Turkish from upper case to lower case ([explanation|http://www.i18nguy.com/unicode/turkish-i18n.html]). For instance, the following sequence fails: {noformat} -> 5 FETCH 1:* (BODY.PEEK[HEADER.FIELDS (Message-Id)]) <- 5 BAD Command Argument Error. 11 {noformat} But with a non capital 'i' is succeeds: {noformat} -> 6 FETCH 1:* (BODY.PEEK[HEADER.FiELDS (Message-id)]) <- * ... <- 6 OK FETCH completed. {noformat}

    Atlassian JIRA | 8 years ago | Diego Alonso [Atlassian]
    com.sun.mail.iap.BadCommandException: A4 BAD Command Argument Error. 11

    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. com.sun.mail.iap.BadCommandException

      A12 BAD Command Argument Error. 11

      at com.sun.mail.iap.Protocol.handleResult()
    2. JavaMail API (compat)
      IMAPMessage.getHeader
      1. com.sun.mail.iap.Protocol.handleResult(Protocol.java:343)
      2. com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:1055)
      3. com.sun.mail.imap.protocol.IMAPProtocol.peekBody(IMAPProtocol.java:1025)
      4. com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:722)
      5. com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:737)
      5 frames
    3. org.pentaho.di
      MailInput.getOneRow
      1. org.pentaho.di.trans.steps.mailinput.MailInput.getOneRow(MailInput.java:306)
      1 frame