tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumit D <>
Subject Re: Custom Valve
Date Tue, 07 Jul 2009 10:20:51 GMT
Hey Chris,

Thanks a lot for the detailed reply. At the moment, I have written a class
that extends
I deactivated the AccessLogValve from the server.xml and <Valve
className="my.Valve"> element to your <Engine> for this new Extended
Valve.(We wanted it at Engine level.)
Works completely fine!

Thanks for the clarification :) Its just that I had no idea about this
component when I started the internship.
Since I dont have a lot of time, I prefered to get some help on this
list.(Which I got! More than Enough actually)

I thank you and Chuck for that. hats off! honestly.
I just needed to create a simple Valve and see how to deploy it. (Like a
prototype to test what can be possible if we use the Valve component.)It was
pretty easy once I actually understood how to do it. Now I just need to call
an event and mount this "monitored info"

Thanks once again,


On Wed, Jul 1, 2009 at 2:35 PM, Christopher Schultz <> wrote:

> Hash: SHA1
> Sumit,
> On 7/1/2009 4:02 AM, Sumit D wrote:
> > - Extend the ValveBase class, Implement LifeCycle (not obligatory)
> > - write invoke method implementation
> > - compile and create its .jar file and put it in Catalina_Home/lib
> > - point it using the context.xml or server.xml (depending on the choice
> at
> > what [level] to implement the Valve)
> All looks correct.
> > @ Chris, Sorry but i dont quite understand what you meant by "Many of us
> get
> > paid for our software work..."
> I meant that nobody on this list is going to write your software for you
> unless you pay them. You can get help and tips, and maybe some working
> code, but at some point, you're going to have to do the work yourself.
> > Or if you can give me a really basic idea to write a very basic Valve ,
> that
> > would be great.
> The Valve code is easy (and you probably already have it written,
> compiled, and working). The hard part is designing the logging component
> that you mentioned in your original post. This is what I meant by
> "you're going to have to do the work yourself": you need to design your
> own "logging object" that consumes log messages and does something with
> them. We have no idea what that component should do and how it fits into
> your architecture.
> You seem to be asking for help to do something that is very unclear. I
> can think of many ways to write logging statements to
> files/databases/syslog/whatever but you've not really asked a specific
> question.
> You have basically asked "I want to write a logging valve, and I thought
> I'd start by extending AccessLogValve. Anyone have any ideas?!". This is
> not a very directed question. You aren't going to get very directed
> feedback (at least not from me).
> Posting your code would help. Describing what you think you might want
> to do with your code would help.
> - -chris
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla -
> iEYEARECAAYFAkpLWAEACgkQ9CaO5/Lv0PC+oACgr0Kt7m0OpYapM6wiSlztf8i5
> lToAn05E/obNNHvp+99OBdqIHvG22oMN
> =2CcI
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message