Re: Logging format (port %p)

Sorry, a bit searching revealed: /var/lib/tomcat9/server.xml: > Am 18.11.2023 um 14:48 schrieb Christoph Kukulies : > > I'm running tomcat9 as a backend server and I have configured different > ports. For debugging purposes I would like to log the port > a request is being sent through. > >

Re: Logging

Kevin, On 4/3/23 12:32, Kevin Huntly wrote: ok, can you tell me what your thoughts are? I'm always interested in new things I would recommend sending an alert to a realtime management system, if at all possible. There are no guarantees if the JVM experiences some trouble, but in my

Re: Logging

ok, can you tell me what your thoughts are? I'm always interested in new things Kevin Huntly Email: kmhun...@gmail.com Cell: 716/424-3311 -BEGIN GEEK CODE BLOCK- Version: 1.0 GCS/IT d+ s a

Re: Logging

Kevin, On 4/3/23 12:10, Kevin Huntly wrote: idk why i add the typeset, but I do everywhere just out of habit. i was trained that way many many moons ago. Is there anything else in my setenv that needs work? That mostly depends upon your environment. The only thing that stuck out to me was

Re: Logging

idk why i add the typeset, but I do everywhere just out of habit. i was trained that way many many moons ago. Is there anything else in my setenv that needs work? Kevin Huntly Email: kmhun...@gmail.com Cell: 716/424-3311

Re: Logging

Kevin, On 4/3/23 10:07, Kevin Huntly wrote: I'm launching with startup.sh and I have a setenv: https://pastebin.com/PKRgz2y1 > > typeset JAVA_OPTS="-Xms4096m -Xmx4096m -Dfile.encoding=utf-8 -Djava.awt.headless=true"; You don't want this. You want: typeset CATALINA_OPTS="-Xms4096m

Re: Logging

Kevin, On 4/3/23 10:07, Kevin Huntly wrote: I'm launching with startup.sh and I have a setenv: bin/startup.sh calls bin/catalina.sh. Have a look at the top few pages of catalina.sh to see what environment variables can be used to customize stuff like log file names.

Re: Logging

I'm launching with startup.sh and I have a setenv: https://pastebin.com/PKRgz2y1 Kevin Huntly Email: kmhun...@gmail.com Cell: 716/424-3311 -BEGIN GEEK CODE BLOCK- Version: 1.0 GCS/IT d+ s a

Re: Logging

Kevin, On 4/2/23 09:08, Kevin Huntly wrote: Couple questions: 1. Is there a way to change the default "stdout" to a different name? e.g. SystemOut.log (and by extension, can syserr be printed to something SystemErr.log?) How are you launching Tomcat? 2. When verbose:gc is turned on it logs

Re: Logging "location" header from the HTTP response

On Thu, May 26, 2022 at 11:37 AM Konstantin Kolinko wrote: > чт, 26 мая 2022 г. в 18:19, Robert Hicks : > > > > We would like to start logging the response location in Tomcat. I am not > > sure where to look something like that up. > > You are not mentioning the version number, but from other

Re: Logging "location" header from the HTTP response

чт, 26 мая 2022 г. в 18:19, Robert Hicks : > > We would like to start logging the response location in Tomcat. I am not > sure where to look something like that up. You are not mentioning the version number, but from other threads I assume that it is 9.0.x. Here:

Re: Logging Information when Tomcat reaches max thread limit

Hello Aquib, On Mon, Nov 2, 2020 at 10:09 AM Aquib Khan wrote: > > Hi, > > We have a usecase where we want that our application should indicate when it > reaches maximum thread limit. Our application is deployed in tomcat. Maximum > thread limit of tomcat is 200, so If 200 threads are

Re: Logging Rewrite Activity

Am 06.08.20 um 21:36 schrieb Jerry Malcolm: > How do configure TC to log the activities of the RewriteValve?  I added > > org.apache.catalina.valves.rewrite.RewriteValve.level = FINE > > to logging.properties.  But I'm not seeing any output related to > rewrite. Do I have the logging config

Re: Logging web applications with log4j 1.2

else have a suggestion? On 2/21/19, Thomas Rohde wrote: > Hi Chris, > > -Ursprüngliche Nachricht- > Von: Christopher Schultz [mailto:ch...@christopherschultz.net] > Gesendet: Mittwoch, 20. Februar 2019 16:41 > An: users@tomcat.apache.org > Betreff: Re: Logging web applic

Re: Logging web applications with log4j 1.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thomas, On 2/20/19 08:00, Thomas Rohde wrote: > I've some basic questions regarding the usage of log4j 1.2 in > Tomcat 8.5. > > We are running more than one web application in Tomcat. Each > application uses log4j via slf4j and ships the log4j.jar

Re: Logging web applications with log4j 1.2

I'm using 7.x still .. I put my log4j file in the classes folder of my web app. On 2/20/19, Thomas Rohde wrote: > Hi! > > I've some basic questions regarding the usage of log4j 1.2 in Tomcat 8.5. > > We are running more than one web application in Tomcat. Each application > uses log4j via slf4j

Re: Logging framework

Hi Mirunalini, Are you sure that the catalina.sh that you execute is actually picking up from the one that you have downloaded? Do you have any tomcat installed from other sources, such as from the centos 7.3? For a very long period of time, I have never seen Tomcat written as "jakarta-tomcat"

Re: Logging framework

Hi, This is how i guess tomcat starts, and also it uses the startup script with catalina.sh file. ps -ef | grep tomcat root 1357 1 0 11:53 ?00:00:08 /usr/local/thirdparty/java/jdk/bin/java -classpath

Re: Logging framework

2017-12-08 9:58 GMT+03:00 mirunalini Chandrasekaran : > Hi All, > > I am using Tomcat 7.0.81 on centos 7.3 and using openjdk 1.7.0.141. Tomcat > was downloaded from http://tomcat.apache.org/ > > The problem I am seeing recently is manager*.log and localhost*.log files > are not

Re: Logging framework !

2017-11-01 8:17 GMT+03:00 Utkarsh Dave : > Hi All, > > I am using Tomcat 7.0.81 on centos 7.2 and using openjdk 1.7.0.141. > The problem I am seeing recently is manager*.log and localhost*.log files > are not created. Instead, I see the messages that were to be written

Re: Logging framework !

On 01.11.2017 06:17, Utkarsh Dave wrote: Hi All, I am using Tomcat 7.0.81 on centos 7.2 and using openjdk 1.7.0.141. The problem I am seeing recently is manager*.log and localhost*.log files are not created. Instead, I see the messages that were to be written into, manager.log are going into

Re: Logging TLS Session Failures

Thanks, Will explore JSSE options. On Thu, Mar 9, 2017 at 7:18 PM, Jammy Chen wrote: > If you are using JSSE which you mentioned in earlier post, you probably can > only enable debug for all or specially one > -Djavax.net.debug=ssl:record or -Djavax.net.debug=ssl:handshake -

Re: Logging TLS Session Failures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Durga, On 3/9/17 3:34 AM, Durga Srinivasu Karuturi wrote: > This is one of the requirement from FIPS/CC certification. Can you provide a reference for this requirement? - -chris > On Wed, Mar 8, 2017 at 11:03 PM, Christopher Schultz < >

Re: Logging TLS Session Failures

If you are using JSSE which you mentioned in earlier post, you probably can only enable debug for all or specially one -Djavax.net.debug=ssl:record or -Djavax.net.debug=ssl:handshake - but it will log all sessions You could try to register a customized SSL socket factory in JSSE, you may extend

Re: Logging TLS Session Failures

Our application meaning on RHEL machine within JVM with embedded tomcat (with single web-app) Okay, tomcat may not have this information on handshake failures. I need to see little higher level for capturing these failures. Thanks for answers so far. Thanks, Durga Srinivasu On Thu, Mar 9,

Re: Logging TLS Session Failures

On 09.03.2017 09:34, Durga Srinivasu Karuturi wrote: This is one of the requirement from FIPS/CC certification. Thanks, Durga Srinivasu Durga, I believe that in your original post, you said : "We have a requirement in our application to log all TLS session failures." You should probably

Re: Logging TLS Session Failures

This is one of the requirement from FIPS/CC certification. Thanks, Durga Srinivasu On Wed, Mar 8, 2017 at 11:03 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Durga, > > On 3/8/17 10:02 AM, Durga Srinivasu Karuturi wrote: >

Re: Logging TLS Session Failures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Durga, On 3/8/17 10:02 AM, Durga Srinivasu Karuturi wrote: > We are using JSSE only not APR. Looking for handshake failures. > > Yes, using JSSE SSL debug, we are able to get all handshake > (-Djavax.net.debug=ssl:handshake) logs including

Re: Logging TLS Session Failures

Chris, We are using JSSE only not APR. Looking for handshake failures. Yes, using JSSE SSL debug, we are able to get all handshake (-Djavax.net.debug=ssl:handshake) logs including success cases. These are still quite bit expense logs and meant for debug purposes. As you said it might impact

Re: Logging TLS Session Failures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Durga, On 3/8/17 9:29 AM, Durga Srinivasu Karuturi wrote: > We have a requirement in our application to log all TLS session > failures. Specifically, what kind of failures? Failed handshakes? Initial or re-negotiation? Are you using JSSE or APR?

RE: logging to syslog

Yes, Its possible, using the below log4j configuration. http://jakarta.apache.org/log4j/;> --Chandra -Original Message- From: Schöke, Karsten

Re: logging to syslog

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Karsten, On 2/14/17 8:51 AM, Schöke, Karsten wrote: > Hello, > > it' possible that all messages in catalina.out also log to syslog? > I use tomcat7 under Debian Jessie. I think your best bet is to use log4j as your server logger and use their

Re: logging input and output HTTP message payload

Hi Christopher, On 06/18/2015 05:55 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frederik, On 6/17/15 8:10 AM, Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not easily. All you need is the server's TLS key and Wireshark will look

Re: logging input and output HTTP message payload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Milinda, On 6/17/15 5:10 AM, Milinda Perera wrote: I need to log HTTP payload content for debugging purposes. Following are my findings: 1. Using HTTP message content Access Log Valve [1] and Extended Access Log Valve [2] But it does not

Re: logging input and output HTTP message payload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frederik, On 6/17/15 8:10 AM, Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not easily. All you need is the server's TLS key and Wireshark will look directly at the HTTP conversation. This is a skill worth developing,

Re: logging input and output HTTP message payload

Some more info, On 06/18/2015 06:00 PM, Frederik Nosi wrote: Hi Christopher, On 06/18/2015 05:55 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frederik, On 6/17/15 8:10 AM, Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not

Re: logging input and output HTTP message payload

Hi all, Thanks for suggestions, Actually I want to log all HTTP / HTTPS requests from client applications to my Tomcat server and the Response sent back to the client. And logging requests and payloads are not target specific application running in the Tomcal server, which means all the request

Re: logging input and output HTTP message payload

If you have this: 1) Tomcat listening in HTTP, not HTTPS 2) ssh access to the machine 3) administrator access to the machine and are on Linux (or Unix in general, but my command is linux specific) do this as root: tcpdump -nnpi any -s0 -vvv -w /tmp/dump.pcap port 8080 After the request

Re: logging input and output HTTP message payload

Just to make sure.. Milinda Perera wrote: Hi all, Thanks for suggestions, Actually I want to log all HTTP / HTTPS requests from client applications to my Tomcat server and the Response sent back to the client. And logging requests and payloads are not target specific application running in

Re: logging input and output HTTP message payload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/17/2015 11:32 AM, André Warnier wrote: Just to make sure.. Milinda Perera wrote: Hi all, Thanks for suggestions, Actually I want to log all HTTP / HTTPS requests from client applications to my Tomcat server and the Response sent back

Re: logging input and output HTTP message payload

It helps only with HTTP though, no HTTPS or at least not easily. While we are at this, are you trying to debug a SOAP / REST connection from your application running on Tomcat to another server or a connection coming from outside to your Tomcat? On 06/17/2015 11:16 AM, Mark Thomas wrote:

Re: logging input and output HTTP message payload

Frederik Nosi wrote: It helps only with HTTP though, no HTTPS or at least not easily. While we are at this, are you trying to debug a SOAP / REST connection from your application running on Tomcat to another server or a connection coming from outside to your Tomcat? On 06/17/2015 11:16 AM,

Re: logging input and output HTTP message payload

On 17/06/2015 10:10, Milinda Perera wrote: Hi, I need to log HTTP payload content for debugging purposes. Use Wireshark. That has the added benefit of not having any unwanted side-effects on your application. Mark - To

RE: Logging Issue in Tomcat v7.0.0.32

We are using Windows version of tomcat on Windows 2008. -Original Message- From: Bomma, Nithun Sent: Tuesday, September 09, 2014 10:06 AM To: users@tomcat.apache.org Subject: Logging Issue in Tomcat v7.0.0.32 Hello, I have tried to login into Manger app using default user name

RE: Logging Issue in Tomcat v7.0.0.32

Hi Can you send your tomcat-users.xml. It has been changed and will not work if you are using the old format. BRLulseged From: nithun.bo...@amtrak.com To: users@tomcat.apache.org Subject: Logging Issue in Tomcat v7.0.0.32 Date: Tue, 9 Sep 2014 14:05:39 + Hello, I have tried to

RE: Logging Issue in Tomcat v7.0.0.32

- Information Technology (Operations) Desk: 215-349-2065; ATS: 728-2065 -Original Message- From: Lulseged Zerfu [mailto:zlulse...@hotmail.com] Sent: Tuesday, September 09, 2014 10:08 AM To: Tomcat Users List Subject: RE: Logging Issue in Tomcat v7.0.0.32 Hi Can you send your tomcat-users.xml

Re: Logging Issue in Tomcat v7.0.0.32

Hi. Sorry for top-posting, in this case it's easier to read. Bomma, Nithun wrote: The tomcat-users.xml is an XML file (as its name hints at). This is a valid XML comment : !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the

RE: Logging Issue in Tomcat v7.0.0.32

Thanks Andre! It got fixed. I have deleted them and restarted. Thanks again. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Tuesday, September 09, 2014 11:17 AM To: Tomcat Users List Subject: Re: Logging Issue in Tomcat v7.0.0.32 Hi. Sorry for top-posting

Re: Logging makes a grown man cry

Sorry if resurrecting the dead is frowned upon here but I thought I would just add my resolve to this. Honestly, after writing a lot of code otherwise, logging was probably the most frustrating. Tomcat 7.0.42, RHEL 6 1. SL4FJ with Logback works beautifully. 2. I have custom error pages in

Re: Logging makes a grown man cry

That seems like a good solution. Are you able to avoid having a single giant catalina.out file in $CATALINA_HOME/logs? On Tue, Dec 3, 2013 at 11:01 PM, Dale Ogilvie dale_ogil...@trimble.comwrote: Currently we use tomcat configured as out-of-the-box for logging (no log4j) and log4j.jar and

Re: Logging makes a grown man cry

I'd argue that dealing with logging configuration is not newbie stuff. This is probably some of the most poorly implemented technology in the servlet container. On Tue, Dec 3, 2013 at 3:44 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2013/12/3 Tomcat Random tomcat.ran...@gmail.com:

Re: Logging makes a grown man cry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 12/3/13, 1:12 PM, Tomcat Random wrote: I'm trying to implement log4j as per the instructions here (skipping step 5): http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j Since I'm not using the Manager, I've removed the

Re: Logging makes a grown man cry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 12/4/13, 11:31 AM, Tomcat Random wrote: I'd argue that dealing with logging configuration is not newbie stuff. This is probably some of the most poorly implemented technology in the servlet container. What about the implementation is

Re: Logging makes a grown man cry

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dale, On 12/3/13, 11:01 PM, Dale Ogilvie wrote: Currently we use tomcat configured as out-of-the-box for logging (no log4j) and log4j.jar and config in the app war file. We found issues with trying to have log4j in catalina/lib. That said,

Re: Logging makes a grown man cry

Chris, The examples don't meet your needs exactly? Well, I'm sure we're all terribly sorry about that. Heh...Sorry, I was responding to Konstantin's comment and mine crossed over just before your long and helpful reply. Thanks, as always, Alec On Wed, Dec 4, 2013 at 12:39 PM, Christopher

RE: Logging makes a grown man cry

Dale wrote: We found issues with trying to have log4j in catalina/lib. That said, it would be nice to use log4j for tomcat, however we found that the two configurations collided in our slf4j setup. You can do this if you put log4j.jar into a server-only ClassLoader. That's not configured

RE: Logging makes a grown man cry

Alec: That seems like a good solution. Are you able to avoid having a single giant catalina.out file in $CATALINA_HOME/logs? No, we find we can live with that but we try to minimise writes to stdout etc. From Chris's note it seems like the ideal solution for us would be 1. server log4j

Re: Logging Best Practices on RHEL

Chris, thanks. That's good to know since I just implemented 1.2.17. On Mon, Dec 2, 2013 at 5:27 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 12/2/13, 3:48 PM, Tomcat Random wrote: Thanks Chris, Are you using log4j

Re: Logging Best Practices on RHEL

2013/11/30 Christopher Schultz ch...@christopherschultz.net: On 11/27/13, 5:00 PM, Tomcat Random wrote: I find java.logging to be... frankly frustrating to configure. Totally agree, I feel like the Tomcat logging.properties file is weirdly clunky. Yes. That's because out of the box it uses

Re: Logging makes a grown man cry

2013/12/3 Tomcat Random tomcat.ran...@gmail.com: Environment is RHEL6, Tomcat 7.0.42. There is only one webapp. I'm trying to implement log4j as per the instructions here (skipping step 5): http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j Since I'm not using the Manager,

RE: Logging makes a grown man cry

Currently we use tomcat configured as out-of-the-box for logging (no log4j) and log4j.jar and config in the app war file. We found issues with trying to have log4j in catalina/lib. That said, it would be nice to use log4j for tomcat, however we found that the two configurations collided in our

Re: Logging Best Practices on RHEL

Thanks Chris, Are you using log4j 1.x or 2.beta? On Fri, Nov 29, 2013 at 6:06 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 5:00 PM, Tomcat Random wrote: Thanks Dave, I'll take a look at it. Chris,

Re: Logging Best Practices on RHEL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 12/2/13, 3:48 PM, Tomcat Random wrote: Thanks Chris, Are you using log4j 1.x or 2.beta? I've been using 1.x for quite a long time. I haven't looked much into the new version. I'd be surprised if it's a mind-blowing upgrade. :) - -chris

Re: Logging Best Practices on RHEL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 5:00 PM, Tomcat Random wrote: Thanks Dave, I'll take a look at it. Chris, thanks as well. Out of curiosity, do either of you know if/how you'd consolidate logging for things like say clustering. I have clustering configured

Re: Logging Best Practices on RHEL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 11:45 AM, Tomcat Random wrote: I'm running Tomcat 7.0.42 on RHEL. Currently all my exceptions are handled with e.printStackTrace() and go to catalina.out, which doesn't rotate. Yuk. Could someone be so kind as to

Re: Logging Best Practices on RHEL

Yes, Yuk indeed. So just to clarify, you recommend using log4j, and replacing all my printStackTrace with log4j specific code. Would that be correct? Cheers, Alec On Wed, Nov 27, 2013 at 12:18 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE-

Re: Logging Best Practices on RHEL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 12:35 PM, Tomcat Random wrote: Yes, Yuk indeed. So just to clarify, you recommend using log4j, and replacing all my printStackTrace with log4j specific code. Would that be correct? It's really a matter of personal

RE: Logging Best Practices on RHEL

We chose slf4j with log4j underneath. 1. slf4j has nice optimal syntax: Log.debug(The logged in user is {} {},firstName,lastName); http://www.slf4j.org/faq.html#logging_performance 2. It has bridging apis to route other logging frameworks. If you are using other libraries which use a different

Re: Logging Best Practices on RHEL

Thanks Dave, I'll take a look at it. Chris, thanks as well. Out of curiosity, do either of you know if/how you'd consolidate logging for things like say clustering. I have clustering configured for two physical servers each running an instance of tomcat. I have logging configured as per the

Re: Logging for session-replication debugging

On 8/26/2013 12:29 PM, Tomcat Random wrote: What exactly should go in logging.properties to get the most information about clustering/session replication? I see two different logging suggestions, one in the docs and one in the FAQ. Tried both but couldn't get anymore information that what's

Re: Logging for session-replication debugging

Thank you, works perfectly. On Mon, Aug 26, 2013 at 4:25 PM, Mark Eggers its_toas...@yahoo.com wrote: On 8/26/2013 12:29 PM, Tomcat Random wrote: What exactly should go in logging.properties to get the most information about clustering/session replication? I see two different logging

Re: Logging cookies in Tomcat 7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russ, On 11/26/12 1:27 PM, Russ Kepler wrote: I'm running Tomcat 7 with juli logging enabled and so I'm seeing the standard logfiles. In my access log I'm seeing the standard entries on each line and I'd like to see the cookies being passed as

Re: Logging cookies in Tomcat 7

On Monday, November 26, 2012 01:44:25 PM Christopher Schultz wrote: On 11/26/12 1:27 PM, Russ Kepler wrote: I'm running Tomcat 7 with juli logging enabled and so I'm seeing the standard logfiles. In my access log I'm seeing the standard entries on each line and I'd like to see the cookies

Re: Logging cookies in Tomcat 7

On Monday, November 26, 2012 12:05:45 PM Russ Kepler wrote: On Monday, November 26, 2012 01:44:25 PM Christopher Schultz wrote: On 11/26/12 1:27 PM, Russ Kepler wrote: I'm running Tomcat 7 with juli logging enabled and so I'm seeing the standard logfiles. In my access log I'm seeing the

Re: Logging cookies in Tomcat 7

2012/11/26 Russ Kepler r...@kepler-eng.com: On Monday, November 26, 2012 01:44:25 PM Christopher Schultz wrote: so if there doesn't seem to be a general print the cookies pattern. I see a %S and that seems to be printing You can print all cookies sent by the client with %{Cookie}i and new

Re: Logging of user's login attempts

Hi Mark. Thanks for the suggestion -- but I'm not getting the realm log file. That all looks like it should work, maybe there's just a little something that I'm missing. -- Chris On Thu, Nov 8, 2012 at 4:26 PM, Mark Eggers its_toas...@yahoo.com wrote: On 11/8/2012 12:29 PM, Christopher

Re: Logging of user's login attempts

On 11/9/2012 6:04 AM, Christopher Gross wrote: Hi Mark. Thanks for the suggestion -- but I'm not getting the realm log file. That all looks like it should work, maybe there's just a little something that I'm missing. -- Chris On Thu, Nov 8, 2012 at 4:26 PM, Mark Eggers its_toas...@yahoo.com

Re: Logging of user's login attempts

Mark, I already had it down to FINE, but I switched it to FINEST but I still didn't get the realm.date.txt file to show up. Perhaps the control lines (the ones with MESSAGES in them) aren't quite right for realm, but that's how your clustering setup works. Perhaps someone else who has done this

Re: Logging of user's login attempts

2012/11/9 Christopher Gross cogr...@gmail.com Perhaps someone else who has done this can chime in, but I'll keep looking around. I think you got me started on the right track. Well, I'm used to extending UserDatabaseRealm class and to configure Tomcat with it, so I can have more control

Re: Logging of user's login attempts

On 11/8/2012 12:29 PM, Christopher Gross wrote: Using Tomcat 6.0.36. Realm: Realm className=org.apache.catalina.realm.LockOutRealm failureCount=3 lockOutTime=30 Realm className=org.apache.catalina.realm.UserDatabaseRealm digest=SHA resourceName=UserDatabase / /Realm Is there a way that I

Re: Logging framework for Tomcat -Exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kiran, On 7/11/12 11:33 PM, Kiran Badi wrote: I know this is not a place to learn Java and thats not my intention.Its time for me to implement robust logging framework,so thought let me ask here as which is light weight and yet can log exceptions

Re: Logging framework for Tomcat -Exceptions

On Thu, 2012-07-12 at 06:35 +0530, Kiran Badi wrote: Hi, I have below code for catching DAO exceptions, No, it's not. It's code that defines an interface and a poorly implemented exception type. There's no catching. Anywhere. but I feel its not correct way to do this,Can some one point

Re: Logging framework for Tomcat -Exceptions

On 7/12/2012 7:20 AM, Tim Watts wrote: No offense, but this really isn't a list for teaching Java. But what the hell, I'll make one exception: public class DAOException extends Exception { public DAOException(String msg) { super(); } public

RE: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS

From: Alex Hooper [mailto:ahoo...@bmjgroup.com] Subject: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS With the software noted above Thanks for providing that. I get the following when starting tomcat and no logs other than catalina.are produced. Can't load

Re: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS

Caldarale, Charles R uttered: From: Alex Hooper [mailto:ahoo...@bmjgroup.com] Subject: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS With the software noted above Thanks for providing that. I get the following when starting tomcat and no logs other than

RE: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS

From: Alex Hooper [mailto:ahoo...@bmjgroup.com] Subject: Re: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS We've not modified it, though, so should be as per dist. It appears to be as you say. Looking at the stack trace a bit more

Re: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS

Caldarale, Charles R uttered: From: Alex Hooper [mailto:ahoo...@bmjgroup.com] Subject: Re: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu 10.04.3 LTS We've not modified it, though, so should be as per dist. It appears to be as you say. Looking at the stack trace a bit more

Re: [logging processes] Too many or Not too many?

On 02/18/2012 05:17 PM, Mark Thomas wrote: On 18/02/2012 21:57, Pae Choi wrote: Tomcat v7.0.25 CentOS 5.7 32bit Running the tomcat without any webapp deployed, the system shows about 38 processes(i think) related to logging. Why that many and what are they logging about? I see some of logging

Re: [logging processes] Too many or Not too many?

On 18/02/2012 21:57, Pae Choi wrote: Tomcat v7.0.25 CentOS 5.7 32bit Running the tomcat without any webapp deployed, the system shows about 38 processes(i think) related to logging. Why that many and what are they logging about? I see some of logging under the $CATALINA_HOME/logs folder

Re: Logging issue in Eclipse/WTP (disable request logging)

On 14/02/2012 21:49, Marcel Stör wrote: It seems nowadays you need a PHD just to understand Tomcat logging...sigh. In one of my Eclipse/WTP projects Tomcat logs each request (before and after): ... 13.02.2012 20:50:47 org.apache.catalina.core.ApplicationContext log INFO: After request

Re: Logging issue in Eclipse/WTP (disable request logging)

2012/2/15 Pid p...@pidster.com: On 14/02/2012 21:49, Marcel Stör wrote: It seems nowadays you need a PHD just to understand Tomcat logging...sigh. In one of my Eclipse/WTP projects Tomcat logs each request (before and after): ... 13.02.2012 20:50:47

Re: Logging issue in Eclipse/WTP (disable request logging)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marcel, On 2/14/12 4:49 PM, Marcel Stör wrote: It seems nowadays you need a PHD just to understand Tomcat logging...sigh. Does that mean that I can get an honorary PhD if I understand it? In one of my Eclipse/WTP projects Tomcat logs each

Re: Logging issue in Eclipse/WTP (disable request logging)

On 14.02.2012 22:57, Christopher Schultz wrote: In one of my Eclipse/WTP projects Tomcat logs each request (before and after): ... 13.02.2012 20:50:47 org.apache.catalina.core.ApplicationContext log INFO: After request [uri=/demo-webmvc-web/scripts/libs/jquery/jquery-1.6.4.min.js?null]

Re: Logging issue in Eclipse/WTP (disable request logging)

2012/2/15 Marcel Stör mar...@frightanic.com: On 14.02.2012 22:57, Christopher Schultz wrote: In one of my Eclipse/WTP projects Tomcat logs each request (before  and after):  ... 13.02.2012 20:50:47 org.apache.catalina.core.ApplicationContext  log INFO: After request  

Re: Logging per webapp per instance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon, On 12/21/11 2:55 AM, Simon wrote: It is not really a hack in log4j configuration to redirect the logs in stdout, as it is exactly what does the ConsoleAppender by default... True, log4j supports log-to-console. It's only a hack because of

Re: Logging per webapp per instance

Hi, I will use the variable substitution solution by changing the log4j.properties file : log4j.logFileSuffix=... log4j.appender.file.File=/var/log/webapp-${logSuffix}.log The value will be overriden by each instances with -Dlog4j.logFileSuffix=whatever Thank you for your help ! Regards,

Re: Logging per webapp per instance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon, On 12/19/11 11:54 AM, Simon wrote: log4j.appender.file.File=/var/log/webapp.log Thus, there is 3 identical webapps logging into the same log file simultaneously : It's more likely that the last one wins: the first 2 logs was probably

Re: Logging per webapp per instance

2011/12/20 Christopher Schultz ch...@christopherschultz.net: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon, On 12/19/11 11:54 AM, Simon wrote: log4j.appender.file.File=/var/log/webapp.log Thus, there is 3 identical webapps logging into the same log file simultaneously : It's more

Re: Logging per webapp per instance

2011/12/21 Konstantin Kolinko knst.koli...@gmail.com: 2011/12/20 Christopher Schultz ch...@christopherschultz.net: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon, On 12/19/11 11:54 AM, Simon wrote: log4j.appender.file.File=/var/log/webapp.log Thus, there is 3 identical webapps

Re: Logging per webapp per instance

Hello, you can specify the logoutput as relative path: instead of log4j.appender.file.File=/var/log/webapp.log to log4j.appender.file.File=logs/webapp.log and link the local file to the desired destination. regards Leon On Mon, Dec 19, 2011 at 5:54 PM, Simon spyd...@gmail.com wrote: Hi, Our

  1   2   3   4   5   >