Deploying root context
Is there a way to use the Tomcat 5.5.9 manager to deploy a WAR file as the root context? If not, how to I munge the deployed web application to make it the root context? Bernie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Server Side include won't work from root context
I am trying to get server side includes to work across app contexts in Tomcat 5.5.4 My ROOT webapp has the file includer/do_include.shtml The content is: html head link rel =stylesheet type=text/css href=style.css /head body table style=color: #ff9900 tr tdh2This page shows the use of the SSI/h2/td /tr /table table style=border:1px solid; tr td !--#include virtual=/test/index.jsp -- /td /tr /table /body /html The application context test is deployed. If you type http://localhost:8080/test/, the content of index.jsp shows. Finally, SSI functionality has been turned on in TOMCAT_HOME/conf/web.xml: servlet servlet-namessi/servlet-name servlet-class org.apache.catalina.ssi.SSIServlet /servlet-class init-param param-namebuffered/param-name param-value1/param-value /init-param init-param param-namedebug/param-name param-value5/param-value /init-param init-param param-nameexpires/param-name param-value666/param-value /init-param init-param param-nameisVirtualWebappRelative/param-name param-value0/param-value /init-param load-on-startup4/load-on-startup /servlet and servlet-mapping servlet-namessi/servlet-name url-pattern*.shtml/url-pattern /servlet-mapping When I go try to do the Server include using http://localhost/includer/do_include.shtml, I get [an error occurred while processing this directive] SEVERE: ssi: #include--Couldn't include file: /test/index.jsp java.io.IOException: Couldn't get context for path: /test/index.jsp at org.apache.catalina.ssi.SSIServletExternalResolver.getServletContextAndPathFromVirtualPath(SSIServletExternal Resolver.java:273) at org.apache.catalina.ssi.SSIServletExternalResolver.getServletContextAndPath(SSIServletExternalResolver.java:3 17) at org.apache.catalina.ssi.SSIServletExternalResolver.getFileText(SSIServletExternalResolver.java:366) at org.apache.catalina.ssi.SSIMediator.getFileText(SSIMediator.java:154) at org.apache.catalina.ssi.SSIInclude.process(SSIInclude.java:40) at org.apache.catalina.ssi.SSIProcessor.process(SSIProcessor.java:145) at org.apache.catalina.ssi.SSIServlet.processSSI(SSIServlet.java:193) at org.apache.catalina.ssi.SSIServlet.requestHandler(SSIServlet.java:170) at org.apache.catalina.ssi.SSIServlet.doGet(SSIServlet.java:106) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:731) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) The include does work for files within the ROOT context, though Any tips on what's still wrong would be appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can't stop AJP Connector received URL's resolving relative to ROOT context
Please help, driving me mad. Tried hard to find help in archives and docs before resorting to asking here. Versions Server version: Apache/1.3.33 (Unix) mod_jk-1.2.6.so jakarta-tomcat-5.0.28 Problem: Tomcat always seems to resolve URLs coming in through a Coyote/JK2 AJP 1.3 Connector, configured to listen on port 8109, to the ROOT servlet context. The ex. URL: http://www.domain.com/raptor/tomcat-docs This was discovered by trussing the Tomcat JVM process:- /43:lwp_cond_wait(0x009DB680, 0x009DB668, 0x) = 0 /43:read(25, 12 401 00202\0\b H T T P.., 8192)= 308 /43: stat64(/opt/tomcat/jakarta-tomcat-5.0.28/webapps/ROOT/raptor/tomcat-doc s, 0xD137EEE0) Err#2 ENOENT /43: stat64(/opt/tomcat/raptor/jakarta-tomcat-5.0.28/webapps/ROOT/raptor/tom cat-docs, 0xD137E1A0) Err#2 ENOENT /43:send(25, A B\0 \040194\013 / r a.., 96, 0) = 96 /43:send(25, A B03F50303F1 h t m l.., 1017, 0) = 1017 /43:send(25, A B\0020501, 6, 0) = 6 Background Information: 1) Tomcat running behind Apache Web Server with correctly configured httpd.conf and workers.properties. eg. Httpd.conf LoadModule jk_module libexec/mod_jk-1.2.6.so IfModule mod_setenvif.c JkWorkersFile /opt/org/apache/conf/workers.properties jKLogFile /opt/org/apache/logs/jk_error_log JkLogLevel debug JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkMount /eagle/* eagle_ajp13 JkMount /raptor/* raptor_ajp13 /IfModule Workers.properties == worker.raptor_ajp13.port=8109 worker.raptor_ajp13.host=localhost worker.raptor_ajp13.type=ajp13 worker.raptor_ajp13.lbfactor=1 2) The actual Http connector is running on 8180 and resolves correctly using the URL http://localhost:8180/tomcat-docs on the machine itself. 3) There is another instance of Tomcat running behind this Apache configuration with the same Tomcat configuration but on standard distribution ports, 8080 and 8009 etc., for all connectors and that appears to work correctly. tia Paul Worrall Portal Technology and Innovation BECTA ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: Trying to retrieve the ROOT context in Servlet.
I'd want to say the Default context (see bug 33831 for more explanations) This is the tomcat behaviour if your put crossContext=true (but you already have solved your needs, no ?). On Tue, 8 Mar 2005 09:30:01 -0600 Jeffrey Lanham [EMAIL PROTECTED] wrote: So, hitting an invalid context gets you the root context? Isn't that a little insecure? Jeff -Original Message- From: Lionel Farbos [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 3:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Trying to retrieve the ROOT context in Servlet. Hi Jeffrey, I use Tomcat 5.0.30 and, when I use getServletContext().getContext(/toto), if the Context toto doesn't exist, it returns the root context. On Mon, 7 Mar 2005 15:32:25 -0600 Jeffrey Lanham [EMAIL PROTECTED] wrote: I have been trying for days and tons of google searches and mail archive searches and can't find an answer to the quandry I find myself in. I need to allow users to upload to a directory in the ROOT context of my tomcat server. For some reason, and it may be a security deal, I can't retrieve the server context for / so I can get the actual path to upload the file. It always comes back null. I know that the Java servlet specifications say the null may be returned if the container, for some reason, doesn't want to return the context. I don't know if it's a tomcat configuration, or if there is some other mechanism to use besides getServletContext().getContext(/). Any help would be appreciated. Thanks, Jeffrey Lanham Miller Curtain Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Trying to retrieve the ROOT context in Servlet.
So, it's not called the root context but the default context? And, yes, I did solve it with the crossContext attribute in the context.xml. Thanks for the suggestion. -Original Message- From: Lionel Farbos [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 09, 2005 3:43 AM To: [EMAIL PROTECTED] Cc: Tomcat Users List Subject: Re: Trying to retrieve the ROOT context in Servlet. I'd want to say the Default context (see bug 33831 for more explanations) This is the tomcat behaviour if your put crossContext=true (but you already have solved your needs, no ?). On Tue, 8 Mar 2005 09:30:01 -0600 Jeffrey Lanham [EMAIL PROTECTED] wrote: So, hitting an invalid context gets you the root context? Isn't that a little insecure? Jeff -Original Message- From: Lionel Farbos [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 3:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Trying to retrieve the ROOT context in Servlet. Hi Jeffrey, I use Tomcat 5.0.30 and, when I use getServletContext().getContext(/toto), if the Context toto doesn't exist, it returns the root context. On Mon, 7 Mar 2005 15:32:25 -0600 Jeffrey Lanham [EMAIL PROTECTED] wrote: I have been trying for days and tons of google searches and mail archive searches and can't find an answer to the quandry I find myself in. I need to allow users to upload to a directory in the ROOT context of my tomcat server. For some reason, and it may be a security deal, I can't retrieve the server context for / so I can get the actual path to upload the file. It always comes back null. I know that the Java servlet specifications say the null may be returned if the container, for some reason, doesn't want to return the context. I don't know if it's a tomcat configuration, or if there is some other mechanism to use besides getServletContext().getContext(/). Any help would be appreciated. Thanks, Jeffrey Lanham Miller Curtain Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to retrieve the ROOT context in Servlet.
Hi Jeffrey, I use Tomcat 5.0.30 and, when I use getServletContext().getContext(/toto), if the Context toto doesn't exist, it returns the root context. On Mon, 7 Mar 2005 15:32:25 -0600 Jeffrey Lanham [EMAIL PROTECTED] wrote: I have been trying for days and tons of google searches and mail archive searches and can't find an answer to the quandry I find myself in. I need to allow users to upload to a directory in the ROOT context of my tomcat server. For some reason, and it may be a security deal, I can't retrieve the server context for / so I can get the actual path to upload the file. It always comes back null. I know that the Java servlet specifications say the null may be returned if the container, for some reason, doesn't want to return the context. I don't know if it's a tomcat configuration, or if there is some other mechanism to use besides getServletContext().getContext(/). Any help would be appreciated. Thanks, Jeffrey Lanham Miller Curtain Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Trying to retrieve the ROOT context in Servlet.
So, hitting an invalid context gets you the root context? Isn't that a little insecure? Jeff -Original Message- From: Lionel Farbos [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 3:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Trying to retrieve the ROOT context in Servlet. Hi Jeffrey, I use Tomcat 5.0.30 and, when I use getServletContext().getContext(/toto), if the Context toto doesn't exist, it returns the root context. On Mon, 7 Mar 2005 15:32:25 -0600 Jeffrey Lanham [EMAIL PROTECTED] wrote: I have been trying for days and tons of google searches and mail archive searches and can't find an answer to the quandry I find myself in. I need to allow users to upload to a directory in the ROOT context of my tomcat server. For some reason, and it may be a security deal, I can't retrieve the server context for / so I can get the actual path to upload the file. It always comes back null. I know that the Java servlet specifications say the null may be returned if the container, for some reason, doesn't want to return the context. I don't know if it's a tomcat configuration, or if there is some other mechanism to use besides getServletContext().getContext(/). Any help would be appreciated. Thanks, Jeffrey Lanham Miller Curtain Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trying to retrieve the ROOT context in Servlet.
I have been trying for days and tons of google searches and mail archive searches and can't find an answer to the quandry I find myself in. I need to allow users to upload to a directory in the ROOT context of my tomcat server. For some reason, and it may be a security deal, I can't retrieve the server context for / so I can get the actual path to upload the file. It always comes back null. I know that the Java servlet specifications say the null may be returned if the container, for some reason, doesn't want to return the context. I don't know if it's a tomcat configuration, or if there is some other mechanism to use besides getServletContext().getContext(/). Any help would be appreciated. Thanks, Jeffrey Lanham Miller Curtain Company
RE: Trying to retrieve the ROOT context in Servlet.
Ok, if I could read I'd be dangerous. I finally found the crossContext attribute in the context descriptor. Man, I just glossed right over that one. Changed it in the web app accessing the root directory and voila, it works. Duh (dull slap as hand hits forhead with enough force to crack the skull). -Original Message- From: Jeffrey Lanham [mailto:[EMAIL PROTECTED] Sent: Monday, March 07, 2005 3:32 PM To: tomcat-user@jakarta.apache.org Subject: Trying to retrieve the ROOT context in Servlet. I have been trying for days and tons of google searches and mail archive searches and can't find an answer to the quandry I find myself in. I need to allow users to upload to a directory in the ROOT context of my tomcat server. For some reason, and it may be a security deal, I can't retrieve the server context for / so I can get the actual path to upload the file. It always comes back null. I know that the Java servlet specifications say the null may be returned if the container, for some reason, doesn't want to return the context. I don't know if it's a tomcat configuration, or if there is some other mechanism to use besides getServletContext().getContext(/). Any help would be appreciated. Thanks, Jeffrey Lanham Miller Curtain Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Root Context on Tomcat 5.5.7
I am trying to deploy a root context webapp using a war file. Anytime I try to deploy the war file (ROOT.war) it says it deployed successfully but then disappears from the manager. I can deploy it manually by copying the context.xml to 'conf/Catalina/localhost/ROOT.xml' and copying the web app files into 'webapps/ROOT'. I am including a copy of the context.xml and a snippet from the log file. Log file: Mar 3, 2005 12:29:42 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive ROOT.war Mar 3, 2005 12:29:42 PM org.apache.catalina.startup.ContextConfig applicationWebConfig INFO: Missing application web.xml, using defaults only StandardEngine[Catalina].StandardHost[localhost].StandardContext[] META-INF/context.xml file: ?xml version='1.0' encoding='utf-8'? Context path=/ docBase=C:/Program Files/Apache Software Foundation/Tomcat 5.5/webapps/ROOT ResourceLink name=jdbc/ssdb type=javax.sql.DataSource global=jdbc/ssdb/ /Context I know it says it's missing the web.xml but I know it is in the war archive in WEB-INF/web.xml Any ideas? Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Configuring dbcp in / ROOT context (tomcat 5.5.7)
Hi, I've searched the archives and generally on google, and whilst people see the problem a lot, I've not found a definitive answer for how to configure dbcp in the root context. E.g. In server.xml I have: Context path=/DBTest docBase=DBTest debug=5 reloadable=true crossContext=true Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=whatver password=whatver driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/ /Context If I copy this, and have it the same, except: Context path=/ docBase=ROOT debug=5 reloadable=true crossContext=true then it fails, with: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' How should I be configuring my postgress connection for use in the root context? Any help will be hugely appreciated, and will stop me from pulling any more of my hair out! Thanks, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Configuring dbcp in / ROOT context (tomcat 5.5.7)
Hi, Refer to the attached Readme.txt file and verify that you have done these steps. I think it should solve your problem. Have also attached the server.xml web.xml files which worked fine for us. let me know whether ur problem gets solved by this. -Original Message- From: Stuart Lewis [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 4:16 PM To: tomcat-user@jakarta.apache.org Subject: Configuring dbcp in / ROOT context (tomcat 5.5.7) Hi, I've searched the archives and generally on google, and whilst people see the problem a lot, I've not found a definitive answer for how to configure dbcp in the root context. E.g. In server.xml I have: Context path=/DBTest docBase=DBTest debug=5 reloadable=true crossContext=true Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=whatver password=whatver driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/ /Context If I copy this, and have it the same, except: Context path=/ docBase=ROOT debug=5 reloadable=true crossContext=true then it fails, with: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' How should I be configuring my postgress connection for use in the root context? Any help will be hugely appreciated, and will stop me from pulling any more of my hair out! Thanks, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://www.patni.com World-Wide Partnerships. World-Class Solutions. _ This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at [EMAIL PROTECTED] and delete this mail. _ !-- Example Server Configuration File -- !-- Note that component elements are nested corresponding to their parent-child relationships with each other -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- Comment these entries out to disable JMX MBeans support -- !-- You may also configure custom components (e.g. Valves/Realms) by including your own mbean-descriptor file(s), and setting the descriptors attribute to point to a ';' seperated list of paths (in the ClassLoader sense) of files to add to the default list. e.g. descriptors=/com/myfirm/mypackage/mbean-descriptor.xml -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ !-- Global JNDI resources -- GlobalNamingResources !-- Test entry for demonstration purposes -- Environment name=simpleValue type=java.lang.Integer value=30/ !-- Editable user database that can also be used by UserDatabaseRealm to authenticate users -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams !-- Defining the DataSource to be used for Tomcat connectionPooling -- /GlobalNamingResources !-- A Service is a collection of one or more Connectors that share a single Container (and therefore the web applications visible within that Container). Normally, that Container is an Engine, but this is not required. Note: A Service is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- !-- Define the Tomcat Stand-Alone Service -- Service name=Catalina
Re: Configuring dbcp in / ROOT context (tomcat 5.5.7)
Hello, please give follwing context definition a chance conf/Calalina/localhost/ROOT.xml Context reloadable=true crossContext=true Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=whatver password=whatver driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/ Context Your are sure that you copy the postgres jar at common/lib? Peter Stuart Lewis schrieb: Hi, I've searched the archives and generally on google, and whilst people see the problem a lot, I've not found a definitive answer for how to configure dbcp in the root context. E.g. In server.xml I have: Context path=/DBTest docBase=DBTest debug=5 reloadable=true crossContext=true Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=whatver password=whatver driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/ /Context If I copy this, and have it the same, except: Context path=/ docBase=ROOT debug=5 reloadable=true crossContext=true then it fails, with: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' How should I be configuring my postgress connection for use in the root context? Any help will be hugely appreciated, and will stop me from pulling any more of my hair out! Thanks, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuring dbcp in / ROOT context (tomcat 5.5.7)
You shouldn't be specifying the factory (this is a change from 5.0). It is implicit and may change under your nose anyway. If you are not using some custom factory that you are providing, let the container provide the default. Jake Quoting Peter Rossbach [EMAIL PROTECTED]: Hello, please give follwing context definition a chance conf/Calalina/localhost/ROOT.xml Context reloadable=true crossContext=true Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=whatver password=whatver driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/ Context Your are sure that you copy the postgres jar at common/lib? Peter Stuart Lewis schrieb: Hi, I've searched the archives and generally on google, and whilst people see the problem a lot, I've not found a definitive answer for how to configure dbcp in the root context. E.g. In server.xml I have: Context path=/DBTest docBase=DBTest debug=5 reloadable=true crossContext=true Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource maxActive=100 maxIdle=30 maxWait=1 username=whatver password=whatver driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/ /Context If I copy this, and have it the same, except: Context path=/ docBase=ROOT debug=5 reloadable=true crossContext=true then it fails, with: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' How should I be configuring my postgress connection for use in the root context? Any help will be hugely appreciated, and will stop me from pulling any more of my hair out! Thanks, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DELETED /ROOT CONTEXT PLEAS HELP!!!
Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DELETED /ROOT CONTEXT PLEAS HELP!!!
Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DELETED /ROOT CONTEXT PLEAS HELP!!!
You mean like this ??? Context path= docBase=$CATALINA_HOME/webapps/ROOT debug=0 reloadable=true crossContext=true privileged=true D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DELETED /ROOT CONTEXT PLEAS HELP!!!
Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DELETED /ROOT CONTEXT PLEAS HELP!!!
Is there still a ROOT folder underneath the webapps dir? But how did you delete it? Manually out of server.xml, undeployed in the manager app, stopped tomcat, and deleted the ROOT folder underneath webapps. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:07 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! You mean like this ??? Context path= docBase=$CATALINA_HOME/webapps/ROOT debug=0 reloadable=true crossContext=true privileged=true D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DELETED /ROOT CONTEXT PLEAS HELP!!!
So you undeployed using the manager app.. You'll have to restore the ROOT folder from a backup, I'm assuming this is your custom root web application, and not the default that came with tomcat. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:09 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DELETED /ROOT CONTEXT PLEAS HELP!!!
Yes, you are correct. No backup. but I do have a replicated directory on another installation of tomcat that I can copy over do you think that will work?? I really put my self in a jam NOW! D'Alessandro, Arthur wrote: So you undeployed using the manager app.. You'll have to restore the ROOT folder from a backup, I'm assuming this is your custom root web application, and not the default that came with tomcat. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:09 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DELETED /ROOT CONTEXT PLEAS HELP!!!
Yes, should work fine... If you copy/untar that replicated ROOT folder into webapps, it should auto-deploy (if so configured). Otherwise you can copy into the webapps folder, and use the deploy option. I'd make a tar backup of your tomcat folder just to be on the safe side, then try to deploy the replicated ROOT folder. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:18 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Yes, you are correct. No backup. but I do have a replicated directory on another installation of tomcat that I can copy over do you think that will work?? I really put my self in a jam NOW! D'Alessandro, Arthur wrote: So you undeployed using the manager app.. You'll have to restore the ROOT folder from a backup, I'm assuming this is your custom root web application, and not the default that came with tomcat. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:09 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DELETED /ROOT CONTEXT PLEAS HELP!!!
Umm I think you are out of luck. All sources gets completely erased when you use undeploy on the manager webapp. I have done it several times myself. Maybe there are some portions of it left over in the work/Catalina/localhost/yourwebapp/. --- D'Alessandro, Arthur Arthur.D'[EMAIL PROTECTED] wrote: So you undeployed using the manager app.. You'll have to restore the ROOT folder from a backup, I'm assuming this is your custom root web application, and not the default that came with tomcat. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:09 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DELETED /ROOT CONTEXT PLEAS HELP!!!
. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:09 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DELETED /ROOT CONTEXT PLEAS HELP!!!
: So you undeployed using the manager app.. You'll have to restore the ROOT folder from a backup, I'm assuming this is your custom root web application, and not the default that came with tomcat. -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:09 PM To: Tomcat Users List Subject: Re: DELETED /ROOT CONTEXT PLEAS HELP!!! Using the manerger I login and clicked on the remove button to delete the /ROOT Context ... D'Alessandro, Arthur wrote: Define deleted the /ROOT context... -Original Message- From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:01 PM To: Tomcat Users List Subject: DELETED /ROOT CONTEXT PLEAS HELP!!! Like a dummy I made the owfull mistake of deleting the /ROOT context I really need to restore it ASAP. Can someone please help me I have been here for three ours trying to fix this without reinstalling the whole thing. My config. is tomcat5.0.2x/ Apache 2 / mod_jk2 PLEASE HELP. -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
Funny where is the ROOT context the only context available is the one that I defined. I know that if I re-enable the Coyote HTTP/1.1 Connector and disable the Coyote/JK2 AJP 1.3 Connector then the ROOT context implicitly works otherwise it doesn't whe I try to bring it up in my URL (http://mydomain.com). Trying to make all the default tomcat applications work with Apache/Tomcat configuration, is harder then configuring tomcat and apapche together with mod_jk2!!! This so Funny I can't believe this is happening to me. Laconia Data Systems wrote: Dwayne- ROOT war files .war files with the name ROOT.war are given special treatment during deployment, when Tomcat detects and deploys the ROOT.war file instead of creating a web application mapped to (/warname).war it maps it to the root url (http://yourdomain.com/). However, because the root context is preconfigured within the server.xml above deploying a ROOT.war file will have no affect because a root context already exists. To deploy ROOT.war files, stop Tomcat, remove the root context and restart Tomcat. Martin Gainty - Original Message - From: Dwayne Ghant [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, December 09, 2004 3:56 PM Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Does anyone want to take shot at that question. I know it's simple but for some reason I seem to be having some kind of problem!!! PLEASE HELP. Dwayne Ghant wrote: I have successfully install both tomcat and apache. And they work find together. What I would like to do now is re-enable the ROOT context so I can view the ROOT applications. I have tried the code below (thinking that is all I would have to do), but it didn't work. Context path= docBase=ROOT debug=0 reloadable=true crossContext=true/ Could anyone take a shot at this . All I would like to do is be able to see the ROOT default applications in my URL (ex:http://localhost/). Thank you . -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
OR I could just make an NEW Host ex: Host name=www.mycompany.com ... ... Aliasmycompany.com/Alias ... /Host and build and explicit *|appBase|* to tomcat/webapps. What you think??? That would work the same?? Laconia Data Systems wrote: This from David Brown concerning ROOT.WAR the ROOT application context is actually a docBase defined in server.xml. and, this is the /examples webapp that lets u see the tc documentation and other usefull stuff online w/o directory references. in the long run u r much better off creating u own webapp .war and exanding it in ur own webapps directory. see the /examples build: ant and build.xml. i u r not already familiar w/ the java and tc way of building projects Accept that root.war belongs to and is part of Tomcat HTH Martin- - Original Message - From: Dwayne Ghant [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, December 10, 2004 11:22 AM Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Funny where is the ROOT context the only context available is the one that I defined. I know that if I re-enable the Coyote HTTP/1.1 Connector and disable the Coyote/JK2 AJP 1.3 Connector then the ROOT context implicitly works otherwise it doesn't whe I try to bring it up in my URL (http://mydomain.com). Trying to make all the default tomcat applications work with Apache/Tomcat configuration, is harder then configuring tomcat and apapche together with mod_jk2!!! This so Funny I can't believe this is happening to me. Laconia Data Systems wrote: Dwayne- ROOT war files .war files with the name ROOT.war are given special treatment during deployment, when Tomcat detects and deploys the ROOT.war file instead of creating a web application mapped to (/warname).war it maps it to the root url (http://yourdomain.com/). However, because the root context is preconfigured within the server.xml above deploying a ROOT.war file will have no affect because a root context already exists. To deploy ROOT.war files, stop Tomcat, remove the root context and restart Tomcat. Martin Gainty - Original Message - From: Dwayne Ghant [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, December 09, 2004 3:56 PM Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Does anyone want to take shot at that question. I know it's simple but for some reason I seem to be having some kind of problem!!! PLEASE HELP. Dwayne Ghant wrote: I have successfully install both tomcat and apache. And they work find together. What I would like to do now is re-enable the ROOT context so I can view the ROOT applications. I have tried the code below (thinking that is all I would have to do), but it didn't work. Context path= docBase=ROOT debug=0 reloadable=true crossContext=true/ Could anyone take a shot at this . All I would like to do is be able to see the ROOT default applications in my URL (ex:http://localhost/). Thank you . -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
This from David Brown concerning ROOT.WAR the ROOT application context is actually a docBase defined in server.xml. and, this is the /examples webapp that lets u see the tc documentation and other usefull stuff online w/o directory references. in the long run u r much better off creating u own webapp .war and exanding it in ur own webapps directory. see the /examples build: ant and build.xml. i u r not already familiar w/ the java and tc way of building projects Accept that root.war belongs to and is part of Tomcat HTH Martin- - Original Message - From: Dwayne Ghant [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, December 10, 2004 11:22 AM Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Funny where is the ROOT context the only context available is the one that I defined. I know that if I re-enable the Coyote HTTP/1.1 Connector and disable the Coyote/JK2 AJP 1.3 Connector then the ROOT context implicitly works otherwise it doesn't whe I try to bring it up in my URL (http://mydomain.com). Trying to make all the default tomcat applications work with Apache/Tomcat configuration, is harder then configuring tomcat and apapche together with mod_jk2!!! This so Funny I can't believe this is happening to me. Laconia Data Systems wrote: Dwayne- ROOT war files .war files with the name ROOT.war are given special treatment during deployment, when Tomcat detects and deploys the ROOT.war file instead of creating a web application mapped to (/warname).war it maps it to the root url (http://yourdomain.com/). However, because the root context is preconfigured within the server.xml above deploying a ROOT.war file will have no affect because a root context already exists. To deploy ROOT.war files, stop Tomcat, remove the root context and restart Tomcat. Martin Gainty - Original Message - From: Dwayne Ghant [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, December 09, 2004 3:56 PM Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Does anyone want to take shot at that question. I know it's simple but for some reason I seem to be having some kind of problem!!! PLEASE HELP. Dwayne Ghant wrote: I have successfully install both tomcat and apache. And they work find together. What I would like to do now is re-enable the ROOT context so I can view the ROOT applications. I have tried the code below (thinking that is all I would have to do), but it didn't work. Context path= docBase=ROOT debug=0 reloadable=true crossContext=true/ Could anyone take a shot at this . All I would like to do is be able to see the ROOT default applications in my URL (ex:http://localhost/). Thank you . -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
I have successfully install both tomcat and apache. And they work find together. What I would like to do now is re-enable the ROOT context so I can view the ROOT applications. I have tried the code below (thinking that is all I would have to do), but it didn't work. Context path= docBase=ROOT debug=0 reloadable=true crossContext=true/ Could anyone take a shot at this . All I would like to do is be able to see the ROOT default applications in my URL (ex:http://localhost/). Thank you . -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
Does anyone want to take shot at that question. I know it's simple but for some reason I seem to be having some kind of problem!!! PLEASE HELP. Dwayne Ghant wrote: I have successfully install both tomcat and apache. And they work find together. What I would like to do now is re-enable the ROOT context so I can view the ROOT applications. I have tried the code below (thinking that is all I would have to do), but it didn't work. Context path= docBase=ROOT debug=0 reloadable=true crossContext=true/ Could anyone take a shot at this . All I would like to do is be able to see the ROOT default applications in my URL (ex:http://localhost/). Thank you . -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
From: Dwayne Ghant [mailto:[EMAIL PROTECTED] Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Does anyone want to take shot at that question. I know it's simple but for some reason I seem to be having some kind of problem!!! Two things: 1) Make sure you don't have more than one context with path=. 2) Copy the context element from the Tomcat distribution rather than fiddling with a much-edited one. 3) [This must be the Spanish Inquisition sketch...] Try bypassing Apache by accesing the default app on port 8080. - 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 unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x
Dwayne- ROOT war files .war files with the name ROOT.war are given special treatment during deployment, when Tomcat detects and deploys the ROOT.war file instead of creating a web application mapped to (/warname).war it maps it to the root url (http://yourdomain.com/). However, because the root context is preconfigured within the server.xml above deploying a ROOT.war file will have no affect because a root context already exists. To deploy ROOT.war files, stop Tomcat, remove the root context and restart Tomcat. Martin Gainty - Original Message - From: Dwayne Ghant [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, December 09, 2004 3:56 PM Subject: Re: Enabling ROOT context for Tomcat5.0.28/Apache 2.0.x Does anyone want to take shot at that question. I know it's simple but for some reason I seem to be having some kind of problem!!! PLEASE HELP. Dwayne Ghant wrote: I have successfully install both tomcat and apache. And they work find together. What I would like to do now is re-enable the ROOT context so I can view the ROOT applications. I have tried the code below (thinking that is all I would have to do), but it didn't work. Context path= docBase=ROOT debug=0 reloadable=true crossContext=true/ Could anyone take a shot at this . All I would like to do is be able to see the ROOT default applications in my URL (ex:http://localhost/). Thank you . -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Won't deploy to root context even with Context path=?
Hi, Because you've probably left autoDeploy on for your Host. Yoav Shapira http://www.yoavshapira.com -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Ian Brandt Sent: Monday, December 06, 2004 7:14 PM To: [EMAIL PROTECTED] Subject: Won't deploy to root context even with Context path=? Hi, I'm running 5.0.28. I'm using the default $CATALINA_HOME/conf/server.xml. I have removed the ROOT and example webapps leaving only admin, manager (in server/webapps), and myapp (expanded into $CATALINA_HOME/webapps). In $CATALINA_HOME/conf/Catalina/localhost/myapp.xml I have specified my Context path=. When I start the server I get: INFO: Installing web application at context path /myapp from... I then also get the apparently infamous: [myapp] WARN [main] SettingsFactory.buildSettings(96) | Could not obtain connection metadata org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' When I change the Context path back to =myapp in myapp.xml the JDBC error goes away, so I'm assuming there's some sort of context mismatch when I specify but Tomcat deploys to /myapp anyway. So my question is why might Tomcat deploy my webapp to the context path /myapp as opposed to the root context when I specify path=? Thanks! Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Won't deploy to root context even with Context path=?
Hi Yoav, Thanks for the reply. I changed my server.xml as follows: Host name=localhost debug=9 appBase=webapps unpackWARs=true autoDeploy=false xmlValidation=false xmlNamespaceAware=false I restarted, but no change: Dec 7, 2004 7:56:37 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path /myapp from URL file:/Applications/jakarta-tomcat-5.0.28/webapps/myapp I searched but could not find any other Host declarations, nor any instances of 'autoDeploy' in my conf directory. I tried setting every instance of debug in server.xml to 9, but upon restart I'm not getting any more output in logs/catalina.out than I did with debug=0. I tried removing server.xml altogether to see if was being ignored for some reason, but then tomcat failed to start. Anything else I could try? Thanks Again, Ian Shapira, Yoav wrote: Hi, Because you've probably left autoDeploy on for your Host. Yoav Shapira http://www.yoavshapira.com -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Ian Brandt Sent: Monday, December 06, 2004 7:14 PM To: [EMAIL PROTECTED] Subject: Won't deploy to root context even with Context path=? Hi, I'm running 5.0.28. I'm using the default $CATALINA_HOME/conf/server.xml. I have removed the ROOT and example webapps leaving only admin, manager (in server/webapps), and myapp (expanded into $CATALINA_HOME/webapps). In $CATALINA_HOME/conf/Catalina/localhost/myapp.xml I have specified my Context path=. When I start the server I get: INFO: Installing web application at context path /myapp from... I then also get the apparently infamous: [myapp] WARN [main] SettingsFactory.buildSettings(96) | Could not obtain connection metadata org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' When I change the Context path back to =myapp in myapp.xml the JDBC error goes away, so I'm assuming there's some sort of context mismatch when I specify but Tomcat deploys to /myapp anyway. So my question is why might Tomcat deploy my webapp to the context path /myapp as opposed to the root context when I specify path=? Thanks! Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Won't deploy to root context even with Context path=?
More info and a solution: I tried 5.5.4 with similar results. I found that I could hit my app at http://localhost:8080/, and use database connectivity, but no matter what I still always got that error at startup. On a tip from the author of AppFuse I: mv $CATALINA_HOME/webapps/myapp $CATALINA_HOME/webapps/ROOT mv $CATALINA_HOME/conf/Catalina/localhost/myapp.xml $CATALINA_HOME/conf/Catalina/localhost/ROOT.xml Edited ROOT.xml setting docBase=ROOT (path= on 5.0.18, or removed completely on 5.5.4). That did the trick. Regards, Ian Ian Brandt wrote: Hi Yoav, Thanks for the reply. I changed my server.xml as follows: Host name=localhost debug=9 appBase=webapps unpackWARs=true autoDeploy=false xmlValidation=false xmlNamespaceAware=false I restarted, but no change: Dec 7, 2004 7:56:37 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path /myapp from URL file:/Applications/jakarta-tomcat-5.0.28/webapps/myapp I searched but could not find any other Host declarations, nor any instances of 'autoDeploy' in my conf directory. I tried setting every instance of debug in server.xml to 9, but upon restart I'm not getting any more output in logs/catalina.out than I did with debug=0. I tried removing server.xml altogether to see if was being ignored for some reason, but then tomcat failed to start. Anything else I could try? Thanks Again, Ian Shapira, Yoav wrote: Hi, Because you've probably left autoDeploy on for your Host. Yoav Shapira http://www.yoavshapira.com -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Ian Brandt Sent: Monday, December 06, 2004 7:14 PM To: [EMAIL PROTECTED] Subject: Won't deploy to root context even with Context path=? Hi, I'm running 5.0.28. I'm using the default $CATALINA_HOME/conf/server.xml. I have removed the ROOT and example webapps leaving only admin, manager (in server/webapps), and myapp (expanded into $CATALINA_HOME/webapps). In $CATALINA_HOME/conf/Catalina/localhost/myapp.xml I have specified my Context path=. When I start the server I get: INFO: Installing web application at context path /myapp from... I then also get the apparently infamous: [myapp] WARN [main] SettingsFactory.buildSettings(96) | Could not obtain connection metadata org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' When I change the Context path back to =myapp in myapp.xml the JDBC error goes away, so I'm assuming there's some sort of context mismatch when I specify but Tomcat deploys to /myapp anyway. So my question is why might Tomcat deploy my webapp to the context path /myapp as opposed to the root context when I specify path=? Thanks! Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Won't deploy to root context even with Context path=?
Hi, I'm running 5.0.28. I'm using the default $CATALINA_HOME/conf/server.xml. I have removed the ROOT and example webapps leaving only admin, manager (in server/webapps), and myapp (expanded into $CATALINA_HOME/webapps). In $CATALINA_HOME/conf/Catalina/localhost/myapp.xml I have specified my Context path=. When I start the server I get: INFO: Installing web application at context path /myapp from... I then also get the apparently infamous: [myapp] WARN [main] SettingsFactory.buildSettings(96) | Could not obtain connection metadata org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' When I change the Context path back to =myapp in myapp.xml the JDBC error goes away, so I'm assuming there's some sort of context mismatch when I specify but Tomcat deploys to /myapp anyway. So my question is why might Tomcat deploy my webapp to the context path /myapp as opposed to the root context when I specify path=? Thanks! Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: root context equivalent to another context?
Hi, Turn off autoDeploy in the Host element in server.xml. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Frank Morton [mailto:[EMAIL PROTECTED] Sent: Thursday, December 02, 2004 10:30 PM To: [EMAIL PROTECTED] Subject: root context equivalent to another context? I have a context currently defined in server.xml as: Context path=/mycity docBase=mycity debug=9 reloadable=true crossContext=true Loader checkInterval=5 / Logger className=org.apache.catalina.logger.SystemOutLogger timestamp=true / /Context It is deployed as a single war file mycity.war. This works fine. But, now I want the context created by this to be equivalent to the root context. I thought I could add: Context path= docBase=mycity debug=9 reloadable=true crossContext=true Loader checkInterval=5 / Logger className=org.apache.catalina.logger.SystemOutLogger timestamp=true / /Context And it does work since both are pointed at the same docBase, but it apparently creates two separate contexts. The same servlet will run init() each time it is first invoked in each context, which creates major problems for us. Anyone have any suggestions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
root context equivalent to another context?
I have a context currently defined in server.xml as: Context path=/mycity docBase=mycity debug=9 reloadable=true crossContext=true Loader checkInterval=5 / Logger className=org.apache.catalina.logger.SystemOutLogger timestamp=true / /Context It is deployed as a single war file mycity.war. This works fine. But, now I want the context created by this to be equivalent to the root context. I thought I could add: Context path= docBase=mycity debug=9 reloadable=true crossContext=true Loader checkInterval=5 / Logger className=org.apache.catalina.logger.SystemOutLogger timestamp=true / /Context And it does work since both are pointed at the same docBase, but it apparently creates two separate contexts. The same servlet will run init() each time it is first invoked in each context, which creates major problems for us. Anyone have any suggestions? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ROOT context using admin webapp
I sent this a wihle back and didn't get a response, so I'm going to try again. This applies to both Tomcat 5.0.25 and 5.0.27. Is it possible to add a ROOT context to a host using the administrative webapp? I know how to do it by editing the server.xml (or Catalina/host/context.xml) file, but with the admin webapp I can't get a valid ROOT context added. If I try to add the ROOT context with a blank path (). I get an error that the path must start with a slash (/). If I try to add the ROOT context with a single slash (/), all links and stylesheet/javascript includes contain a slash at the front of them, which causes many problems. When I look at the context.xml file, it seems as though the path gets written to the file as / instead of as as it should be for a ROOT context. I looked through bugzilla, and found this issue: http://issues.apache.org/bugzilla/show_bug.cgi?id=26399 The closing comment is very confusing to me though. It says that management tools will refer to ROOT contexts as /. It also says that internally (and the xml config files count as internal) ROOT contexts will be referred to as . He concludes by saying this is not a bug anyway Now to me this seems like a bug - I am attempting to add a ROOT context using /, and it gets added in server.xml as / instead of as . I'm hoping that I am just doing something wrong and there is no bug - so, does anybody know how to add a ROOT context to a host using the administrative webapp? Thanks, Matt Bathje - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
adding root context with admin webapp
Hi all. This message applies to tomcat 5.0.25 and tomcat 5.0.27. Is it possible to add a root context with the admin webapp? I try to add it with a single slash (/) but when I do, my whole site gets messed up with a slash at the front of all style sheets, images and links. You can't add the root context as blank () through the admin webapp. Looking at the context xml file, it seems as though when added with a slash (/) the context is created with the path as / instead of as . I looked through bugzilla, and found this: http://issues.apache.org/bugzilla/show_bug.cgi?id=26399 The message left is very confusing - it says that the root context will be displayed as / in manager apps, but as internally and in server.xml - which is fine - but it also says there is no bug (with creating root contexts?) Anyway - I haven't been able to figure out how to do this. Could someone please let me know if there is a way? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: adding root context with admin webapp
Example:
Context path= docBase=C:\Projects\myapp\docroot debug=99
/Context
Also, I use deployOnStartup=false in my Host. Keep in mind that
this used to be called autoDeploy and due to some left-over stuff the
setting autoDeploy still pops up in the Host if you use the admin
interface (I just keep both of them in there). This setting
(autoDeploy/deployOnStartup) prevents web apps from loading that don't
have an explicit Context defined in either the server.xml or
(preferably) a myapp.xml file under
${CATALINA_HOME}/conf/Catalina/localhost (or actually
${CATALINA_HOME}/conf/${name attribute of Service element}/${name
attribute of Host element})... Example:
Host name=localhost debug=0 appBase=webapps
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false
Anyway, this will prevent the app under ${CATALINA_HOME}/webapps/ROOT
from auto-loading. Alternately, you can just delete the damn ROOT app.
Sorry for the long explanation, I think it's cleaner to explicitly
declare your app personally with the whole Context thing.
Daniel
-Original Message-
From: Matt Bathje [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 26, 2004 5:05 PM
To: Tomcat Users List
Subject: adding root context with admin webapp
Hi all.
This message applies to tomcat 5.0.25 and tomcat 5.0.27.
Is it possible to add a root context with the admin webapp? I try to add
it with a single slash (/) but when I do, my whole site gets messed up
with a slash at the front of all style sheets, images and links. You
can't add the root context as blank () through the admin webapp.
Looking at the context xml file, it seems as though when added with a
slash (/) the context is created with the path as / instead of as
.
I looked through bugzilla, and found this:
http://issues.apache.org/bugzilla/show_bug.cgi?id=26399
The message left is very confusing - it says that the root context will
be displayed as / in manager apps, but as internally and in
server.xml - which is fine - but it also says there is no bug (with
creating root contexts?)
Anyway - I haven't been able to figure out how to do this. Could someone
please let me know if there is a way?
Thanks,
Matt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
will ROOT (/) context, folder hello interfere with context (hello) ?
Something just popped in my mind. If you have a ROOT context which has a folder named hello, And you have a context named hello When you request localhost:8080/hello/ Which one are you gonna get? The ROOT context or the hello context? I will try this out tomorrow, but I wonder how tomcat handles this? Best Regards, Ivan V. Jouikov (206) 228-6670 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004
RE: will ROOT (/) context, folder hello interfere with context (hello) ?
You'd get the hello context. -Original Message- From: Ivan Jouikov [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 3:37 AM To: 'Tomcat Users List' Subject: will ROOT (/) context, folder hello interfere with context (hello) ? Something just popped in my mind. If you have a ROOT context which has a folder named hello, And you have a context named hello When you request localhost:8080/hello/ Which one are you gonna get? The ROOT context or the hello context? I will try this out tomorrow, but I wonder how tomcat handles this? _ Best Regards, Ivan V. Jouikov (206) 228-6670 http://www.ablogic.net/ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004
RE: will ROOT (/) context, folder hello interfere with context (hello) ?
Then what about ROOT/hello ? How do you get to there? -Original Message- From: Mike Curwen [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 8:19 AM To: 'Tomcat Users List' Subject: RE: will ROOT (/) context, folder hello interfere with context (hello) ? You'd get the hello context. -Original Message- From: Ivan Jouikov [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 3:37 AM To: 'Tomcat Users List' Subject: will ROOT (/) context, folder hello interfere with context (hello) ? Something just popped in my mind. If you have a ROOT context which has a folder named hello, And you have a context named hello When you request localhost:8080/hello/ Which one are you gonna get? The ROOT context or the hello context? I will try this out tomorrow, but I wonder how tomcat handles this? _ Best Regards, Ivan V. Jouikov (206) 228-6670 http://www.ablogic.net/ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: will ROOT (/) context, folder hello interfere with context (hello) ?
It's genally a good idea to use the ROOT context as merely a redirection feature, _especially_ if you've got any possibility of naming conflicts (like you're suggesting). By this, I mean make your ROOT context simply do a redirect (either an HTTP redirect or a JSP/Servlet redirect, depending on what you need to accomplish) to your real default web application. It will eliminate problems like this -- naming and implementation/function should be independent. As for your question, you can't practically get to ROOT/hello in the case you're describing. justin At 12:47 PM 7/9/2004, you wrote: Then what about ROOT/hello ? How do you get to there? -Original Message- From: Mike Curwen [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 8:19 AM To: 'Tomcat Users List' Subject: RE: will ROOT (/) context, folder hello interfere with context (hello) ? You'd get the hello context. -Original Message- From: Ivan Jouikov [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 3:37 AM To: 'Tomcat Users List' Subject: will ROOT (/) context, folder hello interfere with context (hello) ? Something just popped in my mind. If you have a ROOT context which has a folder named hello, And you have a context named hello When you request localhost:8080/hello/ Which one are you gonna get? The ROOT context or the hello context? I will try this out tomorrow, but I wonder how tomcat handles this? _ Best Regards, Ivan V. Jouikov (206) 228-6670 http://www.ablogic.net/ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.716 / Virus Database: 472 - Release Date: 05.07.2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential. See: http://www.nextengine.com/confidentiality.php __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deployment to ROOT context
Hello all. I have such problem: I'm working on some web-application and I need my servlet change default servlet. So I'm publishing my web-application to default (ROOT) context (/). I'm using NetBeans 3.6 and tomcat 5.0.19. When I try to deploy my web-application automatically I'm getting strange problems like: No context exists for path / or IllegalStateException: Container StandardContext[] has not been started. I will appreciate any help. On Wednesday 16 June 2004 17:04, [EMAIL PROTECTED] wrote: Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Acknowledgment: I have added the address [EMAIL PROTECTED] to the tomcat-user mailing list. Welcome to [EMAIL PROTECTED] Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address. --- Administrative commands for the tomcat-user list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: [EMAIL PROTECTED] To remove your address from the list, send a message to: [EMAIL PROTECTED] Send mail to the following for info and FAQ for this list: [EMAIL PROTECTED] [EMAIL PROTECTED] Similar addresses exist for the digest list: [EMAIL PROTECTED] [EMAIL PROTECTED] To get messages 123 through 145 (a maximum of 100 per request), mail: [EMAIL PROTECTED] To get an index with subject and author for messages 123-456 , mail: [EMAIL PROTECTED] They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: [EMAIL PROTECTED] The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example [EMAIL PROTECTED], just add a hyphen and your address (with '=' instead of '@') after the command word: [EMAIL PROTECTED] To stop subscription for this address, mail: [EMAIL PROTECTED] In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: [EMAIL PROTECTED] Received: (qmail 5210 invoked by uid 99); 16 Jun 2004 14:04:43 - Received: from [217.196.165.116] (HELO marlboro.softsky.com.ua) (217.196.165.116) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 16 Jun 2004 07:04:43 -0700 Received: from trussardi.softsky.com.ua (trussardi.softsky.com.ua [192.168.0.3]) by marlboro.softsky.com.ua (Postfix) with ESMTP id C325B48E8 for [EMAIL PROTECTED] a.apache.org; Wed, 16 Jun 2004 16:42:23 +0300 (EEST) From: Arsen A. Gutsal [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: SOFTSKY To: [EMAIL PROTECTED] .apache.org Subject: SUBSCRIBE Date: Wed, 16 Jun 2004 17:04:27 +0300 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] X-Virus-Checked: Checked -- Sincerely, Arsen A. Gutsal SOFTSKY Cost Effective Software Development http://www.softsky.com.ua - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deployment to ROOT context
Hi, The path for the root context is not /. The directory name ROOT is just a choice: the context whose path is doesn't have to be located at a directory named ROOT. Yoav Shapira Millennium Research Informatics -Original Message- From: Arsen A. Gutsal [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 16, 2004 10:14 AM To: [EMAIL PROTECTED] Subject: Deployment to ROOT context Hello all. I have such problem: I'm working on some web-application and I need my servlet change default servlet. So I'm publishing my web-application to default (ROOT) context (/). I'm using NetBeans 3.6 and tomcat 5.0.19. When I try to deploy my web-application automatically I'm getting strange problems like: No context exists for path / or IllegalStateException: Container StandardContext[] has not been started. I will appreciate any help. On Wednesday 16 June 2004 17:04, [EMAIL PROTECTED] wrote: Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Acknowledgment: I have added the address [EMAIL PROTECTED] to the tomcat-user mailing list. Welcome to [EMAIL PROTECTED] Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address. --- Administrative commands for the tomcat-user list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: [EMAIL PROTECTED] To remove your address from the list, send a message to: [EMAIL PROTECTED] Send mail to the following for info and FAQ for this list: [EMAIL PROTECTED] [EMAIL PROTECTED] Similar addresses exist for the digest list: [EMAIL PROTECTED] [EMAIL PROTECTED] To get messages 123 through 145 (a maximum of 100 per request), mail: [EMAIL PROTECTED] To get an index with subject and author for messages 123-456 , mail: [EMAIL PROTECTED] They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: [EMAIL PROTECTED] The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example [EMAIL PROTECTED], just add a hyphen and your address (with '=' instead of '@') after the command word: [EMAIL PROTECTED] To stop subscription for this address, mail: [EMAIL PROTECTED] In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: [EMAIL PROTECTED] Received: (qmail 5210 invoked by uid 99); 16 Jun 2004 14:04:43 - Received: from [217.196.165.116] (HELO marlboro.softsky.com.ua) (217.196.165.116) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 16 Jun 2004 07:04:43 -0700 Received: from trussardi.softsky.com.ua (trussardi.softsky.com.ua [192.168.0.3]) by marlboro.softsky.com.ua (Postfix) with ESMTP id C325B48E8 for tomcat-user-sc.1087394577.kncghobmmenifedhklpn- [EMAIL PROTECTED] a.apache.org; Wed, 16 Jun 2004 16:42:23 +0300 (EEST) From: Arsen A. Gutsal [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: SOFTSKY To: tomcat-user-sc.1087394577.kncghobmmenifedhklpn- [EMAIL PROTECTED] .apache.org Subject: SUBSCRIBE Date: Wed, 16 Jun 2004 17:04:27 +0300 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] X-Virus-Checked: Checked -- Sincerely, Arsen A. Gutsal SOFTSKY Cost Effective Software Development http://www.softsky.com.ua - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deployment to ROOT context
Well, can you please help me to set up tomcat properly. My needs are to have the servlet which handles all requests to server: so, requests like http://myserver.con/somecontextpath/somescript will be handeled as well as http://myserver.con/anothercontextpath/anotherscript. I see that by default Tomcat is configured to use Default servlet to handle such requests. I would use my own. Can you please help me? On Wednesday 16 June 2004 17:20, Shapira, Yoav wrote: Hi, The path for the root context is not /. The directory name ROOT is just a choice: the context whose path is doesn't have to be located at a directory named ROOT. Yoav Shapira Millennium Research Informatics -Original Message- From: Arsen A. Gutsal [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 16, 2004 10:14 AM To: [EMAIL PROTECTED] Subject: Deployment to ROOT context Hello all. I have such problem: I'm working on some web-application and I need my servlet change default servlet. So I'm publishing my web-application to default (ROOT) context (/). I'm using NetBeans 3.6 and tomcat 5.0.19. When I try to deploy my web-application automatically I'm getting strange problems like: No context exists for path / or IllegalStateException: Container StandardContext[] has not been started. I will appreciate any help. On Wednesday 16 June 2004 17:04, [EMAIL PROTECTED] wrote: Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Acknowledgment: I have added the address [EMAIL PROTECTED] to the tomcat-user mailing list. Welcome to [EMAIL PROTECTED] Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address. --- Administrative commands for the tomcat-user list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: [EMAIL PROTECTED] To remove your address from the list, send a message to: [EMAIL PROTECTED] Send mail to the following for info and FAQ for this list: [EMAIL PROTECTED] [EMAIL PROTECTED] Similar addresses exist for the digest list: [EMAIL PROTECTED] [EMAIL PROTECTED] To get messages 123 through 145 (a maximum of 100 per request), mail: [EMAIL PROTECTED] To get an index with subject and author for messages 123-456 , mail: [EMAIL PROTECTED] They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: [EMAIL PROTECTED] The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example [EMAIL PROTECTED], just add a hyphen and your address (with '=' instead of '@') after the command word: [EMAIL PROTECTED] To stop subscription for this address, mail: [EMAIL PROTECTED] In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: [EMAIL PROTECTED] Received: (qmail 5210 invoked by uid 99); 16 Jun 2004 14:04:43 - Received: from [217.196.165.116] (HELO marlboro.softsky.com.ua) (217.196.165.116) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 16 Jun 2004 07:04:43 -0700 Received: from trussardi.softsky.com.ua (trussardi.softsky.com.ua [192.168.0.3]) by marlboro.softsky.com.ua (Postfix) with ESMTP id C325B48E8 for tomcat-user-sc.1087394577.kncghobmmenifedhklpn- [EMAIL PROTECTED] a.apache.org; Wed, 16 Jun 2004 16:42:23 +0300 (EEST) From: Arsen A. Gutsal [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: SOFTSKY To: tomcat-user-sc.1087394577.kncghobmmenifedhklpn- [EMAIL PROTECTED] .apache.org Subject: SUBSCRIBE Date: Wed, 16 Jun 2004 17:04:27 +0300 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] X-Virus-Checked: Checked -- Sincerely, Arsen A. Gutsal SOFTSKY Cost Effective Software Development http://www.softsky.com.ua - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments
Re: Deployment to ROOT context
Well, can you please help me to set up tomcat properly. My needs are to have the servlet which handles all requests to server: so, requests like http://myserver.con/somecontextpath/somescript will be handeled as well as http://myserver.con/anothercontextpath/anotherscript. I see that by default Tomcat is configured to use Default servlet to handle such requests. I would use my own. Can you please help me? On Wednesday 16 June 2004 17:20, Shapira, Yoav wrote: Hi, The path for the root context is not /. The directory name ROOT is just a choice: the context whose path is doesn't have to be located at a directory named ROOT. Yoav Shapira Millennium Research Informatics -Original Message- From: Arsen A. Gutsal [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 16, 2004 10:14 AM To: [EMAIL PROTECTED] Subject: Deployment to ROOT context Hello all. I have such problem: I'm working on some web-application and I need my servlet change default servlet. So I'm publishing my web-application to default (ROOT) context (/). I'm using NetBeans 3.6 and tomcat 5.0.19. When I try to deploy my web-application automatically I'm getting strange problems like: No context exists for path / or IllegalStateException: Container StandardContext[] has not been started. I will appreciate any help. On Wednesday 16 June 2004 17:04, [EMAIL PROTECTED] wrote: Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Acknowledgment: I have added the address [EMAIL PROTECTED] to the tomcat-user mailing list. Welcome to [EMAIL PROTECTED] Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address. --- Administrative commands for the tomcat-user list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: [EMAIL PROTECTED] To remove your address from the list, send a message to: [EMAIL PROTECTED] Send mail to the following for info and FAQ for this list: [EMAIL PROTECTED] [EMAIL PROTECTED] Similar addresses exist for the digest list: [EMAIL PROTECTED] [EMAIL PROTECTED] To get messages 123 through 145 (a maximum of 100 per request), mail: [EMAIL PROTECTED] To get an index with subject and author for messages 123-456 , mail: [EMAIL PROTECTED] They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send an empty message to: [EMAIL PROTECTED] The messages do not really need to be empty, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example [EMAIL PROTECTED], just add a hyphen and your address (with '=' instead of '@') after the command word: [EMAIL PROTECTED] To stop subscription for this address, mail: [EMAIL PROTECTED] In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at [EMAIL PROTECTED] Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: [EMAIL PROTECTED] Received: (qmail 5210 invoked by uid 99); 16 Jun 2004 14:04:43 - Received: from [217.196.165.116] (HELO marlboro.softsky.com.ua) (217.196.165.116) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 16 Jun 2004 07:04:43 -0700 Received: from trussardi.softsky.com.ua (trussardi.softsky.com.ua [192.168.0.3]) by marlboro.softsky.com.ua (Postfix) with ESMTP id C325B48E8 for tomcat-user-sc.1087394577.kncghobmmenifedhklpn- [EMAIL PROTECTED] a.apache.org; Wed, 16 Jun 2004 16:42:23 +0300 (EEST) From: Arsen A. Gutsal [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: SOFTSKY To: tomcat-user-sc.1087394577.kncghobmmenifedhklpn- [EMAIL PROTECTED] .apache.org Subject: SUBSCRIBE Date: Wed, 16 Jun 2004 17:04:27 +0300 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] X-Virus-Checked: Checked -- Sincerely, Arsen A. Gutsal SOFTSKY Cost Effective Software Development http://www.softsky.com.ua - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments
No hot deploy possible for ROOT context app?
Hi all, I've been working on setting up an application in the root context, meaning I configure it via this in server.xml: Context path= docBase=/path/to/my/war debug=0 / This works fine, and my application gets loaded properly at tomcat start-up. I just want to make sure I'm not missing any tricks. This approach seems to eliminate the possibility of hot deploy, right? Meaning, any time I change my war file, I need to restart tomcat? Next I will try an expanded war and reloadable classes, but any comments would be appreciated. This is 4.1.29 under jboss. Thanks, Fred - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Could I restart root context of a new host without restarting Tom cat 5?
Another strange point about Tomcat 5 is that I can create a new non-root context and reload it in a new host without restarting the application server. When I want to reload the context, I can press commit changes button and Tomcat 5 will re-initialize every context for me. However, for root context in the new host, Tomcat won't initialize it. Is there a workaround for the root context? Thank you very much. Best regards, Sheng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HttpSession and ROOT context path
Hi, I have a very peculiar situation. I have an webapplication whose main page(login.jsp) contains 2 frames. Each frame loads pages from different web application .Frame1 has index.jsp which is loaded from the same webapp as login.jsp and frame2 loads search.jsp from a different application running on a different tomcat. In frame1(index.jsp) there is a link which when user clicks opens a new window with url which is the url of frame2(search.jsp). Basically the authentication of frame1 and frame2 are done when user logs on to frame1(index.jsp) and hence it is expected that when user clicks on the link in frame1 to open frame2 url the user is already authenticated. This works perfectly when ROOT context of tomcat is not defined (Context path=). If ROOT context is defined to this application(application in frame1) IE doesn't behave as expected . It shows the login page of frame2 app instead of showing the next page as if the user is not logged in. Basically the session is not passing from frame2 to the new window. The same works in netscape and other browsers irrespective of the ROOT context. IE also behaves well when this application is not set as ROOT context. Can someone please shed some light on this peculiar situation. Thanks, Anna. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Redirect from root context to other context
What is required to redirect the root context to another context, with a relative path name rather than an absolute path name? can I just response.sendRedirect(/webapps/othercontext/); Or is there additional configuration - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Redirect from root context to other context
Hi, What is required to redirect the root context to another context, with a relative path name rather than an absolute path name? can I just response.sendRedirect(/webapps/othercontext/); Or is there additional configuration No additional configuration, just response.sendRedirect. You don't want the /webapps, just /othercontext/whatever. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Redirect from root context to other context
We had originally removed the /ROOT context. I put it back in place with the administrator context. It has saved to the server.xml file. When I browse to the site, it reports HTTP 500 - No context loaded If I add webaddress/ROOT it returns report HTTP 503 - Servlet jsp is currently unavailable 1. Will the /ROOT context work right after tomcat is restarted? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 10:54 AM To: Tomcat Users List Subject: RE: Redirect from root context to other context Hi, What is required to redirect the root context to another context, with a relative path name rather than an absolute path name? can I just response.sendRedirect(/webapps/othercontext/); Or is there additional configuration No additional configuration, just response.sendRedirect. You don't want the /webapps, just /othercontext/whatever. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Redirect from root context to other context
I had configured the ROOT context to have a path of /ROOT when it should be nothing. I still can't get the context to load without restarting the whole tomcat server (I wont). I can get the context to load on a secondary server with a tomcat restart.. -Original Message- From: Luc Foisy Sent: Tuesday, March 16, 2004 11:06 AM To: Tomcat Users List Subject: RE: Redirect from root context to other context We had originally removed the /ROOT context. I put it back in place with the administrator context. It has saved to the server.xml file. When I browse to the site, it reports HTTP 500 - No context loaded If I add webaddress/ROOT it returns report HTTP 503 - Servlet jsp is currently unavailable 1. Will the /ROOT context work right after tomcat is restarted? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 10:54 AM To: Tomcat Users List Subject: RE: Redirect from root context to other context Hi, What is required to redirect the root context to another context, with a relative path name rather than an absolute path name? can I just response.sendRedirect(/webapps/othercontext/); Or is there additional configuration No additional configuration, just response.sendRedirect. You don't want the /webapps, just /othercontext/whatever. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Redirect from root context to other context
I bet you already know this, but nevertheless: ROOT is a keyword for /. The URLs are http://domainname/contextname. In the case of ROOT, you don't have a contextname in the URL. Setting the attribute of the context reloadable=true helps in case you want your changes to reflect without restarting tomcat. Thanks, RS Luc Foisy [EMAIL PROTECTED]To: Tomcat Users List -magic.com [EMAIL PROTECTED] cc: 03/16/2004 10:55 AM Subject: RE: Redirect from root context to other context Please respond to Tomcat Users List I had configured the ROOT context to have a path of /ROOT when it should be nothing. I still can't get the context to load without restarting the whole tomcat server (I wont). I can get the context to load on a secondary server with a tomcat restart.. -Original Message- From: Luc Foisy Sent: Tuesday, March 16, 2004 11:06 AM To: Tomcat Users List Subject: RE: Redirect from root context to other context We had originally removed the /ROOT context. I put it back in place with the administrator context. It has saved to the server.xml file. When I browse to the site, it reports HTTP 500 - No context loaded If I add webaddress/ROOT it returns report HTTP 503 - Servlet jsp is currently unavailable 1. Will the /ROOT context work right after tomcat is restarted? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 10:54 AM To: Tomcat Users List Subject: RE: Redirect from root context to other context Hi, What is required to redirect the root context to another context, with a relative path name rather than an absolute path name? can I just response.sendRedirect(/webapps/othercontext/); Or is there additional configuration No additional configuration, just response.sendRedirect. You don't want the /webapps, just /othercontext/whatever. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This transmission is intended to be strictly confidential. If you are not the intended recipient of this message, you may not disclose, print, copy or disseminate this information. If you have received this in error, please reply and notify the sender (only) and delete the message. Unauthorized interception of this e-mail is a violation of federal criminal law. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: root context loaded again under its docbase name
Howdy, and this is my context (which is found in META-INF/context.xml): Context path= docBase=gargantus.war cachingAllowed=false reloadable=false Anybody else with the same setup see this? Bug or not bug? snip/ Seems like a bug. What happens if you don't have context.xml at all in your WAR, and simply drop the WAR in the webapps directory? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: root context loaded again under its docbase name
On 02/09/2004 02:58 PM Shapira, Yoav wrote: and this is my context (which is found in META-INF/context.xml): Context path= docBase=gargantus.war cachingAllowed=false reloadable=false Anybody else with the same setup see this? Bug or not bug? snip/ Seems like a bug. What happens if you don't have context.xml at all in your WAR, and simply drop the WAR in the webapps directory? If there's no context.xml, then I don't get a root context - no _, no nada - and no errors. Just the context with the same name as the war file. Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: root context loaded again under its docbase name
Howdy, If there's no context.xml, then I don't get a root context - no _, no nada - and no errors. Just the context with the same name as the war file. So if there's no context.xml, the behavior is correct (with all default values, e.g. reloadable). If you add a context.xml, you get the context twice, once as root and once appropriately. Seems like a bug, no? Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: root context loaded again under its docbase name
On 02/09/2004 11:01 PM Shapira, Yoav wrote: If there's no context.xml, then I don't get a root context - no _, no nada - and no errors. Just the context with the same name as the war file. So if there's no context.xml, the behavior is correct (with all default values, e.g. reloadable). If you add a context.xml, you get the context twice, once as root and once appropriately. Seems like a bug, no? Just tried that with a simple test.war file and a mickey mouse context.xml. It seems that it will not occur when the war has never been deployed before. But after the first deploy, once the war-file-name.xml exists in conf/Catalina/localhost/ and then when tomcat is restarted, tc then deploys the unwanted second context. I'll log it as a bug. Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
root context loaded again under its docbase name
I've seen and asked about this about a year ago but since it wasn't important, I didn't bother chasing it up when I found no solution. It's happening again. Tomcat loads my context twice. Once for root and once with the name of its WAR file. My war file is called gargantus.war. This is my Host: Host name=localhost appBase=webapps unpackWARs=false autoDeploy=false deployXML=true and this is my context (which is found in META-INF/context.xml): Context path= docBase=gargantus.war cachingAllowed=false reloadable=false Anybody else with the same setup see this? Bug or not bug? Interestingly tomcat creates working files in work/Catalina/localhost/_/ AND in work/Catalina/localhost/gargantus/ even when I only access the root context. Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: root context loaded again under its docbase name
I definitely have the same problem. And Tomcat does not execute context.xml. I presume is due to the error message: context already in use. Do you have the some problem? Hernani -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: sabado, 7 de Fevereiro de 2004 12:47 To: Tomcat Users List Subject: root context loaded again under its docbase name I've seen and asked about this about a year ago but since it wasn't important, I didn't bother chasing it up when I found no solution. It's happening again. Tomcat loads my context twice. Once for root and once with the name of its WAR file. My war file is called gargantus.war. This is my Host: Host name=localhost appBase=webapps unpackWARs=false autoDeploy=false deployXML=true and this is my context (which is found in META-INF/context.xml): Context path= docBase=gargantus.war cachingAllowed=false reloadable=false Anybody else with the same setup see this? Bug or not bug? Interestingly tomcat creates working files in work/Catalina/localhost/_/ AND in work/Catalina/localhost/gargantus/ even when I only access the root context. Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: root context loaded again under its docbase name
I get no error message - I just grepped the log file. For me the problem is totally benign - unless I decide that I want to have a context with the same name as my root context's war file. I suggest that you are getting an error because you have doubled the Context somehow - perhaps you still have it in your server.xml? Maybe you have an old .xml file in conf/Catalina/localhost/ ? Or maybe for you it lies in the way you declared the context. Adam On 02/07/2004 03:18 PM Hernani Mourao wrote: I definitely have the same problem. And Tomcat does not execute context.xml. I presume is due to the error message: context already in use. Do you have the some problem? Hernani -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: sabado, 7 de Fevereiro de 2004 12:47 To: Tomcat Users List Subject: root context loaded again under its docbase name I've seen and asked about this about a year ago but since it wasn't important, I didn't bother chasing it up when I found no solution. It's happening again. Tomcat loads my context twice. Once for root and once with the name of its WAR file. My war file is called gargantus.war. This is my Host: Host name=localhost appBase=webapps unpackWARs=false autoDeploy=false deployXML=true and this is my context (which is found in META-INF/context.xml): Context path= docBase=gargantus.war cachingAllowed=false reloadable=false Anybody else with the same setup see this? Bug or not bug? Interestingly tomcat creates working files in work/Catalina/localhost/_/ AND in work/Catalina/localhost/gargantus/ even when I only access the root context. Adam -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to start the root context with manager application
Hello, we recently installed Tomcat 4.1.24 on a SUSE 8.2 Linux machine and are trying to get to know how to start, stop and reload applications. So far, Tomcat and the applications seem to be running fine. We have defined our application to run as the default or ROOT application. In the Tomcat manager web application we can stop and reload this root application, but can not start it after having stopped it. The following error appears when trying to start the application at path / (http://xx/manager/html/start?path=/) FAIL - Application at context path / could not be started The documentation states The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string., so we tried replacing the / by (http://xx/manager/html/start?path=;) This results in a similar error: FAIL - No context exists for path How should we represent the zero-length string to start the ROOT application? The / is accepted in the stop (http://xx/manager/html/stop?path=/) and reload (http://xx/manager/html/reload?path=/)commands). We only tried this in the Manager web application. Kind regards, Francis Brouns - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to map Absolute URIs to subdirs in Tomcat's 'ROOT' context?
Howdy, Your JSPs should have the request getContextPath() as part of the image URL. Tomcat will not think /img is a webapp, it's smart enough to know what is and isn't a context path. And it's too bad you can't have relative image URLs, as that's really the correct solution. Yoav Shapira Millennium ChemInformatics -Original Message- From: Jeffery Cann [mailto:[EMAIL PROTECTED] Sent: Saturday, December 27, 2003 11:19 AM To: [EMAIL PROTECTED] Subject: How to map Absolute URIs to subdirs in Tomcat's 'ROOT' context? Greetings. I have an application that is currently running within my $CATALINA_HOME/webapps/mywebapp directory. I access it as: http://localhost:8080/mywebapp/ Within this webapp, there is an 'img' subdirectory. This contains all of the site images used in JSPs: $CATALINA_HOME/webapps/mywebapp/img/ Consequently, all of the JSPs use the absolute URI to reference images, i.e., img src=/mywebapp/img/logo.gif Now, I wish run mywebapp in Tomcat's 'ROOT' application context: $CATALINA_HOME/webapps/ROOT so that I can access it as http://localhost:8080/ I changed an example JSP to refer to this absolute URI: img src=/img/logo.gif [The 'img' subdirectory is now located at $CATALINA_HOME/ROOT/img after I expanded the mywebapp.war] Images referenced using the absolute URI /img/logo.gif do not load. Using a web browser, I can navigate to http://localhost:8080/img/logo.gif and it will load, so I don't think there is a permissions problem. I think when the JSP is compiled by Tomcat, it thinks that /img is an application context, rather than a subdirectory of the ROOT application context. My question: How can I configure Tomcat to allow my absolute URI reference to this image subdirectory? [NOTE: For various reasons, like secure (HTTPS) aliases, we are unable to use relative references to the 'img' directory.] Thanks for any suggestions. Jeff __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to map Absolute URIs to subdirs in Tomcat's 'ROOT' context?
Greetings. I have an application that is currently running within my $CATALINA_HOME/webapps/mywebapp directory. I access it as: http://localhost:8080/mywebapp/ Within this webapp, there is an 'img' subdirectory. This contains all of the site images used in JSPs: $CATALINA_HOME/webapps/mywebapp/img/ Consequently, all of the JSPs use the absolute URI to reference images, i.e., img src=/mywebapp/img/logo.gif Now, I wish run mywebapp in Tomcat's 'ROOT' application context: $CATALINA_HOME/webapps/ROOT so that I can access it as http://localhost:8080/ I changed an example JSP to refer to this absolute URI: img src=/img/logo.gif [The 'img' subdirectory is now located at $CATALINA_HOME/ROOT/img after I expanded the mywebapp.war] Images referenced using the absolute URI /img/logo.gif do not load. Using a web browser, I can navigate to http://localhost:8080/img/logo.gif and it will load, so I don't think there is a permissions problem. I think when the JSP is compiled by Tomcat, it thinks that /img is an application context, rather than a subdirectory of the ROOT application context. My question: How can I configure Tomcat to allow my absolute URI reference to this image subdirectory? [NOTE: For various reasons, like secure (HTTPS) aliases, we are unable to use relative references to the 'img' directory.] Thanks for any suggestions. Jeff __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple virtual hosts at root context
I am using Tomcat 4.1.27 under Linux for a project where the machine is embedded into a pumping machine, i.e. limited memory and resources. The 'services' are all identified by sub domains so that you would get a master domain of the pump site, a sub domain for each pump unit and a further subdomain for each reading. For example, http://finham - gives an overview of the site called finham http://top-bearing.finham gives an overview of the pump called top-bearing http://power.top-bearing.finham gives a power reading for the pump etc. Everything was developed with Apache fronting Tomcat and all is well. We've now arrived at the factory tests and I think I've shot myself in the foot. I had always intended to remove the Apache front end as it just will not fit onto the hardware. The problem seems to be that you cannot have a standalone Tomcat supporting many virtual hosts where the context paths are the same. You can in Apache. I appreciate that there are other ways to do this but this 'design' has now been used by other systems so any changes are bad news at this stage. My question is, am I correct that this cannot be done using a standalone Tomcat and, if not, does anyone have any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: Multiple virtual hosts at root context
Oops. In the panic of thinking it wasn't possible I somehow proved to myself that it wasn't possible |-( I inadvertently loaded all the contexts for all the hosts into all the hosts. I think the previous post is what used to be known as a structured walk through. So thanks for that all the same. Date: Tue, 21 Oct 2003 09:55:24 +0100 To: Tomcat Users List [EMAIL PROTECTED] From: Andy Hutchinson [EMAIL PROTECTED] Subject: Multiple virtual hosts at root context I am using Tomcat 4.1.27 under Linux for a project where the machine is embedded into a pumping machine, i.e. limited memory and resources. The 'services' are all identified by sub domains so that you would get a master domain of the pump site, a sub domain for each pump unit and a further subdomain for each reading. For example, http://finham - gives an overview of the site called finham http://top-bearing.finham gives an overview of the pump called top-bearing http://power.top-bearing.finham gives a power reading for the pump etc. Everything was developed with Apache fronting Tomcat and all is well. We've now arrived at the factory tests and I think I've shot myself in the foot. I had always intended to remove the Apache front end as it just will not fit onto the hardware. The problem seems to be that you cannot have a standalone Tomcat supporting many virtual hosts where the context paths are the same. You can in Apache. I appreciate that there are other ways to do this but this 'design' has now been used by other systems so any changes are bad news at this stage. My question is, am I correct that this cannot be done using a standalone Tomcat and, if not, does anyone have any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple virtual hosts at root context
You can have virtual hosts in tomcat. We are doing it, but I will need to look up the server.xml configuration: Host name=host1.com debug=0 appBase=webapps unpackWARs=true etc... Context path= docBase=/usr/local/webapps/partners debug=0 reloadable=false crossContext=false etc... /Context /Host Host name=host2.com debug=0 appBase=webapps unpackWARs=true etc... Context path= docBase=/usr/local/webapps/rr debug=0 reloadable=false crossContext=false etc... /Context etc... /Host It works fine for us. Daniel Gibby Andy Hutchinson wrote: I am using Tomcat 4.1.27 under Linux for a project where the machine is embedded into a pumping machine, i.e. limited memory and resources. The 'services' are all identified by sub domains so that you would get a master domain of the pump site, a sub domain for each pump unit and a further subdomain for each reading. For example, http://finham - gives an overview of the site called finham http://top-bearing.finham gives an overview of the pump called top-bearing http://power.top-bearing.finham gives a power reading for the pump etc. Everything was developed with Apache fronting Tomcat and all is well. We've now arrived at the factory tests and I think I've shot myself in the foot. I had always intended to remove the Apache front end as it just will not fit onto the hardware. The problem seems to be that you cannot have a standalone Tomcat supporting many virtual hosts where the context paths are the same. You can in Apache. I appreciate that there are other ways to do this but this 'design' has now been used by other systems so any changes are bad news at this stage. My question is, am I correct that this cannot be done using a standalone Tomcat and, if not, does anyone have any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Yes, I did this. But the problem looks to me like the server is caching
the page and not the client. Because, when you access the servlet directly
it refreshes the content just fine, but when you access it through the jsp
page that forwards the request it never changes after the first request.
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
Wade Chandler [EMAIL PROTECTED]
10/10/2003 12:26 PM
Please respond to Tomcat Users List
To: 'Tomcat Users List' [EMAIL PROTECTED]
cc:
Subject:RE: Help root context problem!!!
I did not see the other posts, but anytime I have a problem with issues
like this I use a meta tag to make the page expire some time ago. I
usually put stuff like this:
META HTTP-EQUIV=expires CONTENT=Tue, 2 OCT 1996 17:45:00 GMT
in my head. There is also a header which you can set in your
jsp/servlet code of the same name (Expires)..that is what the HTTP-EQUIV
does. Says in this html take this to be the same as an http header and
use it as such.
Hope that helps,
Wade
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 1:14 PM
To: Tomcat Users List
Subject: RE: Help root context problem!!!
Well, I got it to work, but I don't care for it. I'd like to know what's
wrong if someone knows. Here's the jsp below:
%
java.net.URL url = new
java.net.URL(request.getRequestURL().append(/PageWorks/servlet/PageMill
).toString());
java.net.URLConnection connect = url.openConnection();
connect.connect();
java.io.BufferedReader in = new java.io.BufferedReader(new
java.io.InputStreamReader(connect.getInputStream()));
String html;
while((html = in.readLine()) != null){
out.write(html);
}
%
This works, but it's not very pretty of a method. Why doesn't the
jsp:forward/ work? This way it doesn't cache the page forever on the
server. If I just us jsp:forward it caches the page and never update
it's
information from the servlet.
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Well, I got it to work, but I don't care for it. I'd like to know what's
wrong if someone knows. Here's the jsp below:
%
java.net.URL url = new
java.net.URL(request.getRequestURL().append(/PageWorks/servlet/PageMill).toString());
java.net.URLConnection connect = url.openConnection();
connect.connect();
java.io.BufferedReader in = new java.io.BufferedReader(new
java.io.InputStreamReader(connect.getInputStream()));
String html;
while((html = in.readLine()) != null){
out.write(html);
}
%
This works, but it's not very pretty of a method. Why doesn't the
jsp:forward/ work? This way it doesn't cache the page forever on the
server. If I just us jsp:forward it caches the page and never update it's
information from the servlet.
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
RE: Help root context problem!!!
I did not see the other posts, but anytime I have a problem with issues
like this I use a meta tag to make the page expire some time ago. I
usually put stuff like this:
META HTTP-EQUIV=expires CONTENT=Tue, 2 OCT 1996 17:45:00 GMT
in my head. There is also a header which you can set in your
jsp/servlet code of the same name (Expires)..that is what the HTTP-EQUIV
does. Says in this html take this to be the same as an http header and
use it as such.
Hope that helps,
Wade
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 1:14 PM
To: Tomcat Users List
Subject: RE: Help root context problem!!!
Well, I got it to work, but I don't care for it. I'd like to know what's
wrong if someone knows. Here's the jsp below:
%
java.net.URL url = new
java.net.URL(request.getRequestURL().append(/PageWorks/servlet/PageMill
).toString());
java.net.URLConnection connect = url.openConnection();
connect.connect();
java.io.BufferedReader in = new java.io.BufferedReader(new
java.io.InputStreamReader(connect.getInputStream()));
String html;
while((html = in.readLine()) != null){
out.write(html);
}
%
This works, but it's not very pretty of a method. Why doesn't the
jsp:forward/ work? This way it doesn't cache the page forever on the
server. If I just us jsp:forward it caches the page and never update
it's
information from the servlet.
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Help root context problem!!!
I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813
RE: Help root context problem!!!
Howdy, Post the relevant sections of your server.xml. All you had to do is make path= in your Context declaration. Yoav Shapira Millennium ChemInformatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Here is it. !-- Tomcat Root Context -- Context path= docBase=PageWorks debug=0 / Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Shapira, Yoav [EMAIL PROTECTED] 10/09/2003 03:04 PM Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Howdy, Post the relevant sections of your server.xml. All you had to do is make path= in your Context declaration. Yoav Shapira Millennium ChemInformatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
No, but what will that do for me? Would I have to do that every time? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:20 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Hi Justin, The work directory contains the generated source code and compiled classes for JSPs. When a JSP is first requested, Tomcat generates Java source code for the JSP, and then compiles it. Both the source code and the compiled class are stored there. Since you changed your context and didn't change any code, tomcat may not have updated your work directory accordingly. Try shutting down tomcat, deleting the contents of your work directoy and restarting. You should not have to do this everytime. Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:25 PM To: Tomcat Users List Subject: RE: Help root context problem!!! No, but what will that do for me? Would I have to do that every time? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:20 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Oh, no that's not it. It does recompile the code just fine. If you for example call http://myserver/a-path/index.jsp it works fine. Then index.jsp will forward to http://myserver/a-path/servlet/MyServlet and that works just fine. Both path will reflect any changes of the dynamic content from the database. But if you access the index.jsp using http://myserver it will load the content the first time, which it gets from the Servlet and the servlet get from the database. However, from that point on the http://myserver path will keep showing the same content even after changing it in the database. Basically it's only loading the information from the jsp and caching it forever. But if you access the jsp and servlet directly using http://myserver/a-path/index.jsp or for the servlet http://myserver/a-path/servlet/MyServlet they both will reflect the changes. For some reason the context is caching the last content send and never let's it go even though the jsp and servlet show they have the updated information in them. It's not the code that needs to be recompiled, it's the dynamic content from the database that needs to update. Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:40 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, The work directory contains the generated source code and compiled classes for JSPs. When a JSP is first requested, Tomcat generates Java source code for the JSP, and then compiles it. Both the source code and the compiled class are stored there. Since you changed your context and didn't change any code, tomcat may not have updated your work directory accordingly. Try shutting down tomcat, deleting the contents of your work directoy and restarting. You should not have to do this everytime. Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:25 PM To: Tomcat Users List Subject: RE: Help root context problem!!! No, but what will that do for me? Would I have to do that every time? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:20 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
Sorry, I misunderstood. So something else here is caching your page. Do you have a webserver sitting in front of tomcat or just tomcat? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 5:05 PM To: Tomcat Users List Subject: RE: Help root context problem!!! Oh, no that's not it. It does recompile the code just fine. If you for example call http://myserver/a-path/index.jsp it works fine. Then index.jsp will forward to http://myserver/a-path/servlet/MyServlet and that works just fine. Both path will reflect any changes of the dynamic content from the database. But if you access the index.jsp using http://myserver it will load the content the first time, which it gets from the Servlet and the servlet get from the database. However, from that point on the http://myserver path will keep showing the same content even after changing it in the database. Basically it's only loading the information from the jsp and caching it forever. But if you access the jsp and servlet directly using http://myserver/a-path/index.jsp or for the servlet http://myserver/a-path/servlet/MyServlet they both will reflect the changes. For some reason the context is caching the last content send and never let's it go even though the jsp and servlet show they have the updated information in them. It's not the code that needs to be recompiled, it's the dynamic content from the database that needs to update. Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:40 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, The work directory contains the generated source code and compiled classes for JSPs. When a JSP is first requested, Tomcat generates Java source code for the JSP, and then compiles it. Both the source code and the compiled class are stored there. Since you changed your context and didn't change any code, tomcat may not have updated your work directory accordingly. Try shutting down tomcat, deleting the contents of your work directoy and restarting. You should not have to do this everytime. Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:25 PM To: Tomcat Users List Subject: RE: Help root context problem!!! No, but what will that do for me? Would I have to do that every time? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:20 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help root context problem!!!
That's ok. Yep, something else. Here's what's in my jsp page: jsp:forward page=/servlet/PageMill / It just forwards to the servlet. It's strange, if you use the full path to either one you get the updated information from the database. But if you access using that context I set in the server.xml it loads the information from the database once and that's it. It just keeps sending what was sent the first time. Looks to me like it's not even accessing the jsp to get the info. Would the backgroundProcessorDelay setting help any? I didn't understand the doc's very well on that. Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 04:22 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Sorry, I misunderstood. So something else here is caching your page. Do you have a webserver sitting in front of tomcat or just tomcat? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 5:05 PM To: Tomcat Users List Subject: RE: Help root context problem!!! Oh, no that's not it. It does recompile the code just fine. If you for example call http://myserver/a-path/index.jsp it works fine. Then index.jsp will forward to http://myserver/a-path/servlet/MyServlet and that works just fine. Both path will reflect any changes of the dynamic content from the database. But if you access the index.jsp using http://myserver it will load the content the first time, which it gets from the Servlet and the servlet get from the database. However, from that point on the http://myserver path will keep showing the same content even after changing it in the database. Basically it's only loading the information from the jsp and caching it forever. But if you access the jsp and servlet directly using http://myserver/a-path/index.jsp or for the servlet http://myserver/a-path/servlet/MyServlet they both will reflect the changes. For some reason the context is caching the last content send and never let's it go even though the jsp and servlet show they have the updated information in them. It's not the code that needs to be recompiled, it's the dynamic content from the database that needs to update. Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:40 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, The work directory contains the generated source code and compiled classes for JSPs. When a JSP is first requested, Tomcat generates Java source code for the JSP, and then compiles it. Both the source code and the compiled class are stored there. Since you changed your context and didn't change any code, tomcat may not have updated your work directory accordingly. Try shutting down tomcat, deleting the contents of your work directoy and restarting. You should not have to do this everytime. Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:25 PM To: Tomcat Users List Subject: RE: Help root context problem!!! No, but what will that do for me? Would I have to do that every time? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:20 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver
RE: Help root context problem!!!
Oh, yep just Tomcat no web server. Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 04:22 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Sorry, I misunderstood. So something else here is caching your page. Do you have a webserver sitting in front of tomcat or just tomcat? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 5:05 PM To: Tomcat Users List Subject: RE: Help root context problem!!! Oh, no that's not it. It does recompile the code just fine. If you for example call http://myserver/a-path/index.jsp it works fine. Then index.jsp will forward to http://myserver/a-path/servlet/MyServlet and that works just fine. Both path will reflect any changes of the dynamic content from the database. But if you access the index.jsp using http://myserver it will load the content the first time, which it gets from the Servlet and the servlet get from the database. However, from that point on the http://myserver path will keep showing the same content even after changing it in the database. Basically it's only loading the information from the jsp and caching it forever. But if you access the jsp and servlet directly using http://myserver/a-path/index.jsp or for the servlet http://myserver/a-path/servlet/MyServlet they both will reflect the changes. For some reason the context is caching the last content send and never let's it go even though the jsp and servlet show they have the updated information in them. It's not the code that needs to be recompiled, it's the dynamic content from the database that needs to update. Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:40 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, The work directory contains the generated source code and compiled classes for JSPs. When a JSP is first requested, Tomcat generates Java source code for the JSP, and then compiles it. Both the source code and the compiled class are stored there. Since you changed your context and didn't change any code, tomcat may not have updated your work directory accordingly. Try shutting down tomcat, deleting the contents of your work directoy and restarting. You should not have to do this everytime. Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:25 PM To: Tomcat Users List Subject: RE: Help root context problem!!! No, but what will that do for me? Would I have to do that every time? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Lee, PaulNYC [EMAIL PROTECTED] 10/09/2003 03:20 PM Please respond to Tomcat Users List To: 'Tomcat Users List' [EMAIL PROTECTED] cc: Subject:RE: Help root context problem!!! Hi Justin, Did you try deleting the contents of the work folder? Regards, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 3:41 PM To: [EMAIL PROTECTED] Subject: Help root context problem!!! I'm having caching problems with Tomcat. Here's what I'm trying to do. I have an app under the mapping of /PageWorks. In the context I have a index.jsp that does a jsp:forward to a servlet that handles the request. So to access the app you have to type http://myserver/PageWorks and it works. But, I want user to be able to type http://myserver and the /PageWorks/index.jsp with respond. So to do this I change the context in the server.xml file to point to PageWorks instead of ROOT. This also worked like I wanted, but the index.jsp is loaded from the /PageWorks app once. Then from there on it sends the old content every time. The servlet that this jsp is forwarding to changes and so does the jsp, but the http://myserver always returns the old. If you access the servlet or jsp using there full http://myserver/PageWorks path you get the new content every time. I've tried all the client side cache tricks, but I know for sure it's the server that's caching it. How can I get this to stop? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail
RE: Help root context problem!!!
I just changed the jsp page to a program and removed the jsp:forward and it works. I set a single parameter that can be supplied and that will make it print a different set of numbers. When I do that it changes just fine. So my question is, why will the forward not work? Thank You, Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813
Relocate Root Context
Is there way to point the Root Context to another location? The default appBase is pointed to webapps in server.xml. I want it to point to maybe /usr/local/apache/htdocs instead of the default /usr/tomcat/webapps. What is the proper way to do this including the correct syntax? Please advise. TIA, Dan __ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Relocate Root Context
Context path= docBase=/usr/local/myroot debug=0/ in server.xml Filip - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 02, 2003 1:50 PM Subject: Relocate Root Context Is there way to point the Root Context to another location? The default appBase is pointed to webapps in server.xml. I want it to point to maybe /usr/local/apache/htdocs instead of the default /usr/tomcat/webapps. What is the proper way to do this including the correct syntax? Please advise. TIA, Dan __ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with root context
Hi Every time when I'm trying to update my application located on root context I facing strange problems, which can be solved only by restarting tomcat. When I'm trying to remove an application located on root context I getting the following message Command: http://www.zzz.lt/manager/remove?path=/ Response: FAIL - No context exists for path / But when I'm issung command: http://www.zzz.lt/manager/list Response is: OK - Listed applications for virtual host www.zzz.lt /:running:0:/home/www/eurobiuras/webapps/ROOT.war /manager:running:0:/opt/tomcat/server/webapps/manager By the way, when I do same things with any other context, not root everything is just fine. So is it bug of feature, and how to deal with it. Thanks Remis Sista Tako patu (http://www.takas.lt)! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problems with root context
Howdy, The path for the root context is , not /. Yoav Shapira Millennium ChemInformatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2003 6:53 AM To: [EMAIL PROTECTED] Subject: Problems with root context Hi Every time when I'm trying to update my application located on root context I facing strange problems, which can be solved only by restarting tomcat. When I'm trying to remove an application located on root context I getting the following message Command: http://www.zzz.lt/manager/remove?path=/ Response: FAIL - No context exists for path / But when I'm issung command: http://www.zzz.lt/manager/list Response is: OK - Listed applications for virtual host www.zzz.lt /:running:0:/home/www/eurobiuras/webapps/ROOT.war /manager:running:0:/opt/tomcat/server/webapps/manager By the way, when I do same things with any other context, not root everything is just fine. So is it bug of feature, and how to deal with it. Thanks Remis Sista Tako patu (http://www.takas.lt)! This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
newbie needs help - root context not working with apache
I am running Tomcat 4.1.27 with Apache 2.0.47, using the jk2 2.0.43 connector and j2sdk 1.4.2 I connected Tomcat to Apache using the instructions at http://www.gregoire.org/howto/Apache2_Jk2_TC4.1.x_JSDK1.4.x.html I can open localhost/examples/servlet/HelloWorldExample If I move HelloWorldExample.class into the ROOT contexts WEB-INF folder, I can open it using localhost:8080/servlet/Hello... but I cannot open it using localhost/servlet/Hello... The Tomcat Root Context section in server.xml has been uncommented, but that hasn't helped. I NEED this to work, but I really don't know how to get this new Tomcat version to do it. What am I missing? Can anyone point me to documentation where this is covered? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie needs help - root context not working with apache
It's not working for a couple reasons, not least of which there is no servlet mapping in ROOT's web.xml file, and no entry for the default Invoker. Also, you haven't told us how you changed your JK2 properties file to match the new URL, that is, if you did so (you need to). Sooo...maybe you can repost with a little more detail about what it is that you want to do, what URL you want to use, etc. You might also consider not using Apache and JK2 at all...its not required. John Steve Veltman wrote: I am running Tomcat 4.1.27 with Apache 2.0.47, using the jk2 2.0.43 connector and j2sdk 1.4.2 I connected Tomcat to Apache using the instructions at http://www.gregoire.org/howto/Apache2_Jk2_TC4.1.x_JSDK1.4.x.html I can open localhost/examples/servlet/HelloWorldExample If I move HelloWorldExample.class into the ROOT contexts WEB-INF folder, I can open it using localhost:8080/servlet/Hello... but I cannot open it using localhost/servlet/Hello... The Tomcat Root Context section in server.xml has been uncommented, but that hasn't helped. I NEED this to work, but I really don't know how to get this new Tomcat version to do it. What am I missing? Can anyone point me to documentation where this is covered? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Autodeploy WAR File to ROOT Context Problem
I'm deploying a WAR file to the root context (path=). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing: Tomcat is deleting the context XML file so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of / Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly? Thanks, Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Autodeploy WAR File to ROOT Context Problem
OK, Tried again, and this time the file was not deleted not sure what happened last time. But now I'm getting the WAR autoDeployed according to both the context XML file AND as a war file to a directory with the same name as the WAR file. In other words, my webapp is now accessible via 2 contexts, no big deal, but I'd prefer to have only the root context. Also, let me explain a little better. I am reading this section in the Docs: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/host.html#Automatic%20Application%20Deployment And it indicates I can autoDeploy by creating a file *.xml with a Context tag inside. This will act as if that context was entered in my server.xml. This enables me to control where my WAR will be deployed via a file external to server.xml. This is exactly what I want. The second autoDeploy takes each *.war file and deploys it to a webapp named the same as the war file. For example, my SoiledDove.war gets deployed to a /SoiledDove webapp. Because my context XML file deploys to path= (the ROOT context in other words), AND my SoiledDove.war file is in the webapps directory... I am getting double auto-deployment. How can I control which autoDeployment methods are enabled for a particular WAR? Thanks, Aaron Aaron Longwell wrote: I'm deploying a WAR file to the root context (path=). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing: Tomcat is deleting the context XML file so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of / Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly? Thanks, Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Autodeploy WAR File to ROOT Context Problem
AFAIK, you have to stop putting your WAR file in /webapps. There should probably be a check, or something, though, so that Tomcat can tell if it has already deployed a webapp. John On Tue, 15 Jul 2003 13:59:24 -0600, Aaron Longwell [EMAIL PROTECTED] wrote: OK, Tried again, and this time the file was not deleted not sure what happened last time. But now I'm getting the WAR autoDeployed according to both the context XML file AND as a war file to a directory with the same name as the WAR file. In other words, my webapp is now accessible via 2 contexts, no big deal, but I'd prefer to have only the root context. Also, let me explain a little better. I am reading this section in the Docs: http://jakarta.apache.org/tomcat/tomcat-4.1- doc/config/host.html#Automatic%20Application%20Deployment And it indicates I can autoDeploy by creating a file *.xml with a Context tag inside. This will act as if that context was entered in my server.xml. This enables me to control where my WAR will be deployed via a file external to server.xml. This is exactly what I want. The second autoDeploy takes each *.war file and deploys it to a webapp named the same as the war file. For example, my SoiledDove.war gets deployed to a /SoiledDove webapp. Because my context XML file deploys to path= (the ROOT context in other words), AND my SoiledDove.war file is in the webapps directory... I am getting double auto-deployment. How can I control which autoDeployment methods are enabled for a particular WAR? Thanks, Aaron Aaron Longwell wrote: I'm deploying a WAR file to the root context (path=). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing: Tomcat is deleting the context XML file so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of / Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly? Thanks, Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Autodeploy WAR File to ROOT Context Problem
Is there a standard alternate location for the WAR file? John Turner wrote: AFAIK, you have to stop putting your WAR file in /webapps. There should probably be a check, or something, though, so that Tomcat can tell if it has already deployed a webapp. John On Tue, 15 Jul 2003 13:59:24 -0600, Aaron Longwell [EMAIL PROTECTED] wrote: OK, Tried again, and this time the file was not deleted not sure what happened last time. But now I'm getting the WAR autoDeployed according to both the context XML file AND as a war file to a directory with the same name as the WAR file. In other words, my webapp is now accessible via 2 contexts, no big deal, but I'd prefer to have only the root context. Also, let me explain a little better. I am reading this section in the Docs: http://jakarta.apache.org/tomcat/tomcat-4.1- doc/config/host.html#Automatic%20Application%20Deployment And it indicates I can autoDeploy by creating a file *.xml with a Context tag inside. This will act as if that context was entered in my server.xml. This enables me to control where my WAR will be deployed via a file external to server.xml. This is exactly what I want. The second autoDeploy takes each *.war file and deploys it to a webapp named the same as the war file. For example, my SoiledDove.war gets deployed to a /SoiledDove webapp. Because my context XML file deploys to path= (the ROOT context in other words), AND my SoiledDove.war file is in the webapps directory... I am getting double auto-deployment. How can I control which autoDeployment methods are enabled for a particular WAR? Thanks, Aaron Aaron Longwell wrote: I'm deploying a WAR file to the root context (path=). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing: Tomcat is deleting the context XML file so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of / Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly? Thanks, Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Autodeploy WAR File to ROOT Context Problem
From the doc: The docBase attribute of this Context element will typically be the absolute pathname to a web applicationd directory, or the absolute pathname of a web application archive (WAR) file (which will not be expanded). With an absolute docBase, your WAR file can go anywhere...it doesn't have to go in webapps. John On Tue, 15 Jul 2003 13:59:24 -0600, Aaron Longwell [EMAIL PROTECTED] wrote: OK, Tried again, and this time the file was not deleted not sure what happened last time. But now I'm getting the WAR autoDeployed according to both the context XML file AND as a war file to a directory with the same name as the WAR file. In other words, my webapp is now accessible via 2 contexts, no big deal, but I'd prefer to have only the root context. Also, let me explain a little better. I am reading this section in the Docs: http://jakarta.apache.org/tomcat/tomcat-4.1- doc/config/host.html#Automatic%20Application%20Deployment And it indicates I can autoDeploy by creating a file *.xml with a Context tag inside. This will act as if that context was entered in my server.xml. This enables me to control where my WAR will be deployed via a file external to server.xml. This is exactly what I want. The second autoDeploy takes each *.war file and deploys it to a webapp named the same as the war file. For example, my SoiledDove.war gets deployed to a /SoiledDove webapp. Because my context XML file deploys to path= (the ROOT context in other words), AND my SoiledDove.war file is in the webapps directory... I am getting double auto-deployment. How can I control which autoDeployment methods are enabled for a particular WAR? Thanks, Aaron Aaron Longwell wrote: I'm deploying a WAR file to the root context (path=). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing: Tomcat is deleting the context XML file so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of / Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly? Thanks, Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Autodeploy WAR File to ROOT Context Problem
I found out what caused the delete of the context XML file: It is deleted after removing the SoiledDove web application (in other words the webapp with the same name as the war... I think this may be because my war and xml have the same name: SoiledDove.xml., SoiledDove.war) Aaron Longwell wrote: OK, Tried again, and this time the file was not deleted not sure what happened last time. But now I'm getting the WAR autoDeployed according to both the context XML file AND as a war file to a directory with the same name as the WAR file. In other words, my webapp is now accessible via 2 contexts, no big deal, but I'd prefer to have only the root context. Also, let me explain a little better. I am reading this section in the Docs: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/host.html#Automatic%20Application%20Deployment And it indicates I can autoDeploy by creating a file *.xml with a Context tag inside. This will act as if that context was entered in my server.xml. This enables me to control where my WAR will be deployed via a file external to server.xml. This is exactly what I want. The second autoDeploy takes each *.war file and deploys it to a webapp named the same as the war file. For example, my SoiledDove.war gets deployed to a /SoiledDove webapp. Because my context XML file deploys to path= (the ROOT context in other words), AND my SoiledDove.war file is in the webapps directory... I am getting double auto-deployment. How can I control which autoDeployment methods are enabled for a particular WAR? Thanks, Aaron Aaron Longwell wrote: I'm deploying a WAR file to the root context (path=). I've created the appropriate context XML file in the webapps dir and pointed it to a WAR (which I do NOT want to be expanded). It's working great... except for one thing: Tomcat is deleting the context XML file so that when I stop and restart the server, my WAR file is re-deployed at /WARFileName instead of / Why does tomcat delete this XML file for my webapp but not for Admin or Manager webapps? Am I doing this incorrectly? Thanks, Aaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ROOT context fails to use mail/Session Resource param. defaults to localhost
I am not able to use the JNDI mail Factory from the ROOT context. It works when run from the examples context and other non-ROOT contexts as well. For some reason, the ROOT context fails to correctly load the SMTP host variable defined by the JNDI resource in the server.xml(below). It does however register in the Context log (below) with the correct value. Exception Log ENCOUNTERED EXCEPTION: javax.mail.SendFailedException: Sending failed; nested exception is: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused: connect javax.mail.SendFailedException: Sending failed; nested exception is: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused: connect at javax.mail.Transport.send0(Transport.java:219) at javax.mail.Transport.send(Transport.java:81) at SendMailServlet.doPost(SendMailServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:376) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java:221) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) web.xml web-app display-nameROOT Context/display-name !-- Define servlets and Mappings -- servlet servlet-nameSendMailServlet/servlet-name servlet-classSendMailServlet/servlet-class /servlet servlet-mapping servlet-nameSendMailServlet/servlet-name url-pattern/SendMailServlet/url-pattern /servlet-mapping resource-ref res-ref-namemail/Session/res-ref-name res-typejavax.mail.Session/res-type res-authContainer/res-auth /resource-ref /web-app server.xml !-- ROOT Context -- Context debug=99 docBase=/ROOT path= reloadable=true source=com.ibm.etools.webtools.server:ROOT Logger className=org.apache.catalina.logger.FileLogger prefix=Context_ROOT_ suffix=.log
Re: ROOT context fails to use mail/Session Resource param. defaults to localhost
Windows 2000, Tomcat 4.1.24, Sun J2SDK1.4.1_02
Raimee Stevens [EMAIL PROTECTED] wrote:
I am not able to use the JNDI mail Factory from the ROOT context. It works when
run from the examples context and other non-ROOT contexts as well. For some reason,
the ROOT context fails to correctly load the SMTP host variable defined by the JNDI
resource in the server.xml(below). It does however register in the Context log (below)
with the correct value.
Exception Log
ENCOUNTERED EXCEPTION: javax.mail.SendFailedException: Sending failed; nested
exception is: javax.mail.MessagingException: Could not connect to SMTP host:
localhost, port: 25; nested exception is: java.net.ConnectException: Connection
refused: connect
javax.mail.SendFailedException: Sending failed;
nested exception is:
javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25;
nested exception is:
java.net.ConnectException: Connection refused: connect
at javax.mail.Transport.send0(Transport.java:219)
at javax.mail.Transport.send(Transport.java:81)
at SendMailServlet.doPost(SendMailServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:376)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java:221)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:536)
web.xml
ROOT Context
SendMailServlet
SendMailServlet
SendMailServlet
/SendMailServlet
mail/Session
javax.mail.Session
Container
server.xml
mail.smtp.host
Context FileLogger output shows that JNDI naming context was correctly initialized
with correct host name: ()
2003-07-09 14:37:41 NamingContextListener[/Standalone/myhostname]: Creating JNDI
naming context
2003-07-09 14:37:41 NamingContextListener[/Standalone/myhostname]: Resource parameters
for mail/Session = ResourceParams[name=mail/Session, parameters={mail.smtp.host=}]
2003-07-09 14:37:41 NamingContextListener[/Standalone
ROOT context fails to use mail/Session Resource param. defaults to localhost
I am not able to use the JNDI mail Factory from the ROOT context. It works when run from the examples context and other non-ROOT contexts as well. For some reason, the ROOT context fails to correctly load the SMTP host variable defined by the JNDI resource in the server.xml(below). It does however register in the Context log (below) with the correct value. Exception Log ENCOUNTERED EXCEPTION: javax.mail.SendFailedException: Sending failed; nested exception is: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused: connect javax.mail.SendFailedException: Sending failed; nested exception is: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused: connect at javax.mail.Transport.send0(Transport.java:219) at javax.mail.Transport.send(Transport.java:81) at SendMailServlet.doPost(SendMailServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509)at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:376) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java:221) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) web.xml web-app display-nameROOT Context/display-name !-- Define servlets and Mappings -- servlet servlet-nameSendMailServlet/servlet-name servlet-classSendMailServlet/servlet-class /servlet servlet-mapping servlet-nameSendMailServlet/servlet-name url-pattern/SendMailServlet/url-pattern /servlet-mapping resource-ref res-ref-namemail/Session/res-ref-name res-typejavax.mail.Session/res-type res-authContainer/res-auth /resource-ref /web-app server.xml !-- ROOT Context -- Context debug=99 docBase=/ROOT path= reloadable=true source
Trying to remove the root context using the manager app
Hello everybody, I am trying to remove the root context using the manager application. First, I list all installed applications: http://www.xxx.de/manager/list OK - Listed applications for virtual host www.xxx.de /manager:running:0:../server/webapps/manager /:running:1:xxx Here are my 3 unsuccessful tries: http://www.xxx.de/manager/remove?path= FAIL - Invalid context path was specified http://www.xxx.de/manager/remove?path=/ FAIL - Encountered exception java.io.IOException: java.lang.NullPointerException http://www.xxx.de/manager/remove?path=ROOT FAIL - No context exists for path ROOT What am I doing wrong? Regards, Andreas P.S. I have substituted all references to my real domain name with xxx in this post. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
