Glassfish JMS queue with HornetQ: Store locally and Forward remotely -
i need precise steps (with reference glassfish docs) following scenario;
- how create jms queues support "store locally , forward remotely". remote system hornetq.
- the remote connectivity should support ssl , user/password authentication
- it should support automatic retry , configuration of # of retry.
- in case of failure, should possible select jms messages resend in bulk
i went through of glassfish docs needs further validated experts.
simple scenario still not working "send jms sourcequeue , jms bridge service transfer targetqueue". here configurations;
a. domain.xml (extract)
<jms-service default-jms-host="default_jms_host" type="embedded"> <jms-host host="localhost" name="default_jms_host" lazy-init="false"> <property name="imq.bridge.bridge1.type" value="jms"></property> <property name="imq.bridge.bridge1.xmlurl" value="file:///c:/temp/bridge.xml"></property> <property name="imq.bridge.bridge1.autostart" value="true"></property> <property name="imq.bridge.bridge1.logfile.limit" value="0"></property> <property name="imq.bridge.bridge1.logfile.count" value="1"></property> <property name="imq.bridge.enabled" value="true"></property> <property name="imq.bridge.admin.user" value="admin"></property> <property name="imq.bridge.admin.password" value="admin"></property> <property name="imq.bridge.activelist" value="bridge1"></property> </jms-host> </jms-service>
b. bridge.xml (bridge configuration)
<?xml version="1.0" encoding="utf-8"?> <!doctype jmsbridge system "sun_jmsbridge_1_0.dtd"> <jmsbridge name="bridge1"> <link name="link1"> <enabled ="true"></enabled> <source connection-factory-ref=”jms/__defaultconnectionfactory" destination-ref="sourcequeue"></source> <target connection-factory-ref="jms/__defaultconnectionfactory" destination-ref="targetqueue "></target> </link> <connection-factory ref-name="jms/__defaultconnectionfactory"/> <connection-factory ref-name="jms/__defaultconnectionfactory"/> <destination ref-name="sourcequeue" type="queue" lookup-name="sourcequeue"/> <destination ref-name="targetqueue" type="queue" lookup-name="targetqueue"/> </jmsbridge>
glassfish deploys glassfish jms server. if want talk hornetq need use hornetq libraries , use proper api (either core or jms) talk hornetq server.
if need xa integration through mdbs need deploy resource adapter , proper recovery integration. @ glassfish on how deploy external resource adapter.. that's area nobody @ redhat has tested yet , given state of glassfish being discontinued doubt happen time soon.
another way deploy jms bridge within jboss / hornetq, message sent on glassfish jms consumed on hornetq through bridging process.
Comments
Post a Comment