| Author |
Message
|
| RogerLacroix |
 Posted: Thu Aug 15, 2002 8:08 pm Post subject: Bad Data? |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hello all, I'm posting this message for a friend.
Does anyone have experience with or knowledge of the follow error condition:
On S/390 v2.10 running MQ Series v2.1 the CHIN is recording the following message
+CSQX206E MQT0 CSQXRCTL Error sending data,
channel MQT0.QAT104,
connection qat104 (xx.xxx.xx.xx),
TRPTYPE=TCP RC=0000008C
+CSQX599E MQT0 CSQXRCTL Channel MQT0.QAT104 ended abnormally
+CSQX500I MQT0 CSQXRCTL Channel MQT0.QAT104 started
The x'8C' indicates the 'The pipe is broken'... does anyone know what this
means?
On AIX running MQ Series 5.x the error logs shows the following:
-------------------------------------------------------------------------------
AMQ9207: The data received from host 'CTRMVS (xx.xxx.x.xx)' is not valid.
EXPLANATION:
Incorrect data format received from host 'CTRMVS (xx.xxx.x.xx)' over
TCP/IP. It may be that an unknown host is attempting to send data.
An FFST file has been generated containing the invalid data received.
ACTION:
Tell the systems administrator.
-------------------------------------------------------------------------------
08/15/02 13:47:48
AMQ6184: An internal MQSeries error has occurred on queue manager QAT104.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has
been called. The failing process is process 24982.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM
support center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
The FFST file shows a major return code of 'rrcE_BAD_DATA_RECEIVED' and a minor return code of 'OK'.
This error is causeing our MQ application on UNIX to core without much to
work on. If anyone can help, it would be appreciated.
Thanks!
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| skn |
| Posted: Fri Sep 05, 2003 8:41 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
did u get this resolved.
Thanks. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Fri Sep 05, 2003 8:51 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Wow, time warp. Hummm, I think IBM told them to apply an AIX OS patch. If I remember correctly, it fixed the problem.
later
Roger...
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| MSV |
| Posted: Thu Dec 04, 2008 9:55 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
Can someone provide me the version of os patch to be applied ?
I am facing the same issues...
"Major Errorcode :- rrcE_BAD_DATA_RECEIVED" &
"Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL"
My environment details are as follows
AIX: v5.3.8.0
MQ: v6.0.2.4
MB: v6.0.0.8 |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Dec 04, 2008 12:36 pm Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Since this thread is 5+ years old, I can't imagine the OS levels and patches would be of any use to you?
Are you having the same issue where this is definitely MQ <--> MQ traffic causing the problem? Do you have errors on both ends? Or is it more likely a telnet or port scanner? |
|
| Back to top |
|
|
| MSV |
| Posted: Fri Dec 05, 2008 5:30 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
Hi Toronto,
Thanks for your response.
We are sending webservice requests to the message broker using soapui(a webservice client). Here we are not getting any response. Instead, we found that the connection is refused and broker httplistener port 7080 is not running on the server.
There are no network connectivity issues found.
We analysed the broker configuration and found that 7080 is correctly configured. There are no issues found in MB.
We started analysing MQ errors and found the above errors "bad data". |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Dec 05, 2008 5:43 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Sounds like your sending app is directing its http requests at the MQ's Listener port instead of the Broker's Http port.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| MSV |
| Posted: Fri Dec 05, 2008 6:30 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
Hi Peter,
We have completely identical servers with the same set of installations/configurations/deployments. Application is working fine in all of those servers and we are able to see http responses.
So, this concludes there is no issue with the application as well.
The only change here when compared to the other servers is the IP address alone(in the webservice url). Everything else is identical. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 05, 2008 7:26 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MSV wrote: |
Hi Peter,
We have completely identical servers with the same set of installations/configurations/deployments. Application is working fine in all of those servers and we are able to see http responses.
So, this concludes there is no issue with the application as well.
The only change here when compared to the other servers is the IP address alone(in the webservice url). Everything else is identical. |
Back to Peter's point: I trust when you say the IP changed you really mean:
http://address:port/rest_of_url_unchanged.
If the port information is absent on the url a default port of 80 is used for http and 443 for https
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MSV |
| Posted: Fri Dec 05, 2008 10:59 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
Hi fjb_saper,
Yes. I mean only the ip address is changed in the below url.
[url]http://New IP address:7080/rest_of_url_unchanged[/url]
Even, I re-checked the port number within broker registry entries. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 05, 2008 2:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MSV wrote: |
Hi fjb_saper,
Yes. I mean only the ip address is changed in the below url.
[url]http://New IP address:7080/rest_of_url_unchanged[/url]
Even, I re-checked the port number within broker registry entries. |
Any port sniffer messing with your setup?
Any entries in the broker's log?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
