| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IIB Flow intermittent issues |
« View previous topic :: View next topic » |
| Author |
Message
|
| vmanel |
 Posted: Wed May 15, 2019 6:47 am Post subject: IIB Flow intermittent issues |
 |
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
Hi,
We have a error handling framework for IIB 10 flows, where in we first log the error to a file in server using log4j and then constuct email in esql and send the email using email node.
We are facing intermittent issues with these, sometimes the log4j Java procedure which logs the error is successfully called, but the errors are not getting logged, and for sending email we get a Java based Timeout exception with smtp server. But we are successfully able to ping to smtp server from IIB server.
These are intermittent issues which automatically gets resolved after sometime. For smtp server, if we consider it as network issue, then why logs are not getting logged?
Since both are related to Java, is it something to do with JVM of the excution groups? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 15, 2019 7:02 am Post subject: Re: IIB Flow intermittent issues |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
| We have a error handling framework for IIB 10 flows, where in we first log the error to a file in server using log4j and then constuct email in esql and send the email using email node. |
Is this log4j from the IAM3 support pac, or is it one that works reliably? 
IAM3 is Cat 2 (supplied in good faith as-is) and we had the same problems with it. Often when multiple instances were trying to write to the log file, or the JVM heap was short, when there was a "y" in the day or when you really needed the message in Prod (worked great in test). We gave up and wrote our own using java.util.logging (which I'm assured by the Java people is much superior) which we tested brutally.
As to the Email nodes, again we didn't have the best luck. We found that both the SMTP and POP3 servers would periodically "hang up" on the nodes for inexplicable reasons; even though the node appeared to have a connection, the EmailOutput node would timeout trying to send a message and the EmailInput node would consistently get "no messages available" even though there were clearly messages in the inbox. I suspect it's because both SMTP and POP3 are provided by an Exchange server and bizarre quirks come free with all MSoft products.
Again we gave up and wrote a Java protocol gateway that exposes a URL for outbound emails (HTTPRequest node) and then does the SMTP stuff. It also polls the POP3 and sends emails as REST calls (HTTPInput node). We also discourage the use of email from or to IIB (even for error notification) because it's a PITA to monitor delivery SLAs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vmanel |
| Posted: Wed May 15, 2019 7:33 am Post subject: Re: IIB Flow intermittent issues |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| Vitor wrote: |
| Is this log4j from the IAM3 support pac, or is it one that works reliably? |
It is from IAM3 support pac. Would altering JVM parameters be of any help?
| Vitor wrote: |
| As to the Email nodes, again we didn't have the best luck. We found that both the SMTP and POP3 servers would periodically "hang up" on the nodes for inexplicable reasons; even though the node appeared to have a connection, the EmailOutput node would timeout trying to send a message and the EmailInput node would consistently get "no messages available" even though there were clearly messages in the inbox. I suspect it's because both SMTP and POP3 are provided by an Exchange server and bizarre quirks come free with all MSoft products. |
Any temporary fix for this issue? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 15, 2019 7:47 am Post subject: Re: IIB Flow intermittent issues |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
| It is from IAM3 support pac. |
Which version? Maybe the most recent one is more reliable..... 
| vmanel wrote: |
| Would altering JVM parameters be of any help? |
I can't see how that's going to help with problems like multiple instances getting deadlocked writing to the log, or the code just not bothering to write the error, but go right ahead and randomly change some stuff. If you hit a magic combination of JVM parameters that make log4j work reliably and doesn't screw up all the JCNs, please post it here.
| vmanel wrote: |
| Vitor wrote: |
| As to the Email nodes, again we didn't have the best luck. We found that both the SMTP and POP3 servers would periodically "hang up" on the nodes for inexplicable reasons; even though the node appeared to have a connection, the EmailOutput node would timeout trying to send a message and the EmailInput node would consistently get "no messages available" even though there were clearly messages in the inbox. I suspect it's because both SMTP and POP3 are provided by an Exchange server and bizarre quirks come free with all MSoft products. |
Any temporary fix for this issue? |
We never found one. Because the problem seemed to be at the Exchange side, and there's never anything wrong with the Exchange server (according to our Exchange server team). Specifically:
| Quote: |
It must be something with the email client your IIB is using. You need to speak to the vendor and get them to build a headless Outlook into it.
But we run on Linux.
Well run it on Windows then.
But you support other Linux products that send emails.
No we don't. <Site name> just happens to have other Linux products that send emails; we don't support them. Maybe IBM should ask the other vendors how to do it right.
|
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mpong |
| Posted: Wed May 15, 2019 11:56 am Post subject: |
|
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
| Regarding SMTP server timeout, there can be many reason. Do you have a SMTP provisioned for your integration solution or is it a SMTP server commonly used across in the enterprise. There can be slowness/Network issue at SMTP. Security is a main concern here, in case of sending out attachements over email acorss different network. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
