Re: Logging.properties not found

2007-08-19 Thread Rainer Jung
Your assignment to JAVA_OPTS seems to consist of multiple lines. You 
need to end all apart from the last with a backslash "\", so that the 
shell executing the script understands, that the following lines still 
contain content for the variable.


The error doesn't say, that it can't file a config file, it tells us 
that the shell tried to execute a file named


-Djava.util.logging.config.file=/export/home/lakshmi/Tomcat/conf/logging.properties

which it couldn't find.

BTW: It's not the original shutdown script, so it's not a bug in Tomcat.

Regards,

Rainer

Lakshmi Venkataraman wrote:
 


We use Tomcat 5.5.23 on all platforms (Solaris, Linux and Win XP).
On Solaris, I see the following message when Tomcat is shutdown.
./shutdown.sh:
 
-Djava.util.logging.config.file=/export/home/lakshmi/Tomcat/conf/logging

.properties: not found

Here is an excerpt from the shutdown script:
-- BEGIN EXCERPT -
MAINCLASS=org.apache.catalina.startup.Bootstrap
export MAINCLASS
ACTION=stop
export ACTION

JAVA_OPTS=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogMana
ger
-Djava.util.logging.config.file="$CATALINA_BASE/conf/logging.properties"
export JAVA_OPTS

LD_LIBRARY_PATH=$CATALINA_HOME/bin:$CATALINA_HOME/libexec:$CATALINA_HOME
/conf:$LD_LIBRARY_PATH
export $LD_LIBRARY_PATH
PATH=$CATALINA_HOME/bin:$INM_HOME/bin:$CATALINA_HOME/conf:$PATH
export $PATH
CLASSPATH includes $CATALINA_HOME/conf/logging.properties

$JAVA_HOME/bin/java $JAVA_OPTS
-Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" -classpath "$CLASSPATH"
-Dcatalina.base="$CATALINA_BASE" -Dcatalina.home="$CATALINA_HOME"
-Djava.io.tmpdir="$CATALINA_TMPDIR" $MAINCLASS $ACTION

- END EXCERPT 
As you can see, $PATH, $LD_LIBRARY_PATH, $CLASSPATH all point to
$CATALINA_HOME/conf location.

Any clue why the message about logging.properties not being found is
printed?

Thanks
Lakshmi


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: logging.properties and Filter problem

2006-10-24 Thread Caldarale, Charles R
> From: Ronny Batty [mailto:[EMAIL PROTECTED] 
> Subject: logging.properties and Filter problem
>  
> The Filter is initialized and works as expected when using 
> Tomcat 5.5.17 on Windows 2K, my deployment on Linux using
> Tomcat 5.5.13 does not initialize the Filter

It would seem that moving up to a later level might be the first thing
to try.  No one's going to look at a problem not reproducible in the
current level.

> The only other difference apart from the OS and Tomcat 
> versions is the fact that the Linux deployment has more
> than one web context defined in server.xml.

You do realize that defining _any_  elements in server.xml is
strongly discouraged?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: logging.properties and Filter problem

2006-10-24 Thread Ronny Batty
Thanks for the response Chuck. I posted the question in the hope that it
might have been a configuration problem that someone else may have
experienced before. We have several sites happily running on 5.5.13 on Linux
and I would prefer not to upgrade the server and potentially introduce
different problems, if at all possible.

When I mentioned contexts we actually have several Host elements defined,
each with a single Context element, we have several domains all pointing to
the same server that each need their own webapps/ROOT.

-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
Sent: 24 October 2006 16:49
To: Tomcat Users List
Subject: RE: logging.properties and Filter problem

> From: Ronny Batty [mailto:[EMAIL PROTECTED]
> Subject: logging.properties and Filter problem
>  
> The Filter is initialized and works as expected when using Tomcat 
> 5.5.17 on Windows 2K, my deployment on Linux using Tomcat 5.5.13 does 
> not initialize the Filter

It would seem that moving up to a later level might be the first thing to
try.  No one's going to look at a problem not reproducible in the current
level.

> The only other difference apart from the OS and Tomcat versions is the 
> fact that the Linux deployment has more than one web context defined 
> in server.xml.

You do realize that defining _any_  elements in server.xml is
strongly discouraged?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
No virus found in this incoming message.
Checked by AVG.

 


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: logging.properties and Filter problem

2006-10-24 Thread Caldarale, Charles R
> From: Ronny Batty [mailto:[EMAIL PROTECTED] 
> Subject: RE: logging.properties and Filter problem
> 
> We have several sites happily running on 
> 5.5.13 on Linux and I would prefer not to
> upgrade the server and potentially introduce
> different problems, if at all possible.

It would still be worthwhile to try 5.5.17 (or 5.5.20) on a test Linux
box and see if the problem is resolved.

> When I mentioned contexts we actually have several Host 
> elements defined, each with a single Context element,
> we have several domains all pointing to the same server
> that each need their own webapps/ROOT.

You would normally do this with a separate appBase attribute for each
.  If you want to share the appBase, then you can put a separate
ROOT.xml file in conf/Catalina/[host] for each host you have defined.
The  element in each ROOT.xml would point to the appropriate
docBase for that host.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: logging.properties and Filter problem

2006-10-24 Thread Ronny Batty
Thanks for your help, everything is working fine now, I did a clean rebuild
of the entire webapp and that inadvertantly fixed the problem. I can only
guess that there was a synchronization issue between our staging and live
servers that resulted in the logging config files not being copied across
properly. Once again thanks for the assistance.

Ronny.
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
Sent: 24 October 2006 17:20
To: Tomcat Users List
Subject: RE: logging.properties and Filter problem

> From: Ronny Batty [mailto:[EMAIL PROTECTED]
> Subject: RE: logging.properties and Filter problem
> 
> We have several sites happily running on
> 5.5.13 on Linux and I would prefer not to upgrade the server and 
> potentially introduce different problems, if at all possible.

It would still be worthwhile to try 5.5.17 (or 5.5.20) on a test Linux box
and see if the problem is resolved.

> When I mentioned contexts we actually have several Host elements 
> defined, each with a single Context element, we have several domains 
> all pointing to the same server that each need their own webapps/ROOT.

You would normally do this with a separate appBase attribute for each
.  If you want to share the appBase, then you can put a separate
ROOT.xml file in conf/Catalina/[host] for each host you have defined.
The  element in each ROOT.xml would point to the appropriate
docBase for that host.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
No virus found in this incoming message.
Checked by AVG.

 


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]