| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| "Fast first message"? |
View previous topic :: View next topic |
| Author |
Message
|
| NealM |
 Posted: Tue Aug 06, 2013 3:18 pm Post subject: "Fast first message"? |
 |
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
In various "What's new in MB8" presentations back in late 2011 and 2012 there was this paragraph:
| Quote: |
“Fast first message” processing with pre-emptive database connections
– New configuration option acquires & maintains database connections before messages processed
• Default will connect first thread to database at flow start before message processing
– Extra flow option to start all flow threads at EG start
• All threads process “fast first message”
– Immediate reconnect option database after failure
• Retry once for successful reconnect
• Exception still thrown to rollback transaction |
But I cannot find mention in the 8.0.0.2 Info Center. Nor on MB Explorer or on the several mqsi.. line commands that I looked at.
Could someone here point me to where I should be looking for more details?
Thanks |
|
| Back to top |
|
 |
| Simbu |
| Posted: Tue Aug 06, 2013 7:09 pm Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
There is a property "Connect before flow starts" in compute node and database node. if you check this box, you can achieve “Fast first message” processing.
| Code: |
By default, the broker connects to the data source when required in a message flow.
If you select the check box, data source connections are made before the flow receives a message, rather than during message flow processing. |
|
|
| Back to top |
|
|
| NealM |
| Posted: Wed Aug 07, 2013 7:02 am Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
|
| Back to top |
|
|
| Herbert |
| Posted: Wed May 21, 2014 10:39 pm Post subject: |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
Some experiences about this option.
I had performance problems after a WMB 6.1 to IIB 9.0 migration project and turning on this "Connect before flow starts" option did help a lot.
Also, it seems that if you have select this just for 1 flow then other flows where this options is not turned on also benefits ... maybe turning this option on for 1 flow triggers an connection pool mechanism where all flows that use the same ODBC connection benefits from? |
|
| 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
|
|
|
|
