QConnector » POC - Prototype

Based on discussion, while queue pool is full (during peak time) till not able to accept any new incoming request, instead of request is wait till no end which will impact on frontend app waiting time, go for approach that drop the request packet or set the request timeout. As request has already been stored in Event Log table, which can be pick up for re-try during re-try daemon execution later.

Please test on the approach of drop packet/request timeout setting.

Change the policy from BLOCK to DROP when reach the maximum size of message in a queue. If maximum size is reached, all of the subsequent message will be dropped.

There is a jmeter script to verify the scenario:

http://192.168.2.13:50000/svn/qconnector/trunk/qconnector-config/jmeter/qconnector_max_queue.jmx

1. copy the script to your local machine
2. login to 192.168.2.13
   1. cd to /opt/jboss-5.1.0.GA/server/default-with-hornetq/deploy
   2. rename the ws-mimic.war to ws-mimic.war.bak
      • to avoid any applications to consume the test messages
3. launch jmeter and execute the script
   • press Ctrl + r or Run -> Start
4. after the test, perform:
   1. cd to /opt/jboss-5.1.0.GA/server/default-with-hornetq/deploy
   2. rename the ws-mimic.war.bak to ws-mimic.war
      • to restore the application
   3. go to this URL, http://192.168.2.13:8180/jmx-console/HtmlAdaptor?action=inspectMBean&name=org.hornetq%3Amodule%3DCore%2Ctype%3DQueue%2Caddress%3D%22jms.queue.RequestQueue%22%2Cname%3D%22jms.queue.RequestQueue%22
      1. invoke the removeMessages() operation to remove all test messages