Hi all,

I'm working with a beanless setup, so I have everything set up by code. Now I 
need the master-slave functionality because the broker sometimes fails on 
production.

I've done this:
        .....setting up the brokserService
        JDBCPersistenceAdapter adapter = new JDBCPersistenceAdapter();
        adapter.setDataSource(dataSource);
        brokerService.setPersistenceAdapter(adapter);
        brokerService.start();

The DataSource is a manually created BasicDataSource with  a driver_class, url, 
username and password (C3P0 does not like to lent out datasources). . One 
broker  works fine in this way, I can easily monitor the messages in the queue 
appear and go away.

However, when I start two brokers on my laptop, one at port 8001 and one at 
port 8002, the application blocks when the second 'brokerService.start()' is 
called. Is there something else I should setup?

And, there is still a local folder called 'active-mq', shouldn't this be 
unnecessary when the JDBCPersistenceAdapter is used?

Thanks a lot!
Niels


                                          

Reply via email to