| Author |
Message
|
| rgn |
 Posted: Tue May 15, 2012 9:44 am Post subject: |
 |
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
So if I was running this from my pc before using qMgr v6 and v6 client and had no issues, then changed to client version 7, what would I tell my network guys...?
It worked before...I changed my dll and now it doesn't work...? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue May 15, 2012 9:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Is the v7 queue manager in the exact same network location as the v6 qmgr was? |
|
| Back to top |
|
|
| rgn |
| Posted: Tue May 15, 2012 9:50 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
K...I think there is some confusion...
Previous setup:
v6 qmgr
v6 client
Current setup:
v6 qmgr
v7 client |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 9:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rgn wrote: |
| what would I tell my network guys...? |
That it's always a network problem, whatever "it" happens to be in that context until they can prove otherwise?
I echo the comment of my most worthy associate; is the v7 queue manager on exact;y the same network location as the v6? Upgraded in place?
| rgn wrote: |
| It worked before...I changed my dll and now it doesn't work...? |
I found this which almost looks like your problem backwards (v6 not working). I do wonder if the conflicting dlls is a place to start looking though.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rgn |
| Posted: Tue May 15, 2012 9:58 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
I will check the link, but there is NO v7 qMgr. The qMgr is v6...always has been, nothing has changed. The only change is that I am now using the v7 as opposed to the v6 dll.
That is why I am curious why this would be network related. I was able to connect fine when i was using the v6 client. I am not saying you guys are wrong, just that I don't know how to approach this question or what my response is when I try to tell the network guys it is the network, but I am the one that made changes. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 10:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rgn wrote: |
| That is why I am curious why this would be network related. |
This is why I felt the link might be a starting point. The TCP/IP code (the same as the one you're experiencing) seemed to be an artifact of the clients bouncing off the local stack rather than an external network component at fault.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rgn |
| Posted: Tue May 15, 2012 10:52 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
I have been checking for duplicate dlls and I haven't seen anything nor have I seen a local error in the errorlogs that states that. I did reboot my pc just in case I had something hung up and retried and I get the same error.
I don't have messages writing to the error log (AMQERR01.LOG) like I did for v6. Is this in another location with 7? |
|
| Back to top |
|
|
| rgn |
| Posted: Tue May 15, 2012 11:05 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
| Quote: |
| The TCP/IP code (the same as the one you're experiencing) seemed to be an artifact of the clients bouncing off the local stack rather than an external network component at fault. |
The MQ guys are saying they are seeing me hit the qMgr, but that it doesn't like something. That makes me think it is something between mq client v7 and qMgr v6.
I am still trying to get confirmation on the 'inq' authority... |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 11:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rgn wrote: |
| I have been checking for duplicate dlls and I haven't seen anything nor have I seen a local error in the errorlogs that states that. I did reboot my pc just in case I had something hung up and retried and I get the same error. |
It's not that then... 
I don't have messages writing to the error log (AMQERR01.LOG) like I did for v6. Is this in another location with 7?[/quote]
Nope, same place. That's me out of ideas.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 11:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rgn wrote: |
| The MQ guys are saying they are seeing me hit the qMgr |
Seeing how? Seeing where? This is what we experts call "a clue".
| rgn wrote: |
| it doesn't like something. |
Congratulate them from me on their grasp of the technical terminology. 
Then suggest they switch on events, especially authority events, to pin down the "something".
| rgn wrote: |
| I am still trying to get confirmation on the 'inq' authority... |
An authority event would confirm this in 10 seconds.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rgn |
| Posted: Tue May 15, 2012 11:12 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
Maybe this will help....
I have been catching the error, but the completion code and reason codes are as follows:
CC = 2
RC = 2035 (07F3) (RC2035): MQRC_NOT_AUTHORIZED |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue May 15, 2012 11:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rgn wrote: |
Maybe this will help....
I have been catching the error, but the completion code and reason codes are as follows:
CC = 2
RC = 2035 (07F3) (RC2035): MQRC_NOT_AUTHORIZED |
Maybe that will help? You have a gift for understatement.
That explains it, doesn't it? An authority event will identify what's missing. If you're still uncertain.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rgn |
| Posted: Tue May 15, 2012 11:41 am Post subject: |
|
|
Novice
Joined: 15 Dec 2011
Posts: 15
|
|
| Back to top |
|
|
| JasonE |
| Posted: Wed May 16, 2012 1:15 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Quote: |
| I know nothing has changed since v6. If the qMgr is on 6 and the client is 6, would I need the +inq authority? Or do I only need that when I go to v7...? |
In MQ v7 XMS/.NET was moved closed to JMS/Java functionality and as such it means that when it connects to the queue manager, it needs to inquire some properties. Hence you need the +inq once your client side moves to v7... sorry
| Quote: |
| The return code from the TCP/IP (read) call was 104 (X'68') |
| Quote: |
| ECONNRESET 104 (0x68) Connection reset by peer |
| Quote: |
| Clearly a network issue. WMQ is the victim of this, and is merely reporting it. |
So in this case, the connection is opened, fails and throws an exception and hence isnt closed. The server correctly reports that the other end has closed the socket without cleaning it up properly. This is not a network error (not all network error reports mean its a network problem (but most...))
| Quote: |
I have been catching the error, but the completion code and reason codes are as follows:
CC = 2
RC = 2035 (07F3) (RC2035): MQRC_NOT_AUTHORIZED |
For reference, if you try setting environment variable MQS_REPORT_NOAUTH before starting the queue manager on Unix, then you should get better error reporting of 2035's in the queue manager error logs (they come out as default on windows)... give it a try  |
|
| Back to top |
|
|
|
|
