manager webapp question
Hello, I have a tomcat server which serves some webapps for different purposes. I now would like to have another instance of the the manager webapp just for one of the webapps on this server, that another person can use the manager webapp to administer this one special webapp and not all the others, too. so I have normal /manager/html and I would like to have something like /web1/manager/html that is capable of adminstering web1 Can this be done? And if yes, what do I have to do? Regards, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manager webapp question
On Tue, Oct 11, 2005 at 04:00:24PM +0200, Marcus Franke wrote: Hello, I have a tomcat server which serves some webapps for different purposes. I now would like to have another instance of the the manager webapp just for one of the webapps on this server, that another person can use the manager webapp to administer this one special webapp and not all the others, too. so I have normal /manager/html and I would like to have something like /web1/manager/html that is capable of adminstering web1 Can this be done? And if yes, what do I have to do? Hmm, I guess I can answer that question by myself. If I use vhosts in tomcat and I have just the manager and the normal webapp in that one vhost will I see more than one webapp? And how do I secure access to that special vhosts manager webapp? As the normal tomcat-users.xml users with the manager role would be able to login into every manager on that tomcat server? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manager webapp question
On Tue, Oct 11, 2005 at 05:13:33PM +0200, Marcus Franke wrote: On Tue, Oct 11, 2005 at 04:00:24PM +0200, Marcus Franke wrote: Can this be done? And if yes, what do I have to do? Hmm, I guess I can answer that question by myself. If I use vhosts in tomcat and I have just the manager and the normal webapp in that one vhost will I see more than one webapp? Hmm, just tried the config on my local test server and only in the first host I can reach the /manager/html pages, in the second host I created there was no manager, just the one webapp I configured inside the host context.. Regards, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manager webapp question
On Tue, Oct 11, 2005 at 05:47:00PM +0200, Marcus Franke wrote: On Tue, Oct 11, 2005 at 05:13:33PM +0200, Marcus Franke wrote: On Tue, Oct 11, 2005 at 04:00:24PM +0200, Marcus Franke wrote: Can this be done? And if yes, what do I have to do? Hmm, I guess I can answer that question by myself. If I use vhosts in tomcat and I have just the manager and the normal webapp in that one vhost will I see more than one webapp? Hmm, just tried the config on my local test server and only in the first host I can reach the /manager/html pages, in the second host I created there was no manager, just the one webapp I configured inside the host context.. Ok, made a mistake, forgot to copy over the manager.xml file vom CATALINA_HOME/conf/Catalina/localhost/ to my new virtual host. Have now a manager webapp in both the default vhost localhost and my vhost test.local but both managers can see all installed webapps :( Did not expected to see them there.. Regards, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Turning on debugging in Tomcat 5.5
On Fri, Oct 07, 2005 at 09:28:23PM -0700, Bill Barker wrote:
James Rome [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Most of the installed Tomcat classes have something like
container.isDebugEnabled() {...}
How do I enable these debug statements in Tomcat 5.5?
I'll assume that you are using Juli. If you are using log4j, compare what
I'm saying to http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html
to see what you need to do.
First you edit $CATALINA_HOME/conf/logging.properties and add and something
like:
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myapp].level
= FINE
Would this control the logging of the tomcat server itsel, too?
Returning to my previous mail, if I activate connectionTimeout
in the asp13 connector tomcat starts to pollute my catalina.out
with messages about timedout connections.
I know that there are connections which tend to timeout, such is life,
but its a waste of time and storage when tomcat itself informs we
about that fact :)
Looking inside properties file I find the default log level and it
is:
# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers. For any given facility this global level
# can be overriden by a facility specific level
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level= INFO
So, I guess, if I use something like .level=WARN the pollution
of catalina.out may will stop?
Regards,
Marcus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Turning on debugging in Tomcat 5.5
On Mon, Oct 10, 2005 at 04:41:32PM +0200, Marcus Franke wrote: On Fri, Oct 07, 2005 at 09:28:23PM -0700, Bill Barker wrote: # Default global logging level. # This specifies which kinds of events are logged across # all loggers. For any given facility this global level # can be overriden by a facility specific level # Note that the ConsoleHandler also has a separate level # setting to limit messages printed to the console. .level= INFO So, I guess, if I use something like .level=WARN the pollution of catalina.out may will stop? Ok, had a deeper look inside the tomcat startup scripts on my RHEL box and catalina.out is written as a redirect of the tomcat stdout. So, my next guess is, java.util.logging.ConsoleHandler.level = INFO could be the right paramter to change? Sorry, it seems Im not as half as familliar with this stuff as I should be :( Marcus -- What terrible way to die. There are no good ways. -- Sulu and Kirk, That Which Survives, stardate unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Turning on debugging in Tomcat 5.5
On Mon, Oct 10, 2005 at 05:20:07PM +0200, Marcus Franke wrote: On Mon, Oct 10, 2005 at 04:41:32PM +0200, Marcus Franke wrote: On Fri, Oct 07, 2005 at 09:28:23PM -0700, Bill Barker wrote: # Default global logging level. # This specifies which kinds of events are logged across # all loggers. For any given facility this global level # can be overriden by a facility specific level # Note that the ConsoleHandler also has a separate level # setting to limit messages printed to the console. .level= INFO So, I guess, if I use something like .level=WARN the pollution of catalina.out may will stop? Ok, had a deeper look inside the tomcat startup scripts on my RHEL box and catalina.out is written as a redirect of the tomcat stdout. So, my next guess is, java.util.logging.ConsoleHandler.level = INFO could be the right paramter to change? oh no, neither of these points stops my tomcat from being extremly talkativ. Any other hints or suggestions how to silence the tomcat? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: silent install of Tomcat
On Mon, Oct 10, 2005 at 10:36:55AM -0700, krux mania wrote: Hi, I need to install tomcat 5.0.28 silently for my application. Can this be done. If this issue has been previously discussed please send me a pointer to the message. What do you mean with silent installation? Marcus -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, Day of the Dove, stardate unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: silent install of Tomcat
On Mon, Oct 10, 2005 at 11:11:30AM -0700, krux mania wrote: Hi Marcus, Silent installation also referred to as batch installation is the process where the install takes place without presenting any dialogs to the user. The user input is put into a properties file and the installation takes it from there. Sounds like you are using Windows? On my Linux boxes I installed quite silently using rpm and no questions to be answered.. But you could use the tarball/zip for it. Marcus -- There are some things worth dying for. -- Kirk, Errand of Mercy, stardate 3201.7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote: Jean-Marc, Actually, without the connectionTimeout set, jk seems to hold on to its connections indefinitely and after a while, the apache to tomcat connection hangs (pages quit serving). Could you tell me which combo of versions you use for apache, jk, and tomcat. I'm trying to figure out what is the correct configuration. Or if you have a link to a guide, I have yet to find a best practices. Out of curiosity I activated the connectionTimeout in my ajp connector and my catalina.out file gets spammed with hundreds of these: 07.10.2005 17:47:15 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:17 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached I guess, it is because of definition of debug=9 in the same Connector. What would be a reasonable debug level? Zero? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Thu, Oct 06, 2005 at 09:40:38AM -0700, Rick wrote: Thanks Jean-Marc, After checking over my workers.properties, orginally configured by someone else, it appears to be missing some of the connection timeout handling properties you have listed in yours. I'm guessing this is the root of my issue. I'll give them a try. Hmm, I guess its not only an issue of the mod_jk, as I restarted the apache server and still had sessions in the jk connector with an age of over 19 hours. Or am I missing something? Marcus -- Live long and prosper. -- Spock, Amok Time, stardate 3372.7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Fri, Oct 07, 2005 at 05:24:27PM +0100, Allistair Crossley wrote: Hi, looks like jk is using commons logging, you'll have better success using a log4j or commons-logging properties configuration to set the threshold to ERROR. you may be able to do that in jk's config files too, i am sure there is an error level setting. check out the jk docs. Hello Allistair, Ok, did not understand a word :) Seems to be too late. I now changed the debug value in the Connector now step by step down to Zero. But no changes, the catalina.out file still fills with those timeout Infos. !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector port=8009 enableLookups=false redirectPort=8443 debug=0 minProcessors=50 maxProcessors=500 connectionTimeout=2 protocol=AJP/1.3 / I tried to modify the logger definition in the server.xml using verbosity=0 !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt verbosity=0 timestamp=true/ But its just the catalina_log and not the catalina.out which according to the start scripts of the tomcat daemon is a redirection of stdout of the daemon itself into the logfile. Is there an option to make the tomcat daemon less noisy? Thanks, Marcus -- History tends to exaggerate. -- Col. Green, The Savage Curtain, stardate 5906.4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with tomcat configuration
On Thu, Oct 06, 2005 at 12:14:58AM -0700, Mark Eggers wrote: https is port 443. You need to to uncomment the HTTP 1.1 connector for 8443 and change the port to 443. Uncomment the following connector in server.xml: !-- Define a SSL HTTP/1.1 Connector on port 8443 -- !-- Connector port=8443 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=false sslProtocol=TLS / -- Change the port to 443. Read the documentation concerning the attributes (especially the sslProtocol and clientAuth). Maybe, but https ins predefined in your browser to use port 443, so if you use https://localhost/ you must ensure, that you have tomcat running on this special machine. Other question if I use apache with mod_jk and ajp13 connector like that: Connector port=8009 enableLookups=false redirectPort=8443 debug=9 minProcessors=50 maxProcessors=500 protocol=AJP/1.3 / then all https requests would be inside the tomcat service redirected to port 8443? browser-apache-via ajp13-tomcat(8009)-redirect-tomcat(8443) right? Marcus --- vineesh kumar [EMAIL PROTECTED] wrote: Hi all, I manged to configure https on tomcat 5.5.9 with a passord different than changeit. It's working.But i tried to configure https on port 80 (i am running tomcat as root user). but when i point the browser to the system like https://localhost/ I am getting an error indicating that connection refused by the https server, but if we pint the browser like https://localhost:80/ it's working fine. but i want it in the former way. How can i do that? regards vineesh __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, Day of the Dove, stardate unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Modjk and Tomcat 5.5.4 problem
On Wed, Oct 05, 2005 at 04:24:08PM -0700, Rick wrote: We had an issue where it seemed like it would crash using mod_jk, the trouble was the connections were not letting go. By default, I think the timeout is infinite, so after setting the property: connectionTimeout, in the server.xml's connector descriptor as follows, Connector port= protocol=AJP/1.3 connectionTimeout=6 .../ The old connections would get cleaned up and we stopped having problems, however, I'm not sure this was the correct way to do this, seems to work. Hi, but concerning to the documentation connectionTimeout is the amount of time between opening the session and receiving the URI to process. So your connector would wait 60 seconds for an empty request before it would cut off the connection. I for example have the interesting behaviour that I have idle connections running for hours and hours which I would like to end but do not know how. Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
limit tomcat threads lifetime
Hello, when I look in the manager/status page I sometimes see threads in status keep-alive that are very old, have atm some which are 70700177ms old, which is over 19 hours. These threads have no longer any connection to the apache server, which invoked them, as I restarted the responsible apache processes yesterday. Is there a timout configuration I can put in my server.xml to do so? I found some directives for mod_jk and workers.properties, but after restarting the apache service the connection is lost and the tomcat should timeout those threads himself. I checked the session timeout from manager/sessions?path=/ and it tells me that it is set to 30 minutes, but 19 hours for those threads is multiple times of 30 minutes. And these threads aren't reused for new connections, they stay and idle till I restart the tomcat service. Any hints or suggestions? Thanks in advance Marcus -- Punishment becomes ineffective after a certain point. Men become insensitive. -- Eneg, Patterns of Force, stardate 2534.7 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
