ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » amq9259

Post new topic  Reply to topic
 amq9259 « View previous topic :: View next topic » 
Author Message
George Carey
PostPosted: Thu Apr 19, 2012 2:50 pm    Post subject: amq9259 Reply with quote

Knight

Joined: 29 Jan 2007
Posts: 500
Location: DC
Looking for the best explanation of what is causing this error (from memory or a manual or where ever):

I have two app server engines talking to an MQ server doing JMS API calls to put messages onto a request queue and same app servers are using MDB listeners to get message replies off a reply queue.

The messages are flowing fine but I see a boat load of AMQ9259s in the MQ server error logs:

AMQ9259 : process (1234.5678) user mqm Program amqrmppa
Connection from host 01.02.03.04 timed out

Explanation:

A connection from host 01.02.03.04 over tcp/ip timed out
Check to see why data was not received in expected time. Correct the problem. Reconnect the channel or wait for the retrying channel to reconnect itself.

We had problems with orphaned channels building up so we used the ClientIdle parameter to cure this. Is the ClientIdle switch forcing the AMQ9259s?

TIA
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding")
Back to top
View user's profile Send private message Visit poster's website AIM Address
fjb_saper
PostPosted: Thu Apr 19, 2012 8:03 pm    Post subject: Re: amq9259 Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
George Carey wrote:

We had problems with orphaned channels building up so we used the ClientIdle parameter to cure this. Is the ClientIdle switch forcing the AMQ9259s?

TIA

I'd expect so. The question really is why did you use ClientIdle instead of trying to get at the root problem: Why are some applications not closing the connection? I guess the build up comes from WAS. The other question is to look at the buildup and determine if it is legitimate...

  • how many connections are needed looking at the MDB setup (number of bean instances + 1 with a sum across all MDB's
  • how many additional instances are needed related to mdbs (answer session) (number of bean instances across all beans doing a reply)
  • How many concurrent request scenarios using another connection will your WAS server support
  • etc...


Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » amq9259
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
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.