| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TCP persistant connections behaviour-WMB |
« View previous topic :: View next topic » |
| Author |
Message
|
| GeneRK4 |
 Posted: Mon Jan 12, 2015 1:04 am Post subject: TCP persistant connections behaviour-WMB |
 |
|
Master
Joined: 08 Jul 2013
Posts: 220
|
I have a requirement to do persistant connection on TCP.Its working fine by using same connection for the future transactions.
However I found the below observations while trying out with continuous transactions.
Need some advice on the below queries that arose during the observations
1.Even when EG is stopped and the flow is removed,one persistant connection is always established - Why one connection is always opened?
2.Only after stopping broker,persistant connection vanished.I believe that connection got closed abruptly
3.After broker restart ,tried to deploy the flow.Still no connection showing.Only for the very first transaction,the connection gets established
4.When transactions are triggered continuously with a delay of 2 to 3 seconds,one more connection got established -Why one new connection is opening up when already one is in established status from the same client and server?
5.After sending continuous requests,the older connection got closed and started with new connection - Not sure why within very few seconds,one connection got into TIME_WAIT status!
Thanks |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Jan 12, 2015 1:26 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
TCP/IP connection management is a complex subject - whether you are using IIB or some other product.
I suggest that you read this topic, and then ask any remaining questions.
http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac67380_.htm
[edited to actually include the URL!]
Also, it would be useful to know what type of data you are sending/receiving.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Mon Jan 12, 2015 8:43 am Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
Hi Kimbert,
I am using WMB version 8.0.0.4.
I am using CSV message in my transactions for both request and response and using Three-way handshake for the Asynchronous transactions.
I am not parsing the message.I am taking as BLOB in the flow.
I read through the link you have given.As I am not using configurable service,I believe the minimum client connections would be defaulted to 0.
I could not find the answers for the questions I have raised from the link.Could you help me to get clarified? |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jan 12, 2015 12:25 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
1. and 2. are hard to explain, unless there is another ( possibly phantom ) EG in the broker that owns the connection.
3. Sounds like correct behaviour, and I think you agree.
4. and 5. TCP/IP applications are not always well behaved. Are you sure that this problem is not being caused by the application that WMB is connecting to? If it was holding on to the connection then that might explain it. Or, if the TCPIP output node was set to hold on to the connection after the flow completes, then that would produce these symptoms.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| GeneRK4 |
| Posted: Mon Jan 12, 2015 5:12 pm Post subject: |
|
|
Master
Joined: 08 Jul 2013
Posts: 220
|
| kimbert wrote: |
| 1. and 2. are hard to explain, unless there is another ( possibly phantom ) EG in the broker that owns the connection. |
There is only one EG which has extablished connection.No other EG is present.
| kimbert wrote: |
| 3. Sounds like correct behaviour, and I think you agree. |
I truely agree.I have just given my observation.This is not query.
| kimbert wrote: |
| 4. and 5. TCP/IP applications are not always well behaved. Are you sure that this problem is not being caused by the application that WMB is connecting to? If it was holding on to the connection then that might explain it. Or, if the TCPIP output node was set to hold on to the connection after the flow completes, then that would produce these symptoms. |
I am not sure whether the other end Application is holding the connection.I want to prove it if so.Kindly let me know what is the way to prove from our end....
In WMB flow,for TCPClientOutput node ,I have set "Close Connection" property as "No" to achieve persistant TCPIP connection.
Is there any problem with this configuration? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
