| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Frequent socket timeout exception due to DNS IP change |
« View previous topic :: View next topic » |
| Author |
Message
|
| dileep1985 |
 Posted: Tue Mar 13, 2018 6:37 am Post subject: Frequent socket timeout exception due to DNS IP change |
 |
|
Novice
Joined: 15 Jul 2017
Posts: 15
|
Hi All,
Issue description : We have an issue where by we are getting continous socket timeout exception for an websevice invocation to an external service provide
Error:
Socket error detected whilst invoking Web service located at host ddo.xxxx.com, port 443, path /dddds/find?key=355617f7-d2fa-46ba-bc89-113d7cf637e2
The issue will solve whenever we restart the EG and will again occur after some time. Again we have to restart the EG. Upon investigation and further analsysis, we have found that this may occurs due to frequent DNS caching.
When using secure HTTP connections, you change a DNS host's destination but the broker is using a cached DNS host definition
https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au16534_.htm#au16534_3
We need to know how can resolve the issue. Disabling the DNS caching will cause preformance improvement issue since broker needs to go for WS call look up everytime.
Client is just wondering why IIB product itself is not correcting the cache. The DNS is very common across all projects and provider can change ips at any time. Everytime restart is not an option and can IIB do something like this
if connection or socket error
restcache()
callagain()
Are we missing anything here. Any config changes required |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Mar 13, 2018 7:13 am Post subject: Re: Frequent socket timeout exception due to DNS IP change |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dileep1985 wrote: |
| Client is just wondering why IIB product itself is not correcting the cache. |
The question comes how does IIB know the IP address has changed rather there being an intermittent network error. The whole point of having a cached IP is to streamline connectivity, and refreshing the cache every time there's a problem defeats the object.
The problem is not specific to IIB; you'll find WAS, Apache and other products using DNS caching in the same way. If these products do not exhibit the same symptoms then you can try setting the cache settings in IIB to match those in WAS.
| dileep1985 wrote: |
| The DNS is very common across all projects and provider can change ips at any time. |
A web service provider, especially an external one that's providing a service to multiple clients, shouldn't be changing IP addresses often enough to cause a problem, and certainly not during working hours. That speaks to a problem with whatever you're using for a proxy.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
