| Author |
Message
|
| zpat |
 Posted: Mon Jun 28, 2010 6:18 am Post subject: WMB database connections |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
AIX 5, WMB 6.1, SQL Server (and other databases).
I have read conflicting information about when the WMB broker acquires, caches and releases ODBC database connections (to application databases, not to the broker database).
What I want to know is - when the ODBC connection to the database (on another server) is first acquired, when it is released and what happens if the database server is restarted while the broker (not necessarily the message flow) is running?
I am concerned that a database server restart would leave the WMB database connection in an unuseable state, which would require manual intervention to stop/start the message flow that referred to it.
Last edited by zpat on Mon Jun 28, 2010 6:51 am; edited 1 time in total |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jun 28, 2010 6:48 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
We had a situation where someone (Grrrr) took sown an oracle DB the other week. Nope, thet didn't ask or even attempt to stop the flows using that DB.
After some 6500+ Severity E messages in the wmbevent.log file, the DB was restarted and Broker carried on as before.
I have seen some versions of SQLServer fail to handle this very well. In the case above, it was handled ok. We just replayed all the messages on the BOQ and everything was hunky dory again.
I don't think there is one blanket atatement that would cover all DB's and the mix of platforms that Broker Runs on. If I were asked this, I'd CYA with a statment like "It depends. This is something I'd have to test thoroughly"
_________________
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. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 28, 2010 6:53 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's particularly a concern with SQL server, because Wintel boxes are patched (and therefore rebooted) frequently.
I guess we will find out during development what happens. I have already asked the developer to test this scenario. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jun 28, 2010 7:00 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You may find that there you see a different behaviour depending upon the location of the SQLServer System. i.e. Are they local or Remote to the broker system. Local means SLQServer runs on the same physical server (or the same VM) as Broker.
_________________
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. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 28, 2010 7:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It also depends somewhat on what ODBC itself allows and what the connection is doing at the time of the server reboot. If, for example, the connection is waiting for a response from the SQL server and the SQL server doesn't provide one before it shuts down, then the connection may stall. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 28, 2010 7:33 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
SQL server doesn't run on AIX 
So it will be a separate server in the same data centre.
I hope the connection will not be waiting at the time, but I have another WMB application where this has happened with a connection to Oracle. |
|
| Back to top |
|
|
|
|
