This is just gone off the tangent line... in a good way though. We are going to try to push back and redesign the process to just simply make use of JMSAppender to put messages on a queue and have JMS clients consume them (and ultimately insert the logs into a database -- maybe use JSON for messages). The MQ runs within an integration broker, hence an initial idea of routing logging SOAP/service calls through the same broker that handles/routes other web services.
This whole marshalling and unmarshalling is very inefficient, on top of a fact that this proposed logging service is entirely internal to begin with. On Thu, May 1, 2014 at 10:59 AM, Ralph Goers <ralph.go...@dslextreme.com>wrote: > This thread originally started to ask about logging to a web service (that > term usually implies SOAP). It seems to have gone off into another > direction and I’m not sure if there is still a question here someone wants > answered. If you are making a proposal for an enhancement to Log4j 2 I am > not sure what it is. > > Ralph > > On May 1, 2014, at 8:51 AM, <walter_mar...@dellteam.com> > <walter_mar...@dellteam.com> wrote: > > > Dell - Internal Use - Confidential > > I take it we were discussing the possibilities for high speed production > logging. Previous people have rightly pointed out that a simplistic > approach using soap might be ineffecient > > > > -----Original Message----- > > From: Ralph Goers [mailto:ralph.go...@dslextreme.com] > > Sent: Thursday, May 01, 2014 10:36 AM > > To: Log4J Users List > > Subject: Re: Web Service Appender > > > > Thats fine. I'm just not really sure what the question is any more. > > > > Ralph > > > > On May 1, 2014, at 8:22 AM, walter_mar...@dellteam.com wrote: > > > >> Dell - Internal Use - Confidential > >> As I say there are a lot of architectural options. We need to decide on > one. Having th ability to modify log4j should make whatever architecture is > chosen cleaner. > >> > >> Thanks > >> > >> Walter > >> > >> -----Original Message----- > >> From: Ralph Goers [mailto:ralph.go...@dslextreme.com] > >> Sent: Thursday, May 01, 2014 10:16 AM > >> To: Log4J Users List > >> Subject: Re: Web Service Appender > >> > >> What you are describing is why I added the integration to Flume. It is > very, very good at collecting log events and forwarding them. However, you > could use a JMS appender to write your events to the MQ queue. > >> > >> Ralph > >> > >> On May 1, 2014, at 7:15 AM, Evan J wrote: > >> > >>> Hi Ralph, > >>> > >>> All the request and response messages, some header data, with > >>> additional information, are placed in an MDC, packaged in an Appender > >>> and sent to an MQ queue which, ultimately, makes a call to the > >>> service. It's a centralized logging model for all the applications in > >>> a cluster. Frankly, I don't like the design nor the setup, but I don't > make such decisions (or requirements). > >>> > >>> > >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote: > >>> > >>>> A web service to do what? Logging via SOAP would be extremely slow > >>>> if every log event is a single request. Can you elaborate on what > >>>> you really want to do? > >>>> > >>>> Ralph > >>>> > >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote: > >>>> > >>>>> Thanks for verifying this. I thought I might be missing an obvious, > >>>>> and this has already been implemented by at least someone. > >>>>> > >>>>> > >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma > >>>> wrote: > >>>>> > >>>>>> Evan, no I'm not aware of any appender that logs to a web service. > >>>>>> > >>>>>> > >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J > >>>>>> > >>>>>> wrote: > >>>>>> > >>>>>>> I searched around, but I could not find an off-the-shelf Appender > >>>>>>> that sends logs to a web service. Is there any? > >>>>>>> > >>>>>> > >>>> > >>>> > >>>> -------------------------------------------------------------------- > >>>> - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > >>>> For additional commands, e-mail: log4j-user-h...@logging.apache.org > >>>> > >>>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > >> For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
