| Author |
Message
|
| jeevan |
 Posted: Tue Apr 17, 2007 5:46 am Post subject: Database uses of Broker |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
How broker uses database? My question is if two broker created in a singple machine, can they use the same database? Do they create separate table inside the database?
Also, is there a way to have database centrally located in case of windows? The document sayd, the dsn can only use direct database on the same machine.
Thanks a lot |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 17, 2007 6:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I am not aware of any document that says that a broker database has to be local, on any platform.
Unless you are talking about Cloudscape/Derby, in which case one needs to remember that Cloudscape/Derby/BERNARD is not accessible from a remote machine.
I'm fairly sure that the Info Center discusses how to share a database between different brokers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Apr 17, 2007 6:17 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
This is what i found
| Quote: |
The short answer is no; 2 brokers cannot operate on the same sets of database tables concurrently. ActiveMQ is designed for high performance so we want to minimise the amount of pessimistic locking; each broker is designed to work with its own persistent database.
If you want to share the same physical database server across two brokers to simplify your installation & backup procedures then just create 2 different logins for each broker so that they get their own sets of database tables within the same physical database. (i.e. each broker gets its own logical database within the same physical database server)
|
I am not sure why we need to use two separate database for two databasee. I know we do not create two broker in one machine in general but i am trying to test /document cases if one has to do what should have been done. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 17, 2007 6:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| pcelari |
| Posted: Tue Apr 17, 2007 11:15 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
you can use the same database for as many brokers as your system can comfortably host. I use it for both DEV, QA and Production, although I plan to split out the production broker out of the system soon.
It's been my understanding that broker database is accessed only during deployment and start of a msgflow, so sharing it among several brokers shouldn't impact performance. Correct me if that's not the case.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Apr 17, 2007 1:09 pm Post subject: Use of broker Databases |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
From looking at the table names in the broker database, one of the uses of this database apart from storing message sets and flows, is to hold all the required data for pub/sub operations.
I am not sure how these are segregated between brokers sharing the same DB but it seems to work. I guess that the Broker UUID has something to do with it.
_________________
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 |
|
|
|
|
