Hide Forgot
Title: Configure a JMS Bridge to Migrate Existing JMS Messages to JBoss EAP 6 Describe the issue: Section describes migrating messages using JMS bridge deployed on EAP 5. Add similar example with using JMS bridge on EAP 6.
Adding Justin to CC. He's probably the best person to provide info.
Check this out: https://access.redhat.com/site/solutions/480193 These are general instruction which can be adapted to JBoss Messaging.
Additional info: Additional explanation of individual bridge settings can be also found in upstream documentation: http://docs.jboss.org/hornetq/2.3.0.Final/docs/user-manual/html/jms-bridge.html (although configuration doesn't translate to EAP 1-to-1, so it would be better to consult with developers).
I am not clear... is this is a 'Migration Guide' issue or an 'Adminstration and Configuration Guide' issue?
Migration guide (more specific info is in Environment field in this bug).
Just to be clear about the use case here: This is about describing how to migrate JMS messages from EAP 5 to EAP 6. EAP 6.0 didn't support JMS bridges, hence the current documentation (with only possibility being the bridge deployed on EAP 5 server). However since 6.1 JMS bridges are fully supported again, so other option to migrate messages is with the bridge deployed on EAP 6 - this is the part that is missing in the document currently. The change didn't make it into 6.1 documentation, so it would be nice to manage this for 6.2.
Thanks Martin. :-)
All the stuff for "Procedure 3.20" looks good to me. However, the first sentence in "Procedure 3.19" says, "To avoid conflicts in classes between releases, you must use the following procedure to configure the JMS bridge on JBoss EAP 6.x." Shouldn't that say "JBoss EAP 5.x" at the end since the bridge is being deployed on JBoss EAP 5.x?
Sande, the text looks good (apart from version typo Justin pointed out), but I think it's a bit too general for migration guide, it should be a bit more specific for migrating from EAP 5 with JBoss Messaging or from EAP5 with HornetQ. My suggestion is: leave the text as is, but add an additional paragraph with list of specific client jars and initial naming factory the user needs to use (for both EAP5 with JBM and EAP5 with HornetQ). Justin, can you please provide the info? Also, will this work for EAP5 with HornetQ? Won't there be any class name conflicts with copying HornetQ 2.2 client jars to EAP6?
Justin, you are right in your comment above. That should say "To avoid conflicts in classes between releases, you must use the following procedure to configure the JMS bridge on JBoss EAP 5.x.". I fixed that issue in topic 9374. If you can provide me with a list of JARs, I will try to make it more specific. Are either of you on IRC? If so, which channels and what nick? I might make this move along more quickly. :-)
This is now staged here: http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Migration_Guide/index.html#Configure_a_JMS_Bridge_to_Migrate_Existing_JMS_Messages_to_Enterprise_Application_Platform_6
Looks good
Removed need-info on me.