Hi Thanks for the advice.
Claus - We’re using log4j out of the box with ServiceMix. paxlogging would be a new direction, but would offer me what I want by the looks. It looks like I may have some success with http://activemq.apache.org/how-do-i-use-log4j-jms-appender-with-activemq.html I’ll let you know. Thanks James From: hekonsek [via Camel] [mailto:[email protected]] Sent: 20 July 2015 12:13 To: BURN, James Subject: Re: Camel access to ROOT log You can also consider creating your own logger appender that would send the log events to the channel that could be understood by Camel. Or maybe use JMS Topic appender [1] as a bridge between the Logger and Camel. Cheers! [1] http://logback.qos.ch/manual/appenders.html#JMSTopicAppender pon., 20.07.2015 o 12:12 użytkownik Claus Ibsen <[hidden email]</user/SendEmail.jtp?type=node&node=5769555&i=0>> napisał: > Hi > > You can try using paxlogging > http://camel.apache.org/pax-logging > > But afair it only reads new events. > > If you want to read a log file, you would need to use the file or > stream component and read the file directly from the file system. > > > On Mon, Jul 20, 2015 at 11:49 AM, BURN, James <[hidden > email]</user/SendEmail.jtp?type=node&node=5769555&i=1>> wrote: > > Hi > > > > I wonder if it is possible to use Camel to access the ServiceMix ROOT > log. We're running Camel 2.13.2 under ServiceMix 5.1.1. > > > > I've tried: > > > > <route id="ROOTLogger"> > > <from uri="log:ROOT" /> > > <to uri="file:ROOTlog"/> > > </route> > > > > But get loads of "Body is null" errors. > > > > I'm ultimately trying to create email alerts based on the ServiceMix > ROOT log, and manage this with Camel. > > > > Thanks for any advice. > > > > James > > > > > > > > > > > > Oxford University Press (UK) Disclaimer > > > > This message is confidential. You should not copy it or disclose its > contents to anyone. You may use and apply the information for the intended > purpose only. OUP does not accept legal responsibility for the contents of > this message. Any views or opinions presented are those of the author only > and not of OUP. If this email has come to you in error, please delete it, > along with any attachments. Please note that OUP may intercept incoming and > outgoing email communications. > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2nd edition: http://www.manning.com/ibsen2 > ________________________________ If you reply to this email, your message will be added to the discussion below: http://camel.465427.n5.nabble.com/Camel-access-to-ROOT-log-tp5769552p5769555.html To start a new topic under Camel - Users, email [email protected]<mailto:[email protected]> To unsubscribe from Camel - Users, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=SmFtZXMuQnVybkBvdXAuY29tfDQ2NTQyOHw5Njc4MTEwNDY=>. NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> Oxford University Press (UK) Disclaimer This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-access-to-ROOT-log-tp5769552p5769598.html Sent from the Camel - Users mailing list archive at Nabble.com.
