[ 
https://issues.apache.org/jira/browse/FLUME-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183038#comment-13183038
 ] 

Bruno Mahé edited comment on FLUME-923 at 1/10/12 2:56 AM:
-----------------------------------------------------------

Here is an example configuration file for flume-ng to exercise that jms sink.
It creates a netcat source and link it to a jms sink.

It assumes a broker is running on localhost on the standard port. So just 
downloading latest Apache ActiveMQ and doing a "bin/activemq start" should work.

The JMS sink does not depend explicitly on any broker (except for the tests). 
So the related jars would have to be made available on the class path. The 
easiest way may be to edit the pom.xml or to copy activemq-all-5.5.1.jar from 
Apache ActiveMQ into flume-ng lib dir

Note: This is not really meant for inclusion in flume, it's just for testing 
the patch

                
      was (Author: bmahe):
    Here is an example configuration file for flume-ng to exercise that jms 
sink.
It creates a netcat source and link it to a jms sink.

It assumes a broker is running on localhost on the standard port. So just 
downloading latest Apache ActiveMQ and doing a "bin/activemq start" should work.

The JMS sink does not depend explicitly on any broker (except for the tests). 
So the jar would have to be made available on the class path. The easiest way 
may be to edit the pom.xml or to copy activemq-all-5.5.1.jar from Apache 
ActiveMQ into flume-ng lib dir

Note: This is not really meant for inclusion in flume, it's just for testing 
the patch

                  
> Implement a JMS sink for Flume NG
> ---------------------------------
>
>                 Key: FLUME-923
>                 URL: https://issues.apache.org/jira/browse/FLUME-923
>             Project: Flume
>          Issue Type: New Feature
>            Reporter: Bruno Mahé
>            Assignee: Bruno Mahé
>         Attachments: FLUME-923.patch, jms.conf
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to