Posted: Mon Feb 27, 2012 11:26 pm Post subject: Broker and database query behavior
Acolyte
Joined: 26 Oct 2005 Posts: 65
Hello.
We have some configurable properties in database. Our message flow reads this data and takes decisions based on it.
However, if I change some parameter values in the database (either by another flow or manually and then commit the change), my message flow continues to run with old data. It somehow does not get updates and I have to reload EG to make changes effective.
Am I missing some configuration on odbc driver or within the broker?
I tried searching answers on the forum. May be it's just me but no help!
(Message broker 6.1.0.4 using odbc drivers and database is oracle 10g)
Is your broker code caching the DB parameter values ? There is no reason a broker flow cannot access modified DB values if it's actually reading the DB
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Unless your flow does a periodic refresh of the params in the DB then your ONLY solution is to reload the EG or restart the Flow.
Normally where you are caching 'stuff' loaded from a DB (normally for performance reasons) you add a periodic timed DB refresh.
This is not difficult to code up but you do have to watch out if any of your flows have additional instances. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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