| Author |
Message
|
| wschutz |
 Posted: Tue Aug 29, 2006 8:09 am Post subject: |
 |
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Let me suggest we start with this configuration:
1. V6 client (with latest service) going to a V5.3 qmgr (with latest service) on a seperate machine, getting amqsputc running with the SERVER variable and then the client channel
then...
2. V6 client (with latest service) going to a V5.3 qmgr on a seperate machine using the java client (MQEnvironment variable) and then trying to use a channel table ....
_________________
-wayne |
|
| Back to top |
|
 |
| tapak |
| Posted: Tue Aug 29, 2006 9:34 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Hi Wayne,
Thank you for looking into it . I reinstalled V6 again and tried connecting using amqsputc to v53 server . Here is the command I did and the server and client errors
C:\>set MQSERVER=SECADMIN/TCP/hostname-edited(1414)
C:\>amqsputc QL.DTEST qmname-edited
Sample AMQSPUT0 start
MQCONN ended with reason code 2059
Client Error
8/29/2006 13:26:00 - Process(804.1) User(dsubhram) Program(amqsputc.exe)
AMQ9202: Remote host '' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using to host '' was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a 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 is 0
(X'0'). 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 ''
was not running. If this is the case, perform the relevant operations to start
the listening program, and try again.
----- amqcrhna.c : 390 --------------------------------------------------------
Server Error
08/29/06 01:26:10 PM
AMQ9209: Connection to host 'lewispc (147.107.150.26)' closed.
EXPLANATION:
An error occurred receiving data from 'clientmcname (clientipaddredited)' over TCP/IP.
The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2736 -------------------------------------------------------
08/29/06 01:26:10 PM
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Aug 29, 2006 9:41 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
So, you only get this:
| Quote: |
AMQ9228: The TCP/IP responder program could not be started.
|
if you're using the V6 client....with the V5.3 client, it works OK?
_________________
-wayne |
|
| Back to top |
|
|
| tapak |
| Posted: Tue Aug 29, 2006 9:43 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Here is some more client errors I got when I tried to use M071 support pack
----- amqccita.c : 1103 -------------------------------------------------------
8/29/2006 13:36:52 - Process(2240.65) User(useridedited) Program(mqmonntp.exe)
AMQ9202: Remote host '' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using to host '' was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a 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 is 0
(X'0'). 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 ''
was not running. If this is the case, perform the relevant operations to start
the listening program, and try again.
----- amqcrhna.c : 390 --------------------------------------------------------
8/29/2006 13:36:57 - Process(2240.64) User(useridedited) Program(mqmonntp.exe)
AMQ9202: Remote host 'bs135766 (ÿÿÿÿc¥qza¥qp˜ß×) (1414)' not available,
retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'bs135766
(ÿÿÿÿc¥qza¥qp˜ß×) (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
10060 (X'274C'). 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 'bs135766 (ÿÿÿÿc¥qza¥qp˜ß×) (1414)' was not running. If this is the
case, perform the relevant operations to start the TCP/IP listening program,
and try again.
----- amqccita.c : 1103 ------- |
|
| Back to top |
|
|
| tapak |
| Posted: Tue Aug 29, 2006 9:53 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
| wschutz wrote: |
So, you only get this:
| Quote: |
AMQ9228: The TCP/IP responder program could not be started.
|
if you're using the V6 client....with the V5.3 client, it works OK? |
Yes I listed out the errors I got when I ran amqsputc on a v6 client to connect to a v53 server.
I was able to connect from v53 client to v53 server without any issues uisng amqsputc. I didnt get your last question. |
|
| Back to top |
|
|
| tapak |
| Posted: Tue Aug 29, 2006 11:19 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
I see that java client using MQEnvironment variables works with v6 client to v53 server . But I am getting a 2278 error when I use channel definition table instead of MQEnvironment variables.
amqsputc doesnt work with MQSERVER variable or MQCHLLIB variable.
I get 2059 on using MQSERVER and 2058 on using MQCHLLIB |
|
| Back to top |
|
|
| tapak |
| Posted: Tue Aug 29, 2006 12:03 pm Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
I see that java client using MQEnvironment variables works with v6 client to v53 server . But I am getting a 2278 error when I use channel definition table instead of MQEnvironment variables.
amqsputc doesnt work with MQSERVER variable or MQCHLLIB variable.
I get 2059 on using MQSERVER and 2058 on using MQCHLLIB |
|
| Back to top |
|
|
| tapak |
| Posted: Tue Aug 29, 2006 12:07 pm Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Wayne ,
My teammate has created a PMR with IBM on the V6 client issue . This is for your info. Here is the PMR no in case you have access to it.
PMR number 20123 180 000
Thanks ..Deepak |
|
| Back to top |
|
|
| tapak |
| Posted: Tue Aug 29, 2006 1:23 pm Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
One more problem I cam across on using the mqver6 client to mq53 .The qmgr.close doesnt close the connection to the queue manager .
Here is the server log .
08/29/06 05:11:37 PM
AMQ9209: Connection to host 'mymcname (ipaddr)' closed.
EXPLANATION:
An error occurred receiving data from 'mymcname (ipaddr)' over TCP/IP.
The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 29, 2006 1:59 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Of course, you can only establish client connections to a channel of SVRCONN type - but you knew that. 
And, of course, you have verified that BlockIP has nothing to do with your problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tapak |
| Posted: Wed Aug 30, 2006 7:27 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Jeff,
I forgot to verify it is anything to do with BLockIP after reinstalling Ver6 client. Thanks for the reminder.
I got the same error with a regular channel too.
I dont see if it is related to the mqserver version . As we are able to connect to some other mqservers with same version level (including mq ver 52 and 53 csd4) . But there are some machines we couldnt connect after installing mqver6 client.
My teammate has created a PMR .Will post the reply once I get some info.
Thanks, Deepak |
|
| Back to top |
|
|
| tapak |
| Posted: Fri Sep 08, 2006 7:50 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
It looks like IBM come up with a fix for the issue I had with V6 client for Windows.
Here is the details.
Fix details:
------------
Below is a summary of each issue fixed in this package
----------------------------------------------------------------------
IY88948 SUMMARY:
----------------------------------------------------------------------
WMQ CHANNEL FAILS TO START WITH AMQ9202 ON WINDOWS
USERS AFFECTED:
---------------
Customers using WebSphere MQ version 6 for Windows who use
channels to communicate with a remote queue manager. This APAR
is not applicable to WebSphere MQ version 5.3 because the
affected code did not exist in that version.
Platforms affected:
Windows
PROBLEM SUMMARY:
----------------
On Windows, WebSphere MQ uses a platform-specific function to
convert numeric IP address bytes into their string
representation. This is used for display purposes in channel
status entries and error logs.
The Windows implementation of this function contained an
incorrect validation check on the IP address which caused it to
reject certain IP addresses.
PROBLEM CONCLUSION:
-------------------
The incorrect validation code was removed. |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Sep 08, 2006 8:47 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Glad to see you got this resolved.
_________________
-wayne |
|
| Back to top |
|
|
| tapak |
| Posted: Fri Sep 08, 2006 9:32 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
It looks like my 2278 problem is not yet resolved . I will try creating a different client conenction channel and see if it helps .
Here is the stacktrace.
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2278
at com.ibm.mq.MQQueueManager.sequentialConstruct(MQQueueManager.java:945)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:819)
at com.bs.pcftest.BSPCFMessageListQueueDepth.main(BSPCFMessageListQueueDepth.java:35) |
|
| Back to top |
|
|
| tapak |
| Posted: Fri Sep 08, 2006 9:39 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Is there anything else missing in my client definition.
AMQ8414: Display Channel details.
CHANNEL(DEEPAK) CHLTYPE(CLNTCONN)
TRPTYPE(TCP) DESCR( )
QMNAME(qmname-edited) MODENAME( )
TPNAME( ) SCYEXIT( )
MAXMSGL(4194304) SCYDATA( )
USERID( ) PASSWORD( )
CONNAME(hostname(port)-edited) HBINT(300)
SSLCIPH( ) LOCLADDR( )
KAINT(AUTO) ALTDATE(2006-08-29)
ALTTIME(11.57.37) SSLPEER()
SENDEXIT( )
RCVEXIT( )
SENDDATA( )
RCVDATA( ) |
|
| Back to top |
|
|
|
|
