| Author |
Message
|
| Hanuman |
 Posted: Thu Oct 12, 2006 3:10 am Post subject: AMQ9202: Remote host 'elabsvr2 (3.209.124.60) (1414)' not av |
 |
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
hi can any one help in this....
10/12/2006 16:29:26 - Process(3280.1) User(942504) Program(amqsputc.exe)
AMQ9202: Remote host 'elabsvr2 (3.209.124.60) (1414)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'elabsvr2
(3.209.124.60) (1414)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'elabsvr2 (3.209.124.60) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
can anybody suggest me how to solve this problem... |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Oct 12, 2006 3:17 am Post subject: Re: AMQ9202: Remote host 'elabsvr2 (3.209.124.60) (1414)' no |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Hanuman wrote: |
| can anybody suggest me how to solve this problem... |
| Hanuman wrote: |
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'elabsvr2 (3.209.124.60) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Hanuman |
| Posted: Thu Oct 12, 2006 3:23 am Post subject: |
|
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
ya but my listner is running...
| Quote: |
bash-2.03$ runmqlsr -t tcp
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED. |
This should confirm u the same... now the new error is
But channel is already connected...
| Quote: |
define channel(CLIENT.QM_orf_qa01) chltype(SVRCONN) trptype(TCP) mcauser('942504')
3 : define channel(CLIENT.QM_orf_qa01) chltype(SVRCONN) trptype(TCP) mcauser('
AMQ8226: WebSphere MQ channel already exists. |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 12, 2006 3:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Sorry, why are you redefining the existing channel? Without using the REPLACE option?
I'm having a very dim morning... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Hanuman |
| Posted: Thu Oct 12, 2006 3:28 am Post subject: |
|
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
ok then who to replace it...
can u pls send me the command....
thanks in advance.... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 12, 2006 3:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
A failure of DEFINE CHANNEL doesn't tell you anything about whether or not the channel is connected.
All it tells you is that there is already some channel DEFINITION of the same name and same chltype. There might be no running INSTANCES of that definition, because the definition is wrong.
And there's nothing in the error message that suggested that the channel doesn't exist. You would only see that information in the error log on the SERVER side, not on the client side.
You seem to have confirmed that the listener is running. You seem to have confirmed that there is a proper channel definition on the server side.
You have not confirmed that the network between the client and the server is running, that the client machine can find the server by the name you are using, that the client machine can connect to the listener port.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 12, 2006 3:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
No, sorry, still not getting your situation. They've put caffine in my coffee or something....
a) You get a comms error (happens)
b) You check the listener (you decide it's running)
c) You attempt to fix the problem by defining the channel (this is where my brain goes soggy)
Sorry, still don't see what you're trying. What has the channel definition to do with a TCP/IP error? Especially for a client SVRCONN? What am I missing?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 12, 2006 3:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
But is the listener running under the right authority?
If the user running the listener process has no authorizations on the qmgr it is as if no listener process was running...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Oct 12, 2006 4:33 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Quote: |
But is the listener running under the right authority?
|
Must be this thread making your brain go soggy. runmqlsr is setuid/setgid mqm/mqm, so it will have the right authority.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 12, 2006 4:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Nigelg wrote: |
Must be this thread making your brain go soggy. |
So is this a poison thread, like a poison message? Are the moderators going to put us on a backout thread? 
Nice to know I'm not alone in my sogginess. Comforting to a man of my years...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Hanuman |
| Posted: Thu Oct 12, 2006 5:11 am Post subject: |
|
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
Ok let me explain what I did …
1. Start MQSC by typing the command:
runmqsc
A message tells you that an MQSC session has started. MQSC has no command prompt.
2. Define a server-connection channel by typing the following command on one line:
define channel(CLIENT.QM_orf_qa01) chltype(SVRCONN) trptype(TCP) mcauser('mqm')
A message tells you when the channel has been created.
3. Stop MQSC by typing:
end
Some messages are displayed followed by the command prompt.
4. Start a listener by typing the following command:
runmqlsr -t tcp
then invoked the client… from windowsxp mq
1. Open the Control Panel: Click Start > Settings > Control Panel
2. Double-click System.
3. Click the Advanced tab.
4. Click Environment Variables.
5. In the User Variables pane, click New.
6. Type MQSERVER into the Variable Name field.
7. Type into the CLIENT.QM_orf_qa01/TCP/3.209.124.60(1414)Variable Value field, where hostname is the computer name or IP address that identifies the machine hosting queue manager QM_orf_qa01. If you do not use the default port number 1414, you must also specify the port number where the listener is listening,
8. Click OK. The MQSERVER environment variable will appear in the User Variables pane.
Open a command prompt on the client and follow these steps:
1. Start the amqsputc sample program as follows:
o On Linux, change to the /opt/mqm/samp/bin directory and type the command: ./amqsputc Q1
o On Windows, type the command: amqsputc GEN2OSM_CPM_ALARM
The following messages are displayed:
Sample AMQSPUT0 start
target queue is Q1
2. Type some message text on one or more lines, then press Enter twice. The following message is displayed:
C:\Documents and Settings\942504>amqsputc GEN2OSM_CPM_ALARM
where GEN2OSM_CPM_ALARM is channel defined on Qmanager..
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
This time error code was
10/12/2006 16:29:26 - Process(3280.1) User(942504) Program(amqsputc.exe)
AMQ9202: Remote host 'elabsvr2 (3.209.124.60) (1414)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'elabsvr2
(3.209.124.60) (1414)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'elabsvr2 (3.209.124.60) (1414)' was not running. If this is the case,
perform the relevant operations to start the TCP/IP listening program, and try
again.
then I did was this
setmqaut -m QM_orf_qa01 -n SYSTEM.DEFAULT.LOCAL.QUEUE -t queue -p 942504 +allmqi
since client user id iis my deskstop where user id 942504
10/12/2006 16:44:23 - Process(3860.1) User(942504) Program(amqsputc.exe)
AMQ9520: Channel not defined remotely.
EXPLANATION:
There is no definition of channel 'CLIENT.QM_orf_qa01' at the remote location.
ACTION:
Add an appropriate definition to the remote hosts list of defined channels and
retry the operation.
Pls tell what think did I do wrong here…….
And how to resolve this error
MQCONN ended with reason code 2059 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 12, 2006 5:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You forgot to put your channel name in quotes, and so it got uppercased.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Hanuman |
| Posted: Thu Oct 12, 2006 5:22 am Post subject: |
|
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
sorry could not understand the jefflowrey
| Quote: |
| You forgot to put your channel name in quotes, and so it got uppercased. |
what is actual problem when i created a channel... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 13, 2006 7:46 am Post subject: |
|
|
Guest
|
MQ folds to object names to UPPERCASE if not enclosed by apostrophes (').
If you want lower-case or mixed-case object names, you must enclose the object name in apostrophes.
Your define channel command looked like this: define channeldefine channel(CLIENT.QM_orf_qa01)
It should look like: define channel('CLIENT.QM_orf_qa01'). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 13, 2006 3:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Nigelg wrote: |
| Quote: |
But is the listener running under the right authority?
|
Must be this thread making your brain go soggy. runmqlsr is setuid/setgid mqm/mqm, so it will have the right authority. |
Unless some security freak changed the permissions... Seen that happen to programs like netstat which became unusable because the sticky bit had been removed...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
