Posted: Mon Dec 12, 2011 4:18 pm Post subject: Connection handle
Acolyte
Joined: 21 Jun 2011 Posts: 50
Hi,
I tried to put a message to QM QA by issuing amqsput,i see the connection handle is inactive.But when i tried to issue amqsget to the same queue QA.local then i see the connection handle is active by viewing Qstatus..So how does the Connection handle turns active when an application open the Q for putting mess.?.As i see in infocenter It turns into active only when an API call is in progress for this queue.But by issuing amqsput call still the application is issuing the API call but the connection handle shows still inactive.......
Did you try reviewing the source code of amqsput and amqsget, to see how they work, to see if you can spot any meaningful differences in how the code is structured around the relevant MQPUT and MQGET calls?
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
Its unlikely you will see the handle being active during MQPUT, as the call may take less than one thousandth of a second. MQGET can take a similar short time if there is an elligible message on the queue to get. MQGET can take longer if the MQGMO_WAIT option is used and there are no messages available straight away (amqsget calls MQGET with 15 second wait interval). _________________ Glenn
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