You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Christopher Gross <co...@gmail.com> on 2012/03/13 20:40:34 UTC
Tomcat Logging Jarhell
Hi all.
I'm trying to utilize the common/lib and shared/lib directories on
Tomcat 5.5.25. I have a few separate apps that were each using many
of the same JAR files, so I have been moving them down to shared &
common lib (DB stuff went to common/lib, the apache commons modules &
others went to the shared/lib). I was doing testing as I went along
-- but I never went to look at the logfiles for my webapps. I'm now
noticing that they aren't getting anything anymore. I haven't changed
anything aside from moving the JARs around. I'm using the Apache
Log4j Logger in my classes.
I have:
shared/lib:
commons-logging-1.0.4.jar
commons-logging-api.jar
commons-logging.jar
common/lib:
apache-log4j-extras-1.0.jar
log4j-1.2.15.jar
each app has:
commons-logging-1.0.4.jar
commons-logging-api.jar
commons-logging.jar
I'd like to avoid rolling back to how everything was, with a lot of
repeated JAR files all over the place. Has anyone run into a similar
problem and found a decent solution?
Any help/tips are appreciated.
Thanks!
-- Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Christopher Gross <co...@gmail.com>.
Well, I think I'm just going to revert back -- was able to get one app
working correctly with having the commons & log4j in its WEB-INF/lib.
Thanks anyway!
-- Chris
On Tue, Mar 13, 2012 at 4:07 PM, Allen Reese <ar...@yahoo-inc.com> wrote:
> Oh you are right. I forgot that part.
>
> We have an ugly process that generates a log4j.xml that is used globally.
> All of the logs are globbed together into a giant mess.
>
> As far as build time, we use maven and provided scope to exclude it.
>
> And most people here run a single instance of a single app.
>
>
> --Allen
> Yahoo!, Inc.
>
>> -----Original Message-----
>> From: Christopher Gross [mailto:cogross@gmail.com]
>> Sent: Tuesday, March 13, 2012 1:01 PM
>> To: Tomcat Users List
>> Subject: Re: Tomcat Logging Jarhell
>>
>> http://publib.boulder.ibm.com/infocenter/initiate/v9r5/index.jsp?topic=
>> %2Fcom.ibm.inspinstall.doc%2Ftopics%2Ft_inspinstall_configuring_log4j_l
>> ogging_apachetomcat.html
>>
>> Having the logging items in the shared/lib means that the
>> shared/classes needs to have a log4j.properties file.
>>
>> I dropped one of my log4j.properties files into that directory, and I
>> was able to pipe log output there...anyone know how I can have a
>> separate one for each app, so that the logfiles will be readable and
>> not all mangled together? Outside of editing all the modules to use a
>> named logger...
>>
>> -- Chris
>>
>>
>>
>> On Tue, Mar 13, 2012 at 3:53 PM, Christopher Gross <co...@gmail.com>
>> wrote:
>> > Allen -- Is there something in particular that your users need to do
>> > for the common logging? Any changes in the file or the setup of
>> their
>> > web app?
>> >
>> > An example of the log4j.properties file from a WEB-INF/classes dir:
>> >
>> > log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
>> > log4j.appender.A1.layout=org.apache.log4j.PatternLayout
>> > log4j.appender.A1.layout.ConversionPattern=%d %-5p %c - %m%n
>> > log4j.appender.A1.File=/test/logs/app/console.log
>> >
>> > log4j.appender.AppAppender=org.apache.log4j.DailyRollingFileAppender
>> > log4j.appender.AppAppender.layout=org.apache.log4j.PatternLayout
>> > log4j.appender.AppAppender.layout.ConversionPattern=%d %-5p %c - %m%n
>> > log4j.appender.AppAppender.File=/test/logs/app/app.log
>> >
>> > log4j.rootLogger=WARN, A1
>> > log4j.logger.opensearch=DEBUG,AppAppender
>> >
>> > -- Chris
>> >
>> >
>> >
>> > On Tue, Mar 13, 2012 at 3:43 PM, Allen Reese <ar...@yahoo-inc.com>
>> wrote:
>> >> We have people exclude commons-logging, and log4j as our
>> installation provides them for you in a common lib dir.
>> >>
>> >> --Allen Reese
>> >> Yahoo!, Inc.
>> >>
>> >>> -----Original Message-----
>> >>> From: Christopher Gross [mailto:cogross@gmail.com]
>> >>> Sent: Tuesday, March 13, 2012 12:41 PM
>> >>> To: Tomcat Users List
>> >>> Subject: Tomcat Logging Jarhell
>> >>>
>> >>> Hi all.
>> >>>
>> >>> I'm trying to utilize the common/lib and shared/lib directories
>> on
>> >>> Tomcat 5.5.25. I have a few separate apps that were each using
>> many
>> >>> of the same JAR files, so I have been moving them down to shared &
>> >>> common lib (DB stuff went to common/lib, the apache commons modules
>> >>> & others went to the shared/lib). I was doing testing as I went
>> >>> along
>> >>> -- but I never went to look at the logfiles for my webapps. I'm
>> now
>> >>> noticing that they aren't getting anything anymore. I haven't
>> >>> changed anything aside from moving the JARs around. I'm using the
>> >>> Apache Log4j Logger in my classes.
>> >>>
>> >>> I have:
>> >>> shared/lib:
>> >>> commons-logging-1.0.4.jar
>> >>> commons-logging-api.jar
>> >>> commons-logging.jar
>> >>>
>> >>> common/lib:
>> >>> apache-log4j-extras-1.0.jar
>> >>> log4j-1.2.15.jar
>> >>>
>> >>> each app has:
>> >>> commons-logging-1.0.4.jar
>> >>> commons-logging-api.jar
>> >>> commons-logging.jar
>> >>>
>> >>> I'd like to avoid rolling back to how everything was, with a lot of
>> >>> repeated JAR files all over the place. Has anyone run into a
>> >>> similar problem and found a decent solution?
>> >>>
>> >>> Any help/tips are appreciated.
>> >>>
>> >>> Thanks!
>> >>>
>> >>> -- Chris
>> >>>
>> >>> -------------------------------------------------------------------
>> -
>> >>> - To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >>> For additional commands, e-mail: users-help@tomcat.apache.org
>> >>
>> >>
>> >> --------------------------------------------------------------------
>> -
>> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> For additional commands, e-mail: users-help@tomcat.apache.org
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat Logging Jarhell
Posted by Allen Reese <ar...@yahoo-inc.com>.
Oh you are right. I forgot that part.
We have an ugly process that generates a log4j.xml that is used globally.
All of the logs are globbed together into a giant mess.
As far as build time, we use maven and provided scope to exclude it.
And most people here run a single instance of a single app.
--Allen
Yahoo!, Inc.
> -----Original Message-----
> From: Christopher Gross [mailto:cogross@gmail.com]
> Sent: Tuesday, March 13, 2012 1:01 PM
> To: Tomcat Users List
> Subject: Re: Tomcat Logging Jarhell
>
> http://publib.boulder.ibm.com/infocenter/initiate/v9r5/index.jsp?topic=
> %2Fcom.ibm.inspinstall.doc%2Ftopics%2Ft_inspinstall_configuring_log4j_l
> ogging_apachetomcat.html
>
> Having the logging items in the shared/lib means that the
> shared/classes needs to have a log4j.properties file.
>
> I dropped one of my log4j.properties files into that directory, and I
> was able to pipe log output there...anyone know how I can have a
> separate one for each app, so that the logfiles will be readable and
> not all mangled together? Outside of editing all the modules to use a
> named logger...
>
> -- Chris
>
>
>
> On Tue, Mar 13, 2012 at 3:53 PM, Christopher Gross <co...@gmail.com>
> wrote:
> > Allen -- Is there something in particular that your users need to do
> > for the common logging? Any changes in the file or the setup of
> their
> > web app?
> >
> > An example of the log4j.properties file from a WEB-INF/classes dir:
> >
> > log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
> > log4j.appender.A1.layout=org.apache.log4j.PatternLayout
> > log4j.appender.A1.layout.ConversionPattern=%d %-5p %c - %m%n
> > log4j.appender.A1.File=/test/logs/app/console.log
> >
> > log4j.appender.AppAppender=org.apache.log4j.DailyRollingFileAppender
> > log4j.appender.AppAppender.layout=org.apache.log4j.PatternLayout
> > log4j.appender.AppAppender.layout.ConversionPattern=%d %-5p %c - %m%n
> > log4j.appender.AppAppender.File=/test/logs/app/app.log
> >
> > log4j.rootLogger=WARN, A1
> > log4j.logger.opensearch=DEBUG,AppAppender
> >
> > -- Chris
> >
> >
> >
> > On Tue, Mar 13, 2012 at 3:43 PM, Allen Reese <ar...@yahoo-inc.com>
> wrote:
> >> We have people exclude commons-logging, and log4j as our
> installation provides them for you in a common lib dir.
> >>
> >> --Allen Reese
> >> Yahoo!, Inc.
> >>
> >>> -----Original Message-----
> >>> From: Christopher Gross [mailto:cogross@gmail.com]
> >>> Sent: Tuesday, March 13, 2012 12:41 PM
> >>> To: Tomcat Users List
> >>> Subject: Tomcat Logging Jarhell
> >>>
> >>> Hi all.
> >>>
> >>> I'm trying to utilize the common/lib and shared/lib directories
> on
> >>> Tomcat 5.5.25. I have a few separate apps that were each using
> many
> >>> of the same JAR files, so I have been moving them down to shared &
> >>> common lib (DB stuff went to common/lib, the apache commons modules
> >>> & others went to the shared/lib). I was doing testing as I went
> >>> along
> >>> -- but I never went to look at the logfiles for my webapps. I'm
> now
> >>> noticing that they aren't getting anything anymore. I haven't
> >>> changed anything aside from moving the JARs around. I'm using the
> >>> Apache Log4j Logger in my classes.
> >>>
> >>> I have:
> >>> shared/lib:
> >>> commons-logging-1.0.4.jar
> >>> commons-logging-api.jar
> >>> commons-logging.jar
> >>>
> >>> common/lib:
> >>> apache-log4j-extras-1.0.jar
> >>> log4j-1.2.15.jar
> >>>
> >>> each app has:
> >>> commons-logging-1.0.4.jar
> >>> commons-logging-api.jar
> >>> commons-logging.jar
> >>>
> >>> I'd like to avoid rolling back to how everything was, with a lot of
> >>> repeated JAR files all over the place. Has anyone run into a
> >>> similar problem and found a decent solution?
> >>>
> >>> Any help/tips are appreciated.
> >>>
> >>> Thanks!
> >>>
> >>> -- Chris
> >>>
> >>> -------------------------------------------------------------------
> -
> >>> - To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >>> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >> --------------------------------------------------------------------
> -
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Christopher Gross <co...@gmail.com>.
http://publib.boulder.ibm.com/infocenter/initiate/v9r5/index.jsp?topic=%2Fcom.ibm.inspinstall.doc%2Ftopics%2Ft_inspinstall_configuring_log4j_logging_apachetomcat.html
Having the logging items in the shared/lib means that the
shared/classes needs to have a log4j.properties file.
I dropped one of my log4j.properties files into that directory, and I
was able to pipe log output there...anyone know how I can have a
separate one for each app, so that the logfiles will be readable and
not all mangled together? Outside of editing all the modules to use a
named logger...
-- Chris
On Tue, Mar 13, 2012 at 3:53 PM, Christopher Gross <co...@gmail.com> wrote:
> Allen -- Is there something in particular that your users need to do
> for the common logging? Any changes in the file or the setup of their
> web app?
>
> An example of the log4j.properties file from a WEB-INF/classes dir:
>
> log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
> log4j.appender.A1.layout=org.apache.log4j.PatternLayout
> log4j.appender.A1.layout.ConversionPattern=%d %-5p %c - %m%n
> log4j.appender.A1.File=/test/logs/app/console.log
>
> log4j.appender.AppAppender=org.apache.log4j.DailyRollingFileAppender
> log4j.appender.AppAppender.layout=org.apache.log4j.PatternLayout
> log4j.appender.AppAppender.layout.ConversionPattern=%d %-5p %c - %m%n
> log4j.appender.AppAppender.File=/test/logs/app/app.log
>
> log4j.rootLogger=WARN, A1
> log4j.logger.opensearch=DEBUG,AppAppender
>
> -- Chris
>
>
>
> On Tue, Mar 13, 2012 at 3:43 PM, Allen Reese <ar...@yahoo-inc.com> wrote:
>> We have people exclude commons-logging, and log4j as our installation provides them for you in a common lib dir.
>>
>> --Allen Reese
>> Yahoo!, Inc.
>>
>>> -----Original Message-----
>>> From: Christopher Gross [mailto:cogross@gmail.com]
>>> Sent: Tuesday, March 13, 2012 12:41 PM
>>> To: Tomcat Users List
>>> Subject: Tomcat Logging Jarhell
>>>
>>> Hi all.
>>>
>>> I'm trying to utilize the common/lib and shared/lib directories on
>>> Tomcat 5.5.25. I have a few separate apps that were each using many of
>>> the same JAR files, so I have been moving them down to shared & common
>>> lib (DB stuff went to common/lib, the apache commons modules & others
>>> went to the shared/lib). I was doing testing as I went along
>>> -- but I never went to look at the logfiles for my webapps. I'm now
>>> noticing that they aren't getting anything anymore. I haven't changed
>>> anything aside from moving the JARs around. I'm using the Apache Log4j
>>> Logger in my classes.
>>>
>>> I have:
>>> shared/lib:
>>> commons-logging-1.0.4.jar
>>> commons-logging-api.jar
>>> commons-logging.jar
>>>
>>> common/lib:
>>> apache-log4j-extras-1.0.jar
>>> log4j-1.2.15.jar
>>>
>>> each app has:
>>> commons-logging-1.0.4.jar
>>> commons-logging-api.jar
>>> commons-logging.jar
>>>
>>> I'd like to avoid rolling back to how everything was, with a lot of
>>> repeated JAR files all over the place. Has anyone run into a similar
>>> problem and found a decent solution?
>>>
>>> Any help/tips are appreciated.
>>>
>>> Thanks!
>>>
>>> -- Chris
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Christopher Gross <co...@gmail.com>.
Allen -- Is there something in particular that your users need to do
for the common logging? Any changes in the file or the setup of their
web app?
An example of the log4j.properties file from a WEB-INF/classes dir:
log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d %-5p %c - %m%n
log4j.appender.A1.File=/test/logs/app/console.log
log4j.appender.AppAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.AppAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.AppAppender.layout.ConversionPattern=%d %-5p %c - %m%n
log4j.appender.AppAppender.File=/test/logs/app/app.log
log4j.rootLogger=WARN, A1
log4j.logger.opensearch=DEBUG,AppAppender
-- Chris
On Tue, Mar 13, 2012 at 3:43 PM, Allen Reese <ar...@yahoo-inc.com> wrote:
> We have people exclude commons-logging, and log4j as our installation provides them for you in a common lib dir.
>
> --Allen Reese
> Yahoo!, Inc.
>
>> -----Original Message-----
>> From: Christopher Gross [mailto:cogross@gmail.com]
>> Sent: Tuesday, March 13, 2012 12:41 PM
>> To: Tomcat Users List
>> Subject: Tomcat Logging Jarhell
>>
>> Hi all.
>>
>> I'm trying to utilize the common/lib and shared/lib directories on
>> Tomcat 5.5.25. I have a few separate apps that were each using many of
>> the same JAR files, so I have been moving them down to shared & common
>> lib (DB stuff went to common/lib, the apache commons modules & others
>> went to the shared/lib). I was doing testing as I went along
>> -- but I never went to look at the logfiles for my webapps. I'm now
>> noticing that they aren't getting anything anymore. I haven't changed
>> anything aside from moving the JARs around. I'm using the Apache Log4j
>> Logger in my classes.
>>
>> I have:
>> shared/lib:
>> commons-logging-1.0.4.jar
>> commons-logging-api.jar
>> commons-logging.jar
>>
>> common/lib:
>> apache-log4j-extras-1.0.jar
>> log4j-1.2.15.jar
>>
>> each app has:
>> commons-logging-1.0.4.jar
>> commons-logging-api.jar
>> commons-logging.jar
>>
>> I'd like to avoid rolling back to how everything was, with a lot of
>> repeated JAR files all over the place. Has anyone run into a similar
>> problem and found a decent solution?
>>
>> Any help/tips are appreciated.
>>
>> Thanks!
>>
>> -- Chris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat Logging Jarhell
Posted by Allen Reese <ar...@yahoo-inc.com>.
We have people exclude commons-logging, and log4j as our installation provides them for you in a common lib dir.
--Allen Reese
Yahoo!, Inc.
> -----Original Message-----
> From: Christopher Gross [mailto:cogross@gmail.com]
> Sent: Tuesday, March 13, 2012 12:41 PM
> To: Tomcat Users List
> Subject: Tomcat Logging Jarhell
>
> Hi all.
>
> I'm trying to utilize the common/lib and shared/lib directories on
> Tomcat 5.5.25. I have a few separate apps that were each using many of
> the same JAR files, so I have been moving them down to shared & common
> lib (DB stuff went to common/lib, the apache commons modules & others
> went to the shared/lib). I was doing testing as I went along
> -- but I never went to look at the logfiles for my webapps. I'm now
> noticing that they aren't getting anything anymore. I haven't changed
> anything aside from moving the JARs around. I'm using the Apache Log4j
> Logger in my classes.
>
> I have:
> shared/lib:
> commons-logging-1.0.4.jar
> commons-logging-api.jar
> commons-logging.jar
>
> common/lib:
> apache-log4j-extras-1.0.jar
> log4j-1.2.15.jar
>
> each app has:
> commons-logging-1.0.4.jar
> commons-logging-api.jar
> commons-logging.jar
>
> I'd like to avoid rolling back to how everything was, with a lot of
> repeated JAR files all over the place. Has anyone run into a similar
> problem and found a decent solution?
>
> Any help/tips are appreciated.
>
> Thanks!
>
> -- Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Christopher Gross <co...@gmail.com>.
Correct -- a typo. WEB-INF/classes
-- Chris
On Wed, Mar 14, 2012 at 10:20 AM, Mark Thomas <ma...@apache.org> wrote:
> On 14/03/2012 14:04, Christopher Gross wrote:
>> After reverting -- all but one of my logs are working correctly. Each
>> web app has a log4j jar and the commons logging jars in its
>> WEB-INF/lib, and a log4j.properties in the WEB-INF/class. I didn't
>> change that file at all.
>>
>> Any ideas as to why the one set of log files aren't being written to?
>
> WEB-INF/classes vs. WEB-INF/class or was that just a typo?
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Mark Thomas <ma...@apache.org>.
On 14/03/2012 14:04, Christopher Gross wrote:
> After reverting -- all but one of my logs are working correctly. Each
> web app has a log4j jar and the commons logging jars in its
> WEB-INF/lib, and a log4j.properties in the WEB-INF/class. I didn't
> change that file at all.
>
> Any ideas as to why the one set of log files aren't being written to?
WEB-INF/classes vs. WEB-INF/class or was that just a typo?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Christopher Gross <co...@gmail.com>.
After reverting -- all but one of my logs are working correctly. Each
web app has a log4j jar and the commons logging jars in its
WEB-INF/lib, and a log4j.properties in the WEB-INF/class. I didn't
change that file at all.
Any ideas as to why the one set of log files aren't being written to?
-- Chris
On Wed, Mar 14, 2012 at 8:42 AM, Christopher Gross <co...@gmail.com> wrote:
> That section just gives some basic info, but nothing that tries to
> help with what I'm doing. I'm well aware what the directories are
> for.
>
> There are a lot of libraries that my apps have in common, and because
> of the nature of the project, I need to try to conserve space. By
> moving jars to a shared spot, I can trim off a decent amount of space.
>
> The individual app's code gets updated, but we rarely update the
> supporting jars, unless it is absolutely needed. It doesn't matter
> anyways, we can always drop a newer version of a supporting jar in the
> web app's WEB-INF/lib and it will be used before the others in
> common/lib or shared/lib get loaded. That's what the documentation
> says, anyway.
>
> 5.5.25 is our standard deployment. We haven't moved up, and perhaps
> later I'll do that. However, this same problem would arise,
> regardless of the version, and I was just trying to provide enough
> about my situation so that I could find appropriate assistance.
>
> While I can appreciate some constructive criticism, I'd rather have
> answers to my questions, as opposed to questions about my design.
>
> -- Chris
>
>
>
> On Tue, Mar 13, 2012 at 4:17 PM, Konstantin Kolinko
> <kn...@gmail.com> wrote:
>> 2012/3/13 Christopher Gross <co...@gmail.com>:
>>> Hi all.
>>>
>>> I'm trying to utilize the common/lib and shared/lib directories on
>>> Tomcat 5.5.25. I have a few separate apps that were each using many
>>> of the same JAR files, so I have been moving them down to shared &
>>> common lib (DB stuff went to common/lib, the apache commons modules &
>>> others went to the shared/lib). I was doing testing as I went along
>>> -- but I never went to look at the logfiles for my webapps. I'm now
>>> noticing that they aren't getting anything anymore. I haven't changed
>>> anything aside from moving the JARs around. I'm using the Apache
>>> Log4j Logger in my classes.
>>>
>>> I have:
>>> shared/lib:
>>> commons-logging-1.0.4.jar
>>> commons-logging-api.jar
>>> commons-logging.jar
>>>
>>> common/lib:
>>> apache-log4j-extras-1.0.jar
>>> log4j-1.2.15.jar
>>>
>>> each app has:
>>> commons-logging-1.0.4.jar
>>> commons-logging-api.jar
>>> commons-logging.jar
>>>
>>> I'd like to avoid rolling back to how everything was, with a lot of
>>> repeated JAR files all over the place. Has anyone run into a similar
>>> problem and found a decent solution?
>>>
>>
>> 1. You have to read "Class Loading" page of the user manual.
>>
>> Then I hope that you will note that it is a bad idea to move
>> everything into common/lib or shared/lib.
>>
>> 2. If you have foo-x.y.z in your libs folder that will impede your
>> efforts to upgrade some webapps to foo-y.z.w.
>>
>> Is is better to limit what you put into the common libs folder to
>> components that are needed by the server itself, like database
>> drivers.
>>
>> 3. Why are you investing your time in several-years-old 5.5.25, and
>> when the whole 5.5.x line is going to be abandoned in several months?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Christopher Gross <co...@gmail.com>.
That section just gives some basic info, but nothing that tries to
help with what I'm doing. I'm well aware what the directories are
for.
There are a lot of libraries that my apps have in common, and because
of the nature of the project, I need to try to conserve space. By
moving jars to a shared spot, I can trim off a decent amount of space.
The individual app's code gets updated, but we rarely update the
supporting jars, unless it is absolutely needed. It doesn't matter
anyways, we can always drop a newer version of a supporting jar in the
web app's WEB-INF/lib and it will be used before the others in
common/lib or shared/lib get loaded. That's what the documentation
says, anyway.
5.5.25 is our standard deployment. We haven't moved up, and perhaps
later I'll do that. However, this same problem would arise,
regardless of the version, and I was just trying to provide enough
about my situation so that I could find appropriate assistance.
While I can appreciate some constructive criticism, I'd rather have
answers to my questions, as opposed to questions about my design.
-- Chris
On Tue, Mar 13, 2012 at 4:17 PM, Konstantin Kolinko
<kn...@gmail.com> wrote:
> 2012/3/13 Christopher Gross <co...@gmail.com>:
>> Hi all.
>>
>> I'm trying to utilize the common/lib and shared/lib directories on
>> Tomcat 5.5.25. I have a few separate apps that were each using many
>> of the same JAR files, so I have been moving them down to shared &
>> common lib (DB stuff went to common/lib, the apache commons modules &
>> others went to the shared/lib). I was doing testing as I went along
>> -- but I never went to look at the logfiles for my webapps. I'm now
>> noticing that they aren't getting anything anymore. I haven't changed
>> anything aside from moving the JARs around. I'm using the Apache
>> Log4j Logger in my classes.
>>
>> I have:
>> shared/lib:
>> commons-logging-1.0.4.jar
>> commons-logging-api.jar
>> commons-logging.jar
>>
>> common/lib:
>> apache-log4j-extras-1.0.jar
>> log4j-1.2.15.jar
>>
>> each app has:
>> commons-logging-1.0.4.jar
>> commons-logging-api.jar
>> commons-logging.jar
>>
>> I'd like to avoid rolling back to how everything was, with a lot of
>> repeated JAR files all over the place. Has anyone run into a similar
>> problem and found a decent solution?
>>
>
> 1. You have to read "Class Loading" page of the user manual.
>
> Then I hope that you will note that it is a bad idea to move
> everything into common/lib or shared/lib.
>
> 2. If you have foo-x.y.z in your libs folder that will impede your
> efforts to upgrade some webapps to foo-y.z.w.
>
> Is is better to limit what you put into the common libs folder to
> components that are needed by the server itself, like database
> drivers.
>
> 3. Why are you investing your time in several-years-old 5.5.25, and
> when the whole 5.5.x line is going to be abandoned in several months?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Logging Jarhell
Posted by Konstantin Kolinko <kn...@gmail.com>.
2012/3/13 Christopher Gross <co...@gmail.com>:
> Hi all.
>
> I'm trying to utilize the common/lib and shared/lib directories on
> Tomcat 5.5.25. I have a few separate apps that were each using many
> of the same JAR files, so I have been moving them down to shared &
> common lib (DB stuff went to common/lib, the apache commons modules &
> others went to the shared/lib). I was doing testing as I went along
> -- but I never went to look at the logfiles for my webapps. I'm now
> noticing that they aren't getting anything anymore. I haven't changed
> anything aside from moving the JARs around. I'm using the Apache
> Log4j Logger in my classes.
>
> I have:
> shared/lib:
> commons-logging-1.0.4.jar
> commons-logging-api.jar
> commons-logging.jar
>
> common/lib:
> apache-log4j-extras-1.0.jar
> log4j-1.2.15.jar
>
> each app has:
> commons-logging-1.0.4.jar
> commons-logging-api.jar
> commons-logging.jar
>
> I'd like to avoid rolling back to how everything was, with a lot of
> repeated JAR files all over the place. Has anyone run into a similar
> problem and found a decent solution?
>
1. You have to read "Class Loading" page of the user manual.
Then I hope that you will note that it is a bad idea to move
everything into common/lib or shared/lib.
2. If you have foo-x.y.z in your libs folder that will impede your
efforts to upgrade some webapps to foo-y.z.w.
Is is better to limit what you put into the common libs folder to
components that are needed by the server itself, like database
drivers.
3. Why are you investing your time in several-years-old 5.5.25, and
when the whole 5.5.x line is going to be abandoned in several months?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org