| Author |
Message
|
| sree |
 Posted: Mon Feb 16, 2004 2:13 pm Post subject: MQ Connection problem with TCP/IP error |
 |
|
Novice
Joined: 12 Mar 2003
Posts: 19
|
Hello All,
I have MQ 5.3.0.5 installed on Windows/2000 box. When I try to establish a connection to the Queue Manager with MQSI, Configuration Manager ( Websphere Business Intigration Message Broker 5.0.0.1), i am getting the following error message in the error log. Queue manager and the configuration manager are on the same box.
-------------------------------------------------------
02/16/2004 16:53:11
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record
these values and tell the systems administrator.
----- amqccita.c : 1409 -------------------------------------------------------
Some one could help me to resolve this problem please?
Thank you.
_________________
Thank you.
sree |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Feb 16, 2004 2:36 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Feb 16, 2004 2:43 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Yes, Funnily enough I started seeing this recently. I think I have narrowed down a piece of software I installed which is causing the problem.
Can you, on your server, get process explorer (www.sysinternals.com), run it, select the listener (runmqlsr) in it, Change lower pane view to DLLS, and View->Select Columns->Dll tick the box 'Path'.
Then pm me the list of dlls please (file -> save as). I'd appreciate the same from anyone who hits the 10038 error without MQNOREMPOOL set.
Setting MQNOREMPOOL in the system portion of the env vars and rebooting will work around the problem for now. I'd like to identify the cause and start getting it addressed! |
|
| Back to top |
|
|
| sree |
| Posted: Fri Feb 20, 2004 5:32 am Post subject: |
|
|
Novice
Joined: 12 Mar 2003
Posts: 19
|
Vennela & Jason,
When I set the environment varible, MQNOREMPOOL=1, it worked and i could able to connect to Configmgr.
Thank you so much for you help.
_________________
Thank you.
sree |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Feb 20, 2004 6:42 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Great news. Can you please get me the information requested above though as I am trying to correlate these problems (dll list of the listener process). You can take the doc with the env var set, its not a problem, and it wont harm a running system either. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Jan 05, 2007 6:05 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Jason,
was this ever fixed somewhere?
I ran into this problem on my new laptop T60p dual core and MQ V6.0.2.0
MQNOREMPOOL=1 fixed the problem without rebooting, just stop start of the queuemanagers...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 05, 2007 6:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've never had that problem on a reasonably dentical laptop.
Starting and stopping the queue manager might not have actually caused MQNOREMPOOL=1 to take effect...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Jan 05, 2007 6:32 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
well...
removing MQNOREMPOOL=1 stopping and starting re-introduced the problem...
why would you think it may not have caused the effect?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 05, 2007 6:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Because Windows environment variables do not necessarily take effect when people think they do. And because MQ on windows runs through DCOM and thus shell changes are complicated.
But if removing it reintroduced the problem, then I guess it did take effect.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
