| Author |
Message
|
| gappodi |
 Posted: Wed Oct 08, 2014 6:51 am Post subject: Unable to send email using Email output node |
 |
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
I have created a very simple message flow that has a simple Fileinput Node connected to a Email Output node. I have configured the Email node with proper email node properties ( for e.g. SMTP server, To Address, etc. ). But when I run the flow I do not get the email as mentioned in the ToEmail address. I took a trace and found the following exception in it .
2014-10-08 19:54:34.961064 10336 RecoverableException BIP4459E: The EmailOutput node received a Java exception when it tried to create an e-mail and send it to the SMTP server. The stack trace from the exception is 'com.ibm.broker.emailnodes.EmailOutputNode : javax.mail.MessagingException: Could not connect to SMTP host: 9.55.53.81, port: 25;
nested exception is:
java.net.SocketException: Network is unreachable: connect
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1282)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at com.ibm.broker.emailnodes.EmailOutputNode.sendMail(EmailOutputNode.java:449)
at com.ibm.broker.emailnodes.EmailOutputNode.sendBasicEmail(EmailOutputNode.java:486)
at com.ibm.broker.emailnodes.EmailOutputNode.sendData(EmailOutputNode.java:358)
at com.ibm.broker.plugin.MbOutputTemplateNode.sendData(MbOutputTemplateNode.java:54)
Caused by: java.net.SocketException: Network is unreachable: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:358)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:219)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:201)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:180)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:616)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:230)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:189)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1250)
... 8 more
'.
Review the stack trace and correct any errors. Contact your IBM support center if you are unable to resolve the problem.
2014-10-08 19:54:34.961116 10336 RecoverableException BIP4678E: An e-mail error occurred during processing of a message. The e-mail error message is ''Could not connect to SMTP host: 9.55.53.81, port: 25
What is causing this to happen ? Am I missing anything here ?
Also I wanted to know that in order to use Email Output node, must I create a configurable service a s following ?
1. mqsicreateconfigurableservice MY_BROKER –c SMTP –o SMTP_MyAlias
2. mqsichangeproperties MY_BROKER –c SMTP –o SMTP_MyAlias –n serverName –v smtp.hursley.ibm.com:25
I believe these commands are only for overriding the values specified in the node. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Oct 08, 2014 7:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No, you don't need to use a configurable service.
Hopefully you wouldn't be talking to that SMTP server anyway.
The problem you're having is clear and specific. Your broker server can not reach the SMTP server, because the network is blocking it.
Talk to your network people. |
|
| Back to top |
|
|
| gappodi |
| Posted: Wed Oct 08, 2014 11:01 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
@mqjeff I checked with the network people but to avail no help. Is there any thing that I can check on my own in my machine where broker is running ?
Like any broker/non-broker specific service OR windows firewall related thing ?
However, I would like to point out one thing. If I write a plain JAVA code ( using java mailing API ), I am able to send an email. So that makes me feel that my broker is attempting to connect to the SMTP host but being stopped by something.
No clue at all  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 08, 2014 11:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Try a plain telnet from the broker machine, as the broker user, to the smtp server and port #.
The error is very explicit that the network is blocking the connection. |
|
| Back to top |
|
|
| gappodi |
| Posted: Wed Oct 08, 2014 11:28 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
I already tried it. I was able to connect. I was prompted a screen where I could type in. I issued a "quit" command to get out of that screen.
Jeff, anything else that I can do here ?
One more thing I would like to point out. I recently migrated to Windows 7 from XP. Issuing a 'telnet' command initially looked disabled and I had to enable it from the control panel settings.
So do you suspect something like that here occurring as well ? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 08, 2014 11:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The error text, as you have posted it, indicates a network issue.
The steps you have taken, as you have described them, do not indicate a network issue.
That means that either the broker is configured incorrectly, or the SMTP server doesn't like the Broker talking to it.
So, double-check and triple-check the node configuration and then delete and fully redeploy the solution and then restart the broker.
If the error still occurs, go talk to your network folks and the SMTP sever admin team. |
|
| Back to top |
|
|
| gappodi |
| Posted: Wed Oct 08, 2014 12:06 pm Post subject: |
|
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
Makes sense Jeff. I feel I should repeat this exercise. The only thing I think should not be happening is "the SMTP server doesn't like the broker talking to it"  Reason being, Pre migration from 7 to XP it always worked.
Anyway Jeff, I will do what you suggest and keep posting until it gets resolved  |
|
| Back to top |
|
|
| gappodi |
| Posted: Wed Oct 08, 2014 12:07 pm Post subject: |
|
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
Sorry for the typo..
From XP to 7 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 08, 2014 12:19 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It is possible that the Windows 7 firewall thingy is preventing the broker process from accessing the network. |
|
| Back to top |
|
|
| gappodi |
| Posted: Thu Oct 09, 2014 3:20 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2014
Posts: 76
|
The issue is resolved now. The problem was with the IBM symantec endpoint protection. Few days back I had received an update for the same because of which this problem got introduced. [However, I did not mention in my previous replies that I was able to send the email some time back but now I was not]. The network team person told me to stop the symantec and try. This time it worked.
Also I had to start the Windows firewall service as it was disabled by default.
Thanks !! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 09, 2014 5:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So the symantec thingy is replacing the windows firewall thingy. I imagine if you tried to use them both at the same time, it would all go wibbly-wobbly.
Regardless, you should discuss with your sysadmins about whether you can leave these disabled, or if you need to configure symantec to allow the broker DFEs to make outgoing network connections. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 09, 2014 7:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| it would all go wibbly-wobbly. |
And a little timey-wimey if I'm any judge.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
