| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Really confused problem. RC 2059 |
« View previous topic :: View next topic » |
| Author |
Message
|
| protossqyj |
 Posted: Mon Mar 31, 2008 2:06 am Post subject: Really confused problem. RC 2059 |
 |
|
Newbie
Joined: 02 Dec 2007
Posts: 2
|
These days I encountered MQ problem which confused me a lot.
I have a MFC application which developed by C++ to send message to Remote Queue. It is working well for several months. But these days, it has a problem that I can not send any message. The reason code is 2059 which is very common here.
Then I made a test that created simple local queue on two PC with default setting which were same with each other. The strange thing is that on computer B, I could connect with the QUEUE for many times. But on computer A, I could only connect once. That means I can't close the MFC application because it can only connect for the first time. Otherwise, I will get error 2059. Then I have to restart the service on computer A, it works again but only for the first time.
It sounds strange but I am confused by this problem and can not find any solution in this forum.
Did anyone encounter such problem before? I am looking forward to your reply.
Thank you very much indeed! |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon Mar 31, 2008 2:14 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
OS Dependent.... 
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 31, 2008 2:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gaya3 wrote: |
| OS Dependent.... |
Sounds like Windoze to me....
....but as the poster's not given any details we're all just guessing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Mar 31, 2008 4:55 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I thought the M in MFC stood for Microsoft..... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 31, 2008 5:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bower5932 wrote: |
| I thought the M in MFC stood for Microsoft..... |
I saw this as a key clue.... 
There's no evidence of which of the various breeds is in use though, and this could easily be relevant.
If I had to theorise (and theorise something other than it's a useless OS) I'd say that the TCP/IP stack is getting stuffed up after the 1st close, causing the 2059.
Possible solutions include using a better OS. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| protossqyj |
| Posted: Mon Mar 31, 2008 7:16 pm Post subject: |
|
|
Newbie
Joined: 02 Dec 2007
Posts: 2
|
I am very grateful to your replies.
I also guess the OS windows server 2003 SP2, but the two computers have same OS, why one can not work properly.
The MFC application is very simple, copied from tutorial, just to connect and send message, like this:
mgr = new ImqQueueManager();
mgr->setName( m_strQM );
mgr->connect();
It has been working well for a long time.
Also, sample program amqsput.exe doesn't work because of 2059.
And what do you mean by TCP/IP stack is stuffed up, how can I check this?
Anyway, thank you very much. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 12:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| protossqyj wrote: |
| I also guess the OS windows server 2003 SP2, but the two computers have same OS, why one can not work properly. |
Because no 2 Windows machines are ever identical!!! 
(You may detect a hint of bias through this, and my other, posts....)
| protossqyj wrote: |
It has been working well for a long time.
Also, sample program amqsput.exe doesn't work because of 2059. |
A 2059 is seldom an application problem. I think you mean amqsputc doesn't work either, which rules out a problem with your application. If you really mean amqsput, that's something else again.
| protossqyj wrote: |
| And what do you mean by TCP/IP stack is stuffed up, how can I check this? |
A 2059 is a failure to connect to the queue manager. If the application has been working before, and there's been no network or firewall changes, then something is preventing connection. I know from experience odd & inexplicable things happen on Windows boxes, including a strange failure to resolve names & IP addresses. There's an item on the Microsoft KB about this, which includes bits of the registry to delete.
I offer the obvious caution about editing the registry on a Windoze box without proper backup, recovery and roll back strategies.
A simple check is to telnet to the target queue manager, quoting the port MQ is using rather than the standard telnet.
_________________
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
|
|
|
|
