| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| AMQ4059 issue on Windows 7, 64 bits |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Sun Dec 30, 2012 3:46 pm Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Wow. From this post I had absolutely no idea that you were anything but a new mq admin. You gave us no indication that you had ever installed wmq, created a qmgr, defined a channel, ...
I certainly had not intended to offend.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
 |
| drodrick |
| Posted: Sun Dec 30, 2012 4:16 pm Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
| bruce2359 wrote: |
| I certainly had not intended to offend. |
Nope, neither you nor anybody else offended me at all. You and others are definitely trying to help me out by a different vision and knowledge and making sure the fundamental MQ basics are taken care of. If I cannot get solution here, probably I will never be able to fix it. May be I did not provide you some important clue to pin point the culprit!
Anyway, thank you!! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 30, 2012 5:36 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
This is not rocket science.
Are you a Windoze person? You indicated that the real installation is to be linux.
So, when you uninstalled wmq from your laptop, did you do a search for amq*.* to make sure there were no wmq modules remaining in the filesystem?
Did you install using the usual Windoze installer?
Did you install Eclipse first?
Did you reboot?
Did the install go perfectly?
Sorry if these sound like stupid questions, but i dont want to make assumptions.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Sun Dec 30, 2012 8:42 pm Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
Ok, after searching so many forums and postings for days, finally, I got it fixed !!
There were two issues here. One with Winsock (Windows socket) and another with MCA User Id of SVRCONN channel.
Following two statements cleaned winsock entries and TCP/IP stack.
netsh winsock reset catalog (resets winsock entries)
netsh int ip reset reset.log hit (resets TCP/IP stack)
In SVRCONN channel's MCA UserId, I tried following.
Blank MCAUserId DID NOT WORK.
'mqm', which is a group and has my userid 'testid' as member of it, DID NOT WORK.
'mqm@MyComputer' also DID NOT WORK.
But 'testid@MyComputer' WORKED!!
Thank you all for your time and help !! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 30, 2012 9:26 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Which listener are you using?
A qmgr listener object DEFINE LISTENER? Or are you using the runmqlsr control command?
Neither? If so, why?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Mon Dec 31, 2012 6:22 am Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
| Queue manager listener object, which was created while creating the queue manager using the wizard on MQ Explorer. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 31, 2012 7:05 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| drodrick wrote: |
There were two issues here. One with Winsock (Windows socket) and another with MCA User Id of SVRCONN channel.
Following two statements cleaned winsock entries and TCP/IP stack.
netsh winsock reset catalog (resets winsock entries)
netsh int ip reset reset.log hit (resets TCP/IP stack)
|
What lead you to try these commands? I ask because I've never needed to use either.
Had you previously reconfigured your laptop network for some other application?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Mon Dec 31, 2012 8:10 am Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
I saw following errors in AMQERR01.LOG file of 'WebSphere MQ\errors', NOT the queue manager 'errors'. Before that, I was paying attention to Qmgr errors only.
EXPLANATION:
An error occurred receiving data from MyComputer
(192.168.1.45)(1414)]whÉIÈ(îÀ*î over TCP/IP. This may be due to a
communications failure.
ACTION:
The return code from the TCP/IP recv() call was 10053 (X'2745'). Record these
values and tell the systems administrator.
I searched this TCP/IP error and found a website where it was suggested to clean TCP/IP stack with those commands. Once this TCP/IP issue was fixed, it gave me authority error, which I fixed by providing userid@hostname, instead of group@hostname. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 31, 2012 8:58 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Thank you for the detailed resolution.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 31, 2012 9:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| drodrick wrote: |
| I saw following errors in AMQERR01.LOG file of 'WebSphere MQ\errors', NOT the queue manager 'errors'. Before that, I was paying attention to Qmgr errors only.. |
The fellow who first introduced me to MQseries (when dinosaurs roamed the Earth), recommended the habit of always looking FIRST in the installation errors directory (to see if the issue is pervasive to all qmgrs); then looking SECOND in the qmgr errors directory.
Again, thanks for following up, and posting the real error messages, and your resolution.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| drodrick |
| Posted: Mon Dec 31, 2012 10:50 am Post subject: |
|
|
Novice
Joined: 26 Dec 2012
Posts: 17
|
| Quote: |
| The fellow who first introduced me to MQseries (when dinosaurs roamed the Earth), recommended the habit of always looking FIRST in the installation errors directory (to see if the issue is pervasive to all qmgrs); then looking SECOND in the qmgr errors directory |
Yes, I agree. |
|
| 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
|
|
|
|
