MQSeries.net :: View topic - AMQ9213: A communications error for TCP/IP occurred

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » AMQ9213: A communications error for TCP/IP occurred

Goto page Previous 1, 2

AMQ9213: A communications error for TCP/IP occurred

« View previous topic :: View next topic »

Author

Message

kevinf2349

Posted: Fri Jun 16, 2006 3:58 am Post subject:

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

I believe MQSoftware has a package (QPasa?) that will detect a channel stopping and try and restart it. If you have the budget that is. I would be surprised if there weren't others out there (Omegamon?) that do the same thing.

The question is....does the cost to the business of these disconnects warrant the cost of the monitoring package?....only you can answer that.

PeterPotkay

Posted: Fri Jun 16, 2006 2:31 pm Post subject:

Poobah

Joined: 15 May 2001
Posts: 7722

If you can't deal with messages piling up in an XMITQ to QM1 because QM1 is N/A and instead want to go to then go to QM2, then just use MQClient conections and try to connect directly to QM1. If you can't go to QM2 directly yourself.

Monitoring MQ channels and choosing which way to go is NOT the way to accomplish this.

Quote:

I believe MQSoftware has a package (QPasa?) that will detect a channel stopping and try and restart it.

Kevin, yes QPASA can do that. So can MQ

(retry interval)
_________________
Peter Potkay
Keep Calm and MQ On

kevinf2349

Posted: Sat Jun 17, 2006 11:06 am Post subject:

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

Quote:

So can MQ (retry interval)

True but my understanding was that the application program is somehow checking the status of the channel (and I agree with you and others that this is never a good thing to do). So I sort of assumed an external monitor would be a better solution for them in this case.

Personally I would use a mix of heartbeats, reties and tirggering for this but I suspect the whole application is badly designed in the first place and from what has been said so far that is beyond the scope of the poster.

fjb_saper

Posted: Sat Jun 17, 2006 5:40 pm Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

How about an MQ Cluster. With 6.0 you can set a preferred target (cluster workload parm from 0 to 9) and if that is not available it would automatically fall back to the other cluster member(s).

You could even achieve load balancing if you were so inclined!...

_________________
MQ & Broker admin

tychak

Posted: Wed Jul 12, 2006 3:10 am Post subject:

Novice

Joined: 16 Mar 2004
Posts: 19

Thanks for your comments.

I think I should pay attention to troubleshoot why there's TCP/IP errors as the servers are connected to the same switch. It would be grateful if someone can help on explaining the MQ error message and how is it related to network problem.

Display posts from previous:

Goto page Previous 1, 2

Page 2 of 2

MQSeries.net Forum Index » General Discussion » AMQ9213: A communications error for TCP/IP occurred

Jump to:

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

Protected by Anti-Spam ACP