Author |
Message
|
moorej_gl |
Posted: Wed Nov 01, 2006 8:51 am Post subject: ODBC data source changes while broker is running? |
|
|
 Apprentice
Joined: 01 Dec 2003 Posts: 35 Location: Madison, WI
|
We're running a v5 broker on Windows 2003 and we have an ODBC connection to a SQL user database. At some point, the default database setting was cleared and the data source was then configured to the wrong database. I'm trying to get an idea of when this happened (because I can't figure out how it changed), but it is getting complicated by a few things.
We have several message flows that use this data source. Several hours before any errors occurred, the broker was restarted. We had plenty of volume for a few hours with no problems, so I assume that the data source was still intact at the point of the restart. The message flow that finally failed had not been exercised since before the broker was restarted, and once messages came through it complained that the table it was looking for could not be found. When I fixed the data source and restarted the broker a second time, the problem was solved.
But if "When you start a broker, it opens all the connections that it requires", how could some message flows using a data source work while others using the same data source fail? Am I right to think that the data source was changed some time after the first time we restarted the broker? Any ideas would be appreciated. |
|
Back to top |
|
 |
madi |
Posted: Wed Nov 01, 2006 12:19 pm Post subject: |
|
|
 Chevalier
Joined: 17 Jan 2006 Posts: 475
|
as far as I know
you only get a data source error when the message actually goes to the node (compute or database) which has that data source
it will not show while restart or deployment
no idea on how other flows worked fine which this one errored
--madi |
|
Back to top |
|
 |
moorej_gl |
Posted: Wed Nov 01, 2006 1:08 pm Post subject: |
|
|
 Apprentice
Joined: 01 Dec 2003 Posts: 35 Location: Madison, WI
|
Right, I understand that no errors like this would occur without a message to be processed. My point in mentioning the broker restart was that I'm trying to figure out when the broker would have picked up the wrong database config from the ODBC data source. And I'm trying to figure out whether it's possible that some message flows connected with the correct config of the data source, and others connected later on with the incorrect config of the same data source, after it had been changed, and without the broker being restarted. I didn't think that would be possible - but I don't see another way it could have happened. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Nov 01, 2006 1:11 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I wouldn't think that changing the ODBC data source would take effect while the broker was running.
On the other hand, if Broker had to open a new connection, I would sort of expect it to go back to the DSN itself to do so.
On the third hand... if I recall, you should have a test system or two that you could verify this with...  _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
moorej_gl |
Posted: Wed Nov 01, 2006 1:20 pm Post subject: |
|
|
 Apprentice
Joined: 01 Dec 2003 Posts: 35 Location: Madison, WI
|
Right - I'll set it up just as soon as my pulse returns to a normal rate.  |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Nov 01, 2006 1:33 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I'd have to stop drinking coffee for that to happen.
Doesn't seem productive, really. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
moorej_gl |
Posted: Fri Nov 03, 2006 9:50 am Post subject: |
|
|
 Apprentice
Joined: 01 Dec 2003 Posts: 35 Location: Madison, WI
|
Yep, I was able to do the same in our test system. Restarted the broker, exercised a couple message flows using the data source. Changed the data source and exercised other message flows also using it. The first message flows continued working properly; the ones that had not yet been exercised picked up the new configuration and broke. Now I just have to figure out why the data source changed.  |
|
Back to top |
|
 |
|