Can you tell me the examples for JMX Bridge for JBM to HornetQ ?
I'm not sure what do you mean by "JMX Bridge". If you want to replace a JBM bridge with HornetQ one, you need to read the user manual. There isn't an example as far as I know.
Can you please tell me how we can configure multiple queues and topics with the JMS Bridge?
It is working with single queue.
I think you are going to need to deploy multiple bridge services.
Yes, thats right, I did the same thing, deployed multiple bridges and its working fine.
you wrote here
Yong Hao Gao wrote:
An update. It is still a work in progress. No need for everyone to waste time review now. But a quick scan to make sure I'm on the right track will be appreciated.
8. Migrating Existing Messages
Here gives the mapping between the database table and the HornetQ's bindings/journal
The main data should be remainging messages and binding informations, and possible long-running transactions.
There should be some tools/scripts to help on this.
Using bridge is also a convenient way.
I wasn't using bridges so far, and I need to migrate from JBOSS 4.2.3 that uses messaging 1.4.5 to 7.1.1 - can you point me to where I can find information on - what is a bridge? how do I set it up? ...
Check out this. Set up a bridge on the JBoss AS 4.2.3 side and push the messages from that server to the AS 7.1.1 server. I think you'll just need the <AS7_HOME>/bin/client/jboss-client.jar on the classpath of the 4.2.3 instance.
One thing that could be done is someone developing an exporter and import with the Importer with XML formater.
Something exports XML on JBM and the importer imports it.
nice idea. I'll keep this in mind...
Here is what I'm going to do it:
Write a tool that perform the following tasks:
1. read the JBM server config (messaging-service.xml, xxx-persistence-service and remoting-service.xml) and converts it to hornetq server config (based on what target user wants, it will generate server configuration suitable for AS5, AS7 or standalone).
2. read the JBM destinations and factories configures and converts them to HornetQ destinations and factories.
3. read the JBM messages and converts them to HornetQ ones.
Eash task will be divided into two steps.
Step 1. Reading JBM stuff and outputs the result into a XML file.
Step 2. Reading the XML file and generate HornetQ stuff.