Posted: Tue Sep 13, 2005 5:58 am Post subject: Channel staying running when remote side crashes
Apprentice
Joined: 15 Nov 2004 Posts: 43
I have a channel that stays in a running status when the remote side crashes. It is the sender channel that stays running so it doesn't try to connect. I don't have these channels setup to be triggered. If I set them up to be triggered will they automatically connect even though he thinks that he is already connected. The remote side does not support HBINT we do use TCP KeepAlive. My DISCINT is set to 0 as these channels have to always be active as they are used for interactive traffic.
The channel will move to retrying state once a message tries to use the channel.The channel intiator comes to play at that time.
Where as on the other scenario where the channel is in retrying state but the remote is up and running(Survived from crash) , then message in TXN queue will trigger the Chl.intiator to start the channel.So the channel will be move to running state.
Posted: Tue Sep 13, 2005 7:53 pm Post subject: Re: Channel staying running when remote side crashes
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
noles321 wrote:
My DISCINT is set to 0 as these channels have to always be active as they are used for interactive traffic.
This is not a reason for having them always running.
What is the lag time for starting the channel if it is in inactive mode ?
Is this acceptable to the application ? How often is it likely to happen and when is it likely to happen ?
These are the questions you really need an answer for.
You do realize that for a high traffic interactive application the channels will likely never go to inactive as there will always be traffic during the DISCINT interval to restart the DISCINT timer....
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