Re: More maven build problems for log4j

[Brett Randall]

> Connection timed out

Are you building behind a firewall that requires you to use a http proxy
for internet access?  If so, you might want to review your
~/.m2/settings.xml and add appropriate / entries.

-Brett


On 2 May 2014 02:08,  wrote:

> Dell - Internal Use - Confidential
> No custom  ~/.m2/settings.xml file that I know of
>
> Build results=>
>
> C:\Software\log4j2source\apache-log4j-2.0-rc1-src>mvn install
> [INFO] Scanning for projects...
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2
> Downloading:
> http://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.pom
> [ERROR] The build could not read 7 projects -> [Help 1]
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-async:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-jpa:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-1.2-osgi-api:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-o
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-net:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-reduced:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\lo
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Mav

Re: Web Service Appender

[Ralph Goers]

Flume, not Felix.

Sent from my iPad

> On May 1, 2014, at 1:28 PM, Matt Sicker  wrote:
> 
> Your best bets for this are certainly Felix, JMS, or maybe even Syslog (the
> new RFC version) if you've got a server set up for that already. I'm going
> to back up Ralph's idea here that Felix really is the best way to go for
> this situation. It's one of the primary use cases for Felix (e.g., in EC2,
> it's great for centralized logging).
> 
> 
>> On 1 May 2014 12:54, Evan J  wrote:
>> 
>> 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 >> 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, 
>>>  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-

Re: Web Service Appender

[Matt Sicker]

Your best bets for this are certainly Felix, JMS, or maybe even Syslog (the
new RFC version) if you've got a server set up for that already. I'm going
to back up Ralph's idea here that Felix really is the best way to go for
this situation. It's one of the primary use cases for Felix (e.g., in EC2,
it's great for centralized logging).


On 1 May 2014 12:54, Evan J  wrote:

> 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  >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, 
> >  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 add

Re: More maven build problems for log4j

[Matt Sicker]

Try changing the maven-bundle-plugin version to 2.4.0. Or try building the
latest svn trunk.


On 1 May 2014 12:12, Gary Gregory  wrote:

> What about mvn package?
>
> Gary
>
>  Original message From:
> walter_mar...@dellteam.com Date:05/01/2014  12:08  (GMT-05:00)
> To: log4j-user@logging.apache.org Subject: RE: More
> maven build problems for log4j 
> Dell - Internal Use - Confidential
> No custom  ~/.m2/settings.xml file that I know of
>
> Build results=>
>
> C:\Software\log4j2source\apache-log4j-2.0-rc1-src>mvn install
> [INFO] Scanning for projects...
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2
> Downloading:
> http://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.pom
> [ERROR] The build could not read 7 projects -> [Help 1]
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-async:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-jpa:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-1.2-osgi-api:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-o
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-net:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] Unknown packaging: bundle @ line 28, column 14
> [ERROR]
> [ERROR]   The project
> org.apache.logging.log4j.osgi:log4j-core-osgi-reduced:2.0-rc1
> (C:\Software\log4j2source\apache-log4j-2.0-rc1-src\lo
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could
> not be reso
> gin:jar:2.3.7: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache (
> https://repository.apache.org/c
> ry.apache.org/140.211.11.74] failed: Connection timed out: connect ->
> [Help 2]
> [ERROR] 

Re: Web Service Appender

[Evan J]

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 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, 
>  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
>
>

RE: More maven build problems for log4j

[Gary Gregory]

What about mvn package?

Gary

 Original message From: 
walter_mar...@dellteam.com Date:05/01/2014  12:08  (GMT-05:00) 
To: log4j-user@logging.apache.org Subject: RE: More maven 
build problems for log4j 
Dell - Internal Use - Confidential
No custom  ~/.m2/settings.xml file that I know of

Build results=>

C:\Software\log4j2source\apache-log4j-2.0-rc1-src>mvn install
[INFO] Scanning for projects...
Downloading: 
https://repository.apache.org/content/repositories/releases/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.pom
[ERROR] The build could not read 7 projects -> [Help 1]
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-async:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project org.apache.logging.log4j.osgi:log4j-core-osgi-jpa:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project org.apache.logging.log4j.osgi:log4j-1.2-osgi-api:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-o
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project org.apache.logging.log4j.osgi:log4j-core-osgi-net:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-reduced:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\lo
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following

RE: More maven build problems for log4j

[Walter_Marvin]

Dell - Internal Use - Confidential
No custom  ~/.m2/settings.xml file that I know of

Build results=>

C:\Software\log4j2source\apache-log4j-2.0-rc1-src>mvn install
[INFO] Scanning for projects...
Downloading: 
https://repository.apache.org/content/repositories/releases/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/felix/maven-bundle-plugin/2.3.7/maven-bundle-plugin-2.3.7.pom
[ERROR] The build could not read 7 projects -> [Help 1]
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-async:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project org.apache.logging.log4j.osgi:log4j-core-osgi-jpa:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project org.apache.logging.log4j.osgi:log4j-1.2-osgi-api:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-o
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project org.apache.logging.log4j.osgi:log4j-core-osgi-net:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\log4j-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couchdb:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongodb:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR]   The project 
org.apache.logging.log4j.osgi:log4j-core-osgi-reduced:2.0-rc1 
(C:\Software\log4j2source\apache-log4j-2.0-rc1-src\lo
[ERROR] Unresolveable build extension: Plugin 
org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not 
be reso
gin:jar:2.3.7: Could not transfer artifact 
org.apache.felix:maven-bundle-plugin:pom:2.3.7 from/to apache 
(https://repository.apache.org/c
ry.apache.org/140.211.11.74] failed: Connection timed out: connect -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 28, column 14
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
C:\Software\log4j2source\

Re: Web Service Appender

[Ralph Goers]

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,  
 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

Re: Web Service Appender

[Ralph Goers]

Yes, persistent buffering can prevent the data loss but adds to the complexity. 
 The Flume Appender does that.

I will take a look at the scribe appender when I get a chance.

Ralph

On May 1, 2014, at 8:39 AM, Michael Wechner  wrote:

> Am 01.05.14 17:18, schrieb Ralph Goers:
>> I guarantee you, on a busy system with lots of logging sending a SOAP 
>> message for every event will be a problem. 
> 
> I can second/confirm that.
> 
> We have developed such an appender in order to log user requests for
> user tracking and personalization
> 
> https://github.com/wyona/yanel/blob/master/conf/log4j.properties
> 
> whereas see the boosthttp configuration
>> If they are being bundled so that multiple events are sent in each request 
>> that will perform better
> 
> yes, that's what we do
>> but could result in losing all the events that are buffered.
> 
> one can buffer them persistently, or do I misunderstand you?
> 
> I am not sure whether "refactoring"
> https://github.com/joshdevins/log4j-scribe-appender might make sense, but
> it probably makes sense to have a look at it.
> 
> HTH
> 
> Michael
>> 
>> Ralph
>> 
>> 
>> On May 1, 2014, at 7:26 AM, walter_mar...@dellteam.com wrote:
>> 
>>> Dell - Internal Use - Confidential
>>> Not necessarily. Remember that the people who read these logs are not in 
>>> the processing loop, and therefore do not slow down the process,
>>> What is required is an asynchronous thread or process to do the soap 
>>> transfer during off cycles, and storage to receive the messages from the
>>> Processing stream. Some sort of queuing and thread, or database storage 
>>> might be used.
>>> 
>>> -Original Message-
>>> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
>>> Sent: Wednesday, April 30, 2014 11:16 PM
>>> To: Log4J Users List
>>> Subject: Re: Web Service Appender
>>> 
>>> 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

RE: Web Service Appender

[Walter_Marvin]

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

Re: Web Service Appender

[Michael Wechner]

Am 01.05.14 17:18, schrieb Ralph Goers:
> I guarantee you, on a busy system with lots of logging sending a SOAP message 
> for every event will be a problem. 

I can second/confirm that.

We have developed such an appender in order to log user requests for
user tracking and personalization

https://github.com/wyona/yanel/blob/master/conf/log4j.properties

whereas see the boosthttp configuration
>  If they are being bundled so that multiple events are sent in each request 
> that will perform better

yes, that's what we do
>  but could result in losing all the events that are buffered.

one can buffer them persistently, or do I misunderstand you?

I am not sure whether "refactoring"
https://github.com/joshdevins/log4j-scribe-appender might make sense, but
it probably makes sense to have a look at it.

HTH

Michael
>
> Ralph
>
>
> On May 1, 2014, at 7:26 AM, walter_mar...@dellteam.com wrote:
>
>> Dell - Internal Use - Confidential
>> Not necessarily. Remember that the people who read these logs are not in the 
>> processing loop, and therefore do not slow down the process,
>> What is required is an asynchronous thread or process to do the soap 
>> transfer during off cycles, and storage to receive the messages from the
>> Processing stream. Some sort of queuing and thread, or database storage 
>> might be used.
>>
>> -Original Message-
>> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
>> Sent: Wednesday, April 30, 2014 11:16 PM
>> To: Log4J Users List
>> Subject: Re: Web Service Appender
>>
>> 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

RE: Web Service Appender

[Walter_Marvin]

Dell - Internal Use - Confidential
What is needed is not only bundling which is a form of buffering, but also 
process overlap so that the transfers are held up to a point where the 
processing is more quiet
And more cycles are available. Offloading to another processor using tux also 
accomplishes this. This buffering could involve a stop and wait type protocol 
with a retransmit feature. The transmit would have to be some form of permanent 
storage to do this. Queuing offers the opportunity to "bundle" in memory, but 
might result in message loss if some permanent storage is also not involved, 
when a process aborts.

-Original Message-
From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
Sent: Thursday, May 01, 2014 10:18 AM
To: Log4J Users List
Subject: Re: Web Service Appender

I guarantee you, on a busy system with lots of logging sending a SOAP message 
for every event will be a problem. If they are being bundled so that multiple 
events are sent in each request that will perform better but could result in 
losing all the events that are buffered.

Ralph


On May 1, 2014, at 7:26 AM, walter_mar...@dellteam.com wrote:

> Dell - Internal Use - Confidential
> Not necessarily. Remember that the people who read these logs are not
> in the processing loop, and therefore do not slow down the process,
> What is required is an asynchronous thread or process to do the soap transfer 
> during off cycles, and storage to receive the messages from the Processing 
> stream. Some sort of queuing and thread, or database storage might be used.
>
> -Original Message-
> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
> Sent: Wednesday, April 30, 2014 11:16 PM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> 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

Re: Web Service Appender

[Ralph Goers]

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

RE: Web Service Appender

[Walter_Marvin]

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

Re: Web Service Appender

[Ralph Goers]

I guarantee you, on a busy system with lots of logging sending a SOAP message 
for every event will be a problem.  If they are being bundled so that multiple 
events are sent in each request that will perform better but could result in 
losing all the events that are buffered.

Ralph


On May 1, 2014, at 7:26 AM, walter_mar...@dellteam.com wrote:

> Dell - Internal Use - Confidential
> Not necessarily. Remember that the people who read these logs are not in the 
> processing loop, and therefore do not slow down the process,
> What is required is an asynchronous thread or process to do the soap transfer 
> during off cycles, and storage to receive the messages from the
> Processing stream. Some sort of queuing and thread, or database storage might 
> be used.
> 
> -Original Message-
> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
> Sent: Wednesday, April 30, 2014 11:16 PM
> To: Log4J Users List
> Subject: Re: Web Service Appender
> 
> 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

Re: Web Service Appender

[Ralph Goers]

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

RE: Web Service Appender

[Walter_Marvin]

Dell - Internal Use - Confidential
There are several architectural options . The cleanest might be to make a 
custom appender, and then do the queue removal and transport with a thread 
within
Log4j itself. This has the advantage of not disturbing the current setup and 
interface for local logging for development, while still providing a "high 
speed" method for production logging. In this case JMS would not be used, 
rather internal java queuing could be used, and the results put to a database, 
ready to be retrieved by a servlet and rich faces client. We have the 
technology to do this, since I am about to demonstrate a debuggable log4j built 
from source code. At the point we modify log4j, we would of course have to 
bring it under configuration management. The main problems is that it is a bit 
of work, and we would have to determine the correct internal queue size so that 
bursts of logging could be accomplished without slowing down the main 
processes. The Idea is to overlap I/O and CPU intensive processing so as to 
make the OS process our data as efficiently as possible. To this end, the 
database load could be done on other processors, perhaps using tux.

Thanks

Walter

-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Thursday, May 01, 2014 9:28 AM
To: Log4J Users List
Subject: Re: Web Service Appender

So the app logs to JMS, not SOAP. Later you have something else that consumes 
the queue and calls the WS, but that would not be done by Log4j.
Or are you suggesting that Log4j should be able to consume from a Q and call a 
WS?

Gary


On Thu, May 1, 2014 at 10: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
> >
> >
>



--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with 
Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: More maven build problems for log4j

[Matt Sicker]

You couldn't build log4j 2.0? What version of Maven are you using? Are you
using a custom ~/.m2/settings.xml file?


On 1 May 2014 08:47,  wrote:

> Dell - Internal Use - Confidential
> Could not build clean target for 1.2.17, could not build install target
> for 2.0. In each case maven libraries could not be found.
>
> Thanks
>
> wALTER
>
>


-- 
Matt Sicker 

RE: Web Service Appender

[Walter_Marvin]

Dell - Internal Use - Confidential
Not necessarily. Remember that the people who read these logs are not in the 
processing loop, and therefore do not slow down the process,
What is required is an asynchronous thread or process to do the soap transfer 
during off cycles, and storage to receive the messages from the
Processing stream. Some sort of queuing and thread, or database storage might 
be used.

-Original Message-
From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
Sent: Wednesday, April 30, 2014 11:16 PM
To: Log4J Users List
Subject: Re: Web Service Appender

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

RE: Web Service Appender

[Walter_Marvin]

Dell - Internal Use - Confidential
Try this url

http://www.ibm.com/developerworks/library/ws-log4j/index.html

-Original Message-
From: Evan J [mailto:maps.this.addr...@gmail.com]
Sent: Wednesday, April 30, 2014 7:21 PM
To: log4j-user@logging.apache.org
Subject: Web Service Appender

I searched around, but I could not find an off-the-shelf Appender that sends 
logs to a web service. Is there any?

Re: Web Service Appender

[Gary Gregory]

So the app logs to JMS, not SOAP. Later you have something else that
consumes the queue and calls the WS, but that would not be done by Log4j.
Or are you suggesting that Log4j should be able to consume from a Q and
call a WS?

Gary


On Thu, May 1, 2014 at 10: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
> >
> >
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Web Service Appender

[Evan J]

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
>
>

More maven build problems for log4j

[Walter_Marvin]

Dell - Internal Use - Confidential
Could not build clean target for 1.2.17, could not build install target for 
2.0. In each case maven libraries could not be found.

Thanks

wALTER