MQSeries.net :: View topic - tcpNoDelay paremeter on HTTP Request Node

OtisFly · Posted: Thu Aug 13, 2009 2:35 am Post subject:

Hello
I'm using WMB 6.1 on Solaris 10. We are doing some webservice request via HTTP Request Nodes that were not performing as we would expect. We have set the tcpNoDelay parameter for the execution group in question to be true using:-

mqsichangeproperties <BrokerName> -e <ExecutionGroupName>
-o ComIbmSocketConnectionManager -n tcpNoDelay -v true

The broker has been restarted and when I run
mqsireportproperties <BrokerName> -e <ExecutionGroupName>
-o ComIbmSocketConnectionManager -r

the response is the following (I've blanked out host names and IP addresses):-

ComIbmSocketConnectionManager
uuid='ComIbmSocketConnectionManager'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
maxSocketAge='4'
maxKeepAliveRequests='90'
resetCollectionStatistics=''
tcpNoDelay='TRUE'
tcpNoDelaySSL='Platform Default'
SocketConnections
host='xxxx'
port='9081'
collectionUseCount='14'
totalSockets='12'
totalBytesSent='16081'
totalBytesRecv='44698'
totalChunksSent='42'
totalChunksRecv='29'
OpenSocket
ip='nn.nnn.nnn.nnn'
secure='FALSE'
created='2009-08-11 11:26:45.122752'
lastUsed='2009-08-11 11:26:47.941975'
bytesSent='3362'
bytesReceived='5726'
chunksSent='6'
chunksReceived='4'
useCount='2'
state='Connected'
tcpNoDelay='FALSE'
SocketConnections
host='xxxx'
port='80'
collectionUseCount='12'
totalSockets='11'
totalBytesSent='18146'
totalBytesRecv='26122'
totalChunksSent='36'
totalChunksRecv='25'
OpenSocket
ip='nn.nnn.nnn.nnn'
secure='FALSE'
created='2009-08-11 11:27:40.352672'
lastUsed='2009-08-11 11:27:45.834343'
bytesSent='1547'
bytesReceived='1409'
chunksSent='3'
chunksReceived='2'
useCount='1'
state='Connected'
tcpNoDelay='FALSE'

I'm confused as to why the open sockets seem to have the tcpNoDelay set to FALSE rather than TRUE. These connections were started after the broker restart and from within the execution group that I changed. I'm wondering if the call to the services is thus still be done with the tcpNoDelay set to FALSE.
Any ideas why this is, and what I can do to change it.?
Thanks
Otis