| Author |
Message
|
| dingjianrui |
 Posted: Tue Jun 26, 2012 5:11 pm Post subject: Websphere MQ 6.0.2.0 Error(Transaction Related) |
 |
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
i have three test machines i listed as below:
Machine S (Windows 2003 + MQ 6.0.2.0) -> MQ Server
Machine A (Windows 2003 + MQ 6.0.2.0 Client+Transaction Extend) -> MQ Client
Machine B (Windows 2008 R2 + MQ 7.0 Client+ Transaction Extend) -> MQ Client
Both Machine A and B can send message to Machine S without transaction. Machine A can send message to Machine S with transaction enabled, but Machine B cannot send message to Machine S with transaction enabled. I got following errors on the Machine S when B send transaction message to S.
EXPLANATION:
An error occurred receiving data from 'Machine S name (F•‚|¬)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
amqccita.c : 3094
2012-06-26 04:03:21 - Process(8636.7) User(s-mq-tst) Program(amqrmppa.exe)
AMQ9209: Connection to host 'Machine S name (F•‚|Ø)' closed.
EXPLANATION:
An error occurred receiving data from 'Machine S name (F•‚|Ø)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
amqccita.c : 3094
by the way, i also setup another environment which is consisted of MQ 6.0.20 server and MQ 7.0 client. they can work well without any issue.
who can help or supply some guidance? thanks very much. |
|
| Back to top |
|
 |
| mvic |
| Posted: Tue Jun 26, 2012 6:36 pm Post subject: Re: Websphere MQ 6.0.2.0 Error(Transaction Related) |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| dingjianrui wrote: |
EXPLANATION:
An error occurred receiving data from '...' over TCP/IP. The connection to the remote host has unexpectedly terminated. |
You are using old software levels, possibly this is a bug already fixed. Check if it works with the latest level.
The connection broke, maybe this is a bug already fixed (see above) or is a bug not yet fixed, or is some problem on the network. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 26, 2012 7:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you checked if the processId running MSDTC on the MQ Server has access to MQ (is part of the local mqm group?).
You need to run MSDTC with XA enabled on all 3 servers (both clients and MQ server) IIRC. I trust you followed all the com imperatives like strong key, part of component services and com visible... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dingjianrui |
| Posted: Tue Jun 26, 2012 11:13 pm Post subject: |
|
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
| fjb_saper wrote: |
Have you checked if the processId running MSDTC on the MQ Server has access to MQ (is part of the local mqm group?).
You need to run MSDTC with XA enabled on all 3 servers (both clients and MQ server) IIRC. I trust you followed all the com imperatives like strong key, part of component services and com visible... |
this client can send transaction message to another MQ server, seems the client configuration is correct. and this client can send message to Machine S without transaction seems the user id is correct. thanks. |
|
| Back to top |
|
|
| dingjianrui |
| Posted: Wed Jun 27, 2012 12:18 am Post subject: Re: Websphere MQ 6.0.2.0 Error(Transaction Related) |
|
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
| mvic wrote: |
| dingjianrui wrote: |
EXPLANATION:
An error occurred receiving data from '...' over TCP/IP. The connection to the remote host has unexpectedly terminated. |
You are using old software levels, possibly this is a bug already fixed. Check if it works with the latest level.
The connection broke, maybe this is a bug already fixed (see above) or is a bug not yet fixed, or is some problem on the network. |
i setup another two environment with the same software package, they can work properly. thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jun 27, 2012 4:36 am Post subject: Re: Websphere MQ 6.0.2.0 Error(Transaction Related) |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| dingjianrui wrote: |
| mvic wrote: |
| dingjianrui wrote: |
EXPLANATION:
An error occurred receiving data from '...' over TCP/IP. The connection to the remote host has unexpectedly terminated. |
You are using old software levels, possibly this is a bug already fixed. Check if it works with the latest level.
The connection broke, maybe this is a bug already fixed (see above) or is a bug not yet fixed, or is some problem on the network. |
i setup another two environment with the same software package, they can work properly. thanks. |
Then, the obvious question is: what is different between the environments where one works and the other does not?
_________________
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 |
|
|
| fjb_saper |
| Posted: Wed Jun 27, 2012 2:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dingjianrui wrote: |
| fjb_saper wrote: |
Have you checked if the processId running MSDTC on the MQ Server has access to MQ (is part of the local mqm group?).
You need to run MSDTC with XA enabled on all 3 servers (both clients and MQ server) IIRC. I trust you followed all the com imperatives like strong key, part of component services and com visible... |
this client can send transaction message to another MQ server, seems the client configuration is correct. and this client can send message to Machine S without transaction seems the user id is correct. thanks. |
Doesn't mean a thing. The question you need to ask yourself is what transaction coordinator is being used?
If it is WMQ why are you talking about the etc client?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jun 27, 2012 2:55 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
And what do you mean by 'transaction?'
_________________
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 |
|
|
| dingjianrui |
| Posted: Wed Jun 27, 2012 4:58 pm Post subject: |
|
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
| bruce2359 wrote: |
| And what do you mean by 'transaction?' |
Transaction means the client sends the message to server side in a distributed transaction. |
|
| Back to top |
|
|
| dingjianrui |
| Posted: Wed Jun 27, 2012 5:00 pm Post subject: Re: Websphere MQ 6.0.2.0 Error(Transaction Related) |
|
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
| bruce2359 wrote: |
| dingjianrui wrote: |
| mvic wrote: |
| dingjianrui wrote: |
EXPLANATION:
An error occurred receiving data from '...' over TCP/IP. The connection to the remote host has unexpectedly terminated. |
You are using old software levels, possibly this is a bug already fixed. Check if it works with the latest level.
The connection broke, maybe this is a bug already fixed (see above) or is a bug not yet fixed, or is some problem on the network. |
i setup another two environment with the same software package, they can work properly. thanks. |
Then, the obvious question is: what is different between the environments where one works and the other does not? |
from my point of view, there isn't any difference.  that's why i cannot figure it out, cause so far i haven't find any difference.  |
|
| Back to top |
|
|
| dingjianrui |
| Posted: Wed Jun 27, 2012 5:02 pm Post subject: |
|
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
| fjb_saper wrote: |
| dingjianrui wrote: |
| fjb_saper wrote: |
Have you checked if the processId running MSDTC on the MQ Server has access to MQ (is part of the local mqm group?).
You need to run MSDTC with XA enabled on all 3 servers (both clients and MQ server) IIRC. I trust you followed all the com imperatives like strong key, part of component services and com visible... |
this client can send transaction message to another MQ server, seems the client configuration is correct. and this client can send message to Machine S without transaction seems the user id is correct. thanks. |
Doesn't mean a thing. The question you need to ask yourself is what transaction coordinator is being used?
If it is WMQ why are you talking about the etc client? |
they use the Microsoft Distribute transaction Coordinator. |
|
| Back to top |
|
|
| dingjianrui |
| Posted: Wed Jun 27, 2012 6:45 pm Post subject: |
|
|
Newbie
Joined: 26 Jun 2012
Posts: 7
|
i put the partial of trace log here.
getaddrinfo(): AF_INET6 & AI_NUMERICHOST: rc=11001 errno=0
00085CAC 03:56:45.940417 1680.3 getaddrinfo(): AF_INET & AI_NUMERICHOST: rc=11001 errno=0
00085CAD 03:56:45.946688 1680.3 --------} cciTcpResolveHostname (rc=OK)
00085CAE 03:56:45.946743 1680.3 --------{ cciTcpResolveAddress
00085CAF 03:56:45.947434 1680.3 --------} cciTcpResolveAddress (rc=OK)
00085CB0 03:56:45.947444 1680.3 -------} cciTcpGetNameandAddress (rc=OK)
00085CB1 03:56:45.947457 1680.3 -------{ rrxError
00085CB2 03:56:45.947472 1680.3 RetCode = 20009209, rc1 = 0, rc2 = 0, Comment1 = 'machine namexx (Â )', Comment2 = 'TCP/IP', Comment3= '', File= 'F:\build\p600_P\src\lib\comms\amqccita.c', Line= '3094'
00085CB3 03:56:45.947482 1680.3 -------}! rrxError (rc=rrcE_CONNECTION_CLOSED)
00085CB4 03:56:45.947514 1680.3 *pointer(008BEF0C)
00085CB5 03:56:45.947525 1680.3 -------{ ccxFreeMem
00085CB6 03:56:45.947533 1680.3 -------} ccxFreeMem (rc=OK)
00085CB7 03:56:45.947541 1680.3 RetCode (rrcE_CONNECTION_CLOSED)
00085CB8 03:56:45.947549 1680.3 ------}! cciTcpReceive (rc=rrcE_CONNECTION_CLOSED)
00085CB9 03:56:45.947559 1680.3 -----}! ccxReceive (rc=rrcE_CONNECTION_CLOSED)
00085CBA 03:56:45.947598 1680.3 -----{ rriCommsError
00085CBB 03:56:45.947606 1680.3 -----} rriCommsError (rc=OK)
00085CBC 03:56:45.947613 1680.3 ----}! rriMQIServer (rc=rrcE_CONNECTION_CLOSED)
----} rrxReportError (rc=OK)
00085E01 03:56:45.952946 1680.3 ----{ xcsQueryValueForSubpool
00085E02 03:56:45.952957 1680.3 ----} xcsQueryValueForSubpool (rc=OK)
00085E03 03:56:45.952967 1680.3 ----{ rrxError
00085E04 03:56:45.952977 1680.3 RetCode = 20009999, rc1 = 0, rc2 = 0, Comment1 = 'BTSCHANNEL', Comment2 = '1680(8068)', Comment3= '', File= 'F:\build\p600_P\src\lib\remote\amqrmrsa.c', Line= '468'
00085E05 03:56:45.953004 1680.3 ----}! rrxError (rc=rrcE_ABNORMAL_CHANNEL_END) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 27, 2012 7:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you opened a PMR with IBM yet?
You need to supply both a trace from the server and a trace from the client.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
