| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQCONN takes 20 seconds on client |
« View previous topic :: View next topic » |
| Author |
Message
|
| PaulClarke |
 Posted: Fri Oct 20, 2017 12:44 pm Post subject: |
 |
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It is surprising that PING primary and Telnet primary shows no delay but MQ sees one. However, at least you know the source (if not the cause) of the problem now.
Good luck.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Sun Oct 22, 2017 4:29 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| MABeatty1978 wrote: |
| Now to figure out why it won't resolve.... |
MQ is calling OS network function getaddrinfo(). Talk to your network or OS support folk.
_________________
Glenn |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Oct 23, 2017 12:25 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Do you use the BlockIP2 exit? That can also have a lot of DNS resolution depending on the rules coded.
Essentially you need to tune your DNS name lookup. Possibly your DNS server has a problem or the local DNS cache is not running.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 23, 2017 6:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
Do you use the BlockIP2 exit? That can also have a lot of DNS resolution depending on the rules coded.
Essentially you need to tune your DNS name lookup. Possibly your DNS server has a problem or the local DNS cache is not running. |
Please make also sure that reverse DNS lookup has been turned off in the queue manager.
Anyways as for the solution, it might have been better to add the host address to the /etc/hosts table. You could then remove it after your dns problems have been solved without touching mq...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Oct 23, 2017 6:59 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
He said it was in the hosts file
| Quote: |
$MQSERVER = SYSTEM.CLNT.SVRCONN/TCP/primary(2414)
from /etc/hosts
10.50.120.201 primary.company.com primary
I've confirmed the server is 10.50.120.201 |
So, in theory, it would resolve it. However I would recommend fully qualifying all DNS names - to avoid any risk of an unsuitable default domain name being used.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
