| Author |
Message
|
| coolcurls |
 Posted: Thu Feb 23, 2012 4:18 pm Post subject: Email Input Node WMB 7.0.0.3 |
 |
|
Novice
Joined: 03 Aug 2007
Posts: 15
|
Hello,
I am trying to receive emails using EmailInputNode. I have configured the input node with server and user credentials.
I deployed the flow. It fails at the Input node while reading the email from the inbox. I am getting the following error in the user log.
I have changed the hostname, broker and EG name in the following log
Any help is appreciated.
Thanks!
Feb 23 18:52:34 hostname user:err|error WebSphere Broker v7003[9896026]: (BROKER1.EG_TT)[13378]BIP2628E: Exception condition detected on input node 'MF_TestEmail.Email Input'. : BROKER1.3b8ddce1-3001-0000-0080-d82fd7446e9e: /build/S700_P/src/DataFlowEngine/TemplateNodes/ImbCallableTemplateNode.cpp: 1202: ImbCallableTemplateNode::processMessage: ComIbmEmailInputNode: MF_TestEmail#FCMComposite_1_1
Feb 23 18:52:34 hostname user:info WebSphere Broker v7003[9896026]: (BROKER1.EG_TT)[13378]BIP4973E: EmailInput node 'Email Input' in message flow 'MF_TestEmail' has received an email with content type 'multipart/mixed; boundary="----_=_NextPart_001_01CC5C3A.953EED7D"' and internal type '### javax.mail.internet.MimeMultipart multipart', which the EmailInput node is not able to process. : BROKER1.3b8ddce1-3001-0000-0080-d82fd7446e9e: MbErrorHandler.java: 104: validateData: : |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Feb 24, 2012 2:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
That says it doesn't like the particular email it's trying to process.
It's not clear why - if the email is really just a multi-part email, it should be easily understood.
I'd dump out the contents of the email in a flatfile using something other than Broker and then stare at it for a while. Then I'd take a service trace of broker trying process the email. Then I'd submit that in a PMR. |
|
| Back to top |
|
|
| coolcurls |
| Posted: Fri Feb 24, 2012 10:06 am Post subject: |
|
|
Novice
Joined: 03 Aug 2007
Posts: 15
|
The message fails on the Email Input Node itself. It does not come to any of the output terminals on the node n debug mode. I wanted to check and see if anyone has had this issue before.
I have opened a service request with IBM.
mqjeff,
Thanks for your help. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Feb 24, 2012 10:19 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Feb 24, 2012 10:20 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
In cases like this, using UserTrace may well give you some more data that you would get with the Debugger.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| cyn |
| Posted: Fri Apr 13, 2012 4:21 am Post subject: |
|
|
Newbie
Joined: 13 Apr 2012
Posts: 5
|
I have the same problem.
I'm using WMB 7.0.0.3 IBM AIX
When I receive e-mail with attachment using EmailInput node, i get exception in this node:
| Quote: |
Text:CHARACTER:Unknown content type: class javax.mail.internet.MimeMultipart
Insert
Type:INTEGER:5
Text:CHARACTER:Email Input
Insert
Type:INTEGER:5
Text:CHARACTER:mail.adapter
Insert
Type:INTEGER:5
Text:CHARACTER:multipart/mixed; boundary="=_mixed 0030B2C2C62579DF_="
Insert
Type:INTEGER:5
Text:CHARACTER:### javax.mail.internet.MimeMultipart multipart
|
Exception occurs only when email has an attachment, simple text emails are processing properly.
I tried to run the same flow and receive the same e-mail on WMB v8 PC-WIN and there was no exception.
Do you think it's java/operating system problem?
@coolcurls
Have you solved your issue? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 13, 2012 4:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cyn wrote: |
| Exception occurs only when email has an attachment, simple text emails are processing properly. |
What kind of attachment?
| cyn wrote: |
I tried to run the same flow and receive the same e-mail on WMB v8 PC-WIN and there was no exception.
Do you think it's java/operating system problem? |
I'd be more inclined to think that AIX & Windows are using 2 different code pages.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cyn |
| Posted: Fri Apr 13, 2012 4:54 am Post subject: |
|
|
Newbie
Joined: 13 Apr 2012
Posts: 5
|
| Vitor wrote: |
What kind of attachment? |
I've tried zip and txt file. I think attachment type does not matter.
| Vitor wrote: |
I'd be more inclined to think that AIX & Windows are using 2 different code pages. |
But in that case simple text e-mail shouldn't also throw an exception in EmalInput node? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 13, 2012 5:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cyn wrote: |
| But in that case simple text e-mail shouldn't also throw an exception in EmalInput node? |
Not if all the characters in the simple text (which being simple are all common) are idenitically mapped in both code pages; i.e alphanumerics & common punctuation.
If the attachment contains more exotic charactes (which the zip certainly will because it's a binary) that could be a issue. A problem with txt file attachments sort of crimps my wonderful theory however but...
...you're using WMBv7 on AIX & WMBv8 on Windows! It's highly possible the node got changed / fixed / enhanced between versions & this is why it working. Perhaps it's more tollerant / smarter with MIME content settings?
That's the next thing I'd look at in your position.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cyn |
| Posted: Fri Apr 13, 2012 5:24 am Post subject: |
|
|
Newbie
Joined: 13 Apr 2012
Posts: 5
|
| Vitor wrote: |
| It's highly possible the node got changed / fixed / enhanced between versions & this is why it working. |
This is the simplest explanation,so I want to test this flow on WMB 7.0.0.3 on Windows.
But if node got fixed in v8 there should be also fix pack for v7, unless the error was fixed unconsciously  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 13, 2012 5:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cyn wrote: |
| But if node got fixed in v8 there should be also fix pack for v7, unless the error was fixed unconsciously |
Not the first time.
It's also highly possible that v8 handles MIME content setting differently or has been enhanced to handle content differently / better.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 13, 2012 5:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
My money is on a bad email created by Microsoft Outlook that requires custom MIME parts.
Again, to debug the email input node, use the following steps - export the email as a text document (inlcuding all of the mime parts) from something other than Broker
- take a service trace of broker trying to receive the email
|
|
| Back to top |
|
|
| cyn |
| Posted: Sun Apr 15, 2012 10:57 pm Post subject: |
|
|
Newbie
Joined: 13 Apr 2012
Posts: 5
|
This issue appears also in WMB 7.0.0.3 on Windows, but I realized that broker throws exception only when email has attachment and is sending as text/html.
The same email with attachment but sent as text/plain is processed properly.
Text/html email without attachment also is correct.
For WMB v8 all kind of email are correct. |
|
| Back to top |
|
|
| cyn |
| Posted: Mon Apr 16, 2012 5:43 am Post subject: |
|
|
Newbie
Joined: 13 Apr 2012
Posts: 5
|
|
| Back to top |
|
|
|
|
