RE: apache-tomcat4 connection via WARP

[Mark . Donoghue]

The web_app module must slap the trailing "/" on the deployment path.


This is my examples app taken from the WebAppInfo page.

==
Application Name:  "examples"
Root URL Path: "/examples/"
Local Deployment Path: "/path/catalina/webapps/examples"
Configuration Details: "Application ID: 2"
Connection:"conn" (details)
Deployed:  TRUE
==

And this is how I deployed it: 

WebAppDeploy examples  conn  /examples

I also get a 404 when I leave off the trailing slash in the URL.  I think it
happens because /examples is not in Apache's document root.  If it were,
Apache would see I requested a directory and issue a redirect to /examples/,
which is the standard behavior for web servers (that I've seen).  That's why
you can give the same URL to tomcat and get a directory listing (or index
page).

That's my theory so far.

-Mark



-Original Message-
From: Young Jun Kim [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 4:35 AM
To: [EMAIL PROTECTED]
Subject: apache-tomcat4 connection via WARP


i have apache+tomcat4 with WARP connector(mod_webapp.so).
everything works fine except one thing...

when i tried
http://hostname/examples/
default webpage (such as index.jsp, index.html) is displayed correctly.
but, when i tried
http://hostname/examples  <-- no slash(/)
i got internal error (500 error).

the strange thing is when i tried http://hostname:8080/examples
(when directly access to tomcat4) default page is displayed correctly.

other directories not connected to tomcat work fine.

does anyone know what's wrong this configuration? is this apache problem? or

tomcat4 problem?


_
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

mod_webapp and Tomcat tip

[Mark . Donoghue]

Hi,

This may be obvious but, it helped me.

Enabling the /webapp-info context as specified in the README file for
mod_webapp will tell you where it's looking for your Tomcat web apps:

Add this line:
WebAppInfo /webapp-info

to your Apache httpd.conf file.

Browsing http://host.com/webapp-info will tell you where mod_webapp is
looking.  The "Local Deployment Path" is where it's trying to access your
web apps.

Saved me some head scratching.

-Mark

.oO Mark Donoghue
.oO System Administrator
.oO S&T, Pearson Education
.oO mark[dot]donoghue[at]pearsoned[dot]com

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Contexts and automatic deployment

[Mark . Donoghue]

Hello,

Does having a context in my server.xml file preclude the ability to
auto-deploy a war file?

Here's why:  I have developers needing to deploy their web apps on our
development server.  They make a war file and drop it in place.

A problem occurs when a context is configured for their web app.  When they
delete their web app's directory, and the old war file Tomcat won't start
because it can't find the context's docBase.

Why do I have a context configured?  To allow for integration w/ Apache.

How do I get around this?  Does it make sense to do this?

Thanks,
Mark

.oO Mark Donoghue
.oO System Administrator
.oO S&T, Pearson Education
.oO mark[dot]donoghue[at]pearsoned[dot]com

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

RE: Tomcat4 not unpacking wars

[Mark . Donoghue]

Quick follow-up.  Turned out to be a badly-packaged war file.  Must throw it
back to the developers.

I tested by jar'ing the examples web-app and it unpacked OK.

Is there a war file validator?  How does tomcat validate war files?

Thanks,
Mark

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 27, 2001 2:54 PM
To: [EMAIL PROTECTED]
Subject: Tomcat4 not unpacking wars


Tomcat4 is not unpacking my wars on startup.  Do I have to configure it to
do this?  The following is the host element from my server.xml. Isn't this
right?


  


Thanks,

Jason E. Brawner



--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Tomcat4 not unpacking wars

[Mark . Donoghue]

Didn't see any responses to this.  I am having the same problem.

My Host element starts like this:



The appBase is not under the CATALINA_HOME directory and works fine if I
unpack the war files myself.

I run tomcat as user www, and www owns the above-referenced webapps
directory.  Oddly enough, when I start tomcat as root my war file is
unpacked but, owned by root :-( .

Has anyone solved a similar problem?

Thanks,
Mark


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 27, 2001 2:54 PM
To: [EMAIL PROTECTED]
Subject: Tomcat4 not unpacking wars


Tomcat4 is not unpacking my wars on startup.  Do I have to configure it to
do this?  The following is the host element from my server.xml. Isn't this
right?


  


Thanks,

Jason E. Brawner



--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: RE: can anyone help

[Mark . Donoghue]

Also, what is the output when you start Tomcat? -Mark

-Original Message-
From: Josh Knowles [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 03, 2002 2:39 PM
To: Tomcat Users List
Subject: RE: RE: can anyone help


Did you restart tomcat after changing the server.xml? 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 03, 2002 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: RE: can anyone help


yes, tomcat is running. tomcat is configured in server.xml to listen to
localhost:8080 however it still not working even if I change the
connectionport to say 8180 in server.xml

Liakim

> This may be a stupid question but, are you sure Tomcat is running when you
>try to hit it?  
>
>If it is then look in the server.xml file.  Look at the HTTP connector to
>see what port Tomcat is configured to listen to.
>
>-Mark
>
>-Original Message-
>From: Gerrit Kuilder [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, January 02, 2002 9:57 AM
>To: Tomcat Users List
>Subject: Re: can anyone help
>
>
>I am not sure if this is valid for windows but on linux/tomcat rpm's I 
>found that 4.01 ist listening on port 8180.
>
>Give it a try
>
>Regards,
>
>Gerrit
>
>[EMAIL PROTECTED] wrote:
>
> Hi everyone,
> 
> Can anyone help with a problem I am a having wtih starting tomcat.
> I have only started to learn java but I have ran into a few problems
>getting started.
> 
> I am running java on windows 98 on a laptop that also has  PWS installed. 
> 
> I have edited the autoexec.bat to include these two lines:
> 
> set JAVA_HOME=C:\jdk1.3.1_01
> set CATALINA_HOME=C:\Program Files\Apache Tomcat 4.0
> 
> however when I browse to localhost:8080 the page cannot be displayed and
>an error file is not been generated in the log directory.
> 
> does anyone know how to fix this?
> 
> many thanks
> 
> Liakim
> 
> 
> 
> 
> talk21 your FREE portable and private address on the net at
>http://www.
talk21.com
> 
> 
> 
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
> 
>
>
>
>--
>To unsubscribe:   
>For additional commands: 
>Troubles with the list: 
>
>--
>To unsubscribe:   
>For additional commands: 
>Troubles with the list: 




talk21 your FREE portable and private address on the net at
http://www.talk21.com



--
To unsubscribe:   
For additional commands: 
Troubles with the list: 


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: can anyone help

[Mark . Donoghue]

This may be a stupid question but, are you sure Tomcat is running when you
try to hit it?  

If it is then look in the server.xml file.  Look at the HTTP connector to
see what port Tomcat is configured to listen to.

-Mark

-Original Message-
From: Gerrit Kuilder [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 02, 2002 9:57 AM
To: Tomcat Users List
Subject: Re: can anyone help


I am not sure if this is valid for windows but on linux/tomcat rpm's I 
found that 4.01 ist listening on port 8180.

Give it a try

Regards,

Gerrit

[EMAIL PROTECTED] wrote:

> Hi everyone,
> 
> Can anyone help with a problem I am a having wtih starting tomcat.
> I have only started to learn java but I have ran into a few problems
getting started.
> 
> I am running java on windows 98 on a laptop that also has  PWS installed. 
> 
> I have edited the autoexec.bat to include these two lines:
> 
> set JAVA_HOME=C:\jdk1.3.1_01
> set CATALINA_HOME=C:\Program Files\Apache Tomcat 4.0
> 
> however when I browse to localhost:8080 the page cannot be displayed and
an error file is not been generated in the log directory.
> 
> does anyone know how to fix this?
> 
> many thanks
> 
> Liakim
> 
> 
> 
> 
> talk21 your FREE portable and private address on the net at
http://www.talk21.com
> 
> 
> 
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
> 



--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Tomcat shutdown problems

[Mark . Donoghue]

Mav,

I had a similar error upon startup.  I switched from java 1.2.1 to java
1.3.1 and it healed.

-Mark

-Original Message-
From: Mav Rck [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 30, 2001 7:32 PM
To: [EMAIL PROTECTED]
Subject: Tomcat shutdown problems


When I try to shutdown Tomcat I get the following error

./catalina.sh: line 234: 18818 Segmentation fault $JAVA_HOME/bin/java 
$CATALINA_OPTS -classpath $CP -Dcatalina.base=$CATALINA_BASE 
-Dcatalina.home=$CATALINA_HOME org.apache.catalina.startup.Bootstrap "$@" 
stop

Can anyone help me figure out what the problem is. ANy help is greatly 
appreciated

Thanks,
Mav

_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: problem with multiple instances on Tomcat 4.0.1

[Mark . Donoghue]

dj,

Did you change all of the port assignments?  I ran into the same problem and
found I hadn't changed the port for the tomcat server :


I had just changed the HTTP connector port.

Search for "port" in the server.xml file and see where it's being assigned.

Good luck,
-Mark


-Original Message-
From: Dong Jiang [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 31, 2001 8:08 AM
To: [EMAIL PROTECTED]
Subject: problem with multiple instances on Tomcat 4.0.1


Hi,

I installed Tomcat4.0.1 on a Solaris box. I try to
start multiple instances on different port according
to the installation instruction. However, I found that
I can only start one instance at the one port, the
other instances, although set to start at different
ports by server.xml, has address in use error.
Anyone has the same experience or help me on this will
be greatly appreciated.

dj

__
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Clarification needed, please

[Mark . Donoghue]

Ahh. OK.  I'm mixing things together when I shouldn't.

Isn't it unfortunate you learn most after putting your foot in your mouth?
I suppose more unfortunate is not learning anything afterward.

Thanks,
-Mark

-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 26, 2001 2:10 PM
To: Tomcat Users List
Subject: RE: Clarification needed, please




On Wed, 26 Dec 2001 [EMAIL PROTECTED] wrote:

> Date: Wed, 26 Dec 2001 12:09:12 -0500
> From: [EMAIL PROTECTED]
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: Clarification needed, please
>
>
>
> -Original Message-
> From: Randy Layman [mailto:[EMAIL PROTECTED]]
> 
>
> > -Original Message-
> > From: Nikola Milutinovic [mailto:[EMAIL PROTECTED]]
>
> 
>
> > If Tomcat gets two requests, handled by the same servlet,
> > will the same instance of that servlet handle it?
> Yes.  Tomcat will always create exactly one instance of a servlet
> for each unique URL that can access it (i.e. two servlet mappings
> equals two instances).
>
> Doesn't this depend upon how the servlet is scoped?  Tomcat will compile
one
> jsp per *.jsp file but instantiates the servlet differently according to
the
> servlet's scope being either application, session, or request.
>

Not really.  *Servlets* are not scoped -- only attributes (i.e. beans).

> Randy is explaining application scope.  You get one instance of the
servlet
> and state is maintained across all accesses.
>
> Session scope will maintain state for the duration of an http session and
> request scope will give you a new servlet for each request with no memory
> shared (and no shared memory) between requests.
>
> >From what I understand of the Servlet Spec. a servlet must be contained
> within one instance of a JVM (because of concurrency issues) but, that is
> not related to the servlet scope which pertains to the semantics of your
web
> application.
>

You don't have it quite right.  Servlet instance lifecycle information is
defined in Section 2 of the Servlet 2.3 specification, which doesn't have
anything to do with scopes.

Scopes (in the JSP vocabulary) match up to servlet concepts like this:

* "application scope" beans == ServletContext attributes
* "session scope" beans == HttpSession attributes
* "request scope" beans == ServletRequest attributes
* "page scope" beans do not have a direct analog in the Servlet API --
  but they act more like local variables in the doGet() or doPost()
  method than anything else.

> That's kinda how I've been understanding it.  Please correct me if I'm
> wrong.
>
> -Mark
>

Craig McClanahan


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Clarification needed, please

[Mark . Donoghue]

-Original Message-
From: Randy Layman [mailto:[EMAIL PROTECTED]]


> -Original Message-
> From: Nikola Milutinovic [mailto:[EMAIL PROTECTED]]



> If Tomcat gets two requests, handled by the same servlet, 
> will the same instance of that servlet handle it?
Yes.  Tomcat will always create exactly one instance of a servlet
for each unique URL that can access it (i.e. two servlet mappings 
equals two instances).

Doesn't this depend upon how the servlet is scoped?  Tomcat will compile one
jsp per *.jsp file but instantiates the servlet differently according to the
servlet's scope being either application, session, or request.

Randy is explaining application scope.  You get one instance of the servlet
and state is maintained across all accesses.

Session scope will maintain state for the duration of an http session and
request scope will give you a new servlet for each request with no memory
shared (and no shared memory) between requests.

>From what I understand of the Servlet Spec. a servlet must be contained
within one instance of a JVM (because of concurrency issues) but, that is
not related to the servlet scope which pertains to the semantics of your web
application.

That's kinda how I've been understanding it.  Please correct me if I'm
wrong.

-Mark

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Tomcat fails to start...

[Mark . Donoghue]

Jack,

Looks like a CLASSPATH issue.  It usually helps to set the CLASSPATH in the
startup.sh file yourself. Look at the tomcat.sh file to see what tomcat
needs and set it in startup.sh.

I usually put everything I think tomcat will need on the classpath.  It
works better than letting tomcat do it itself.  In your case it looks like
tomcat can't find its own classes or something from java's rt.jar (or your
system's equivalent).

Good luck,
Mark



-Original Message-
From: Jack Lauman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 25, 2001 5:37 PM
To: Tomcat Developers List; Tomcat User List
Subject: Tomcat fails to start...


Tomcat 4.x (CVS 12-25-2001) fails to start.

I'm using the following configuration:

RedHat 7.0 (glibc 2.2.4-18.7.0.3)
jdk1.3.1_02
commons-utils-1.1
commons-collections-1.0
commons-digester-1.1.1
commons-dbcp-20011222
commons-modeler-20011222
commons-pool-20011222
crimson-1.1.3
xerces-1.4.4

I got the following error when executing $CATALINA_HOME/bin/startup.sh
and would appreciate any assistance in resolving it.

Thanks,

Jack

End event threw exception
java.lang.ClassNotFoundException:
org.apache.catalina.ServerSocketFactory
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:992)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:857)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:155)
at
org.apache.commons.digester.Digester.endElement(Digester.java:757)
at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator
.java:1550)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java:1809)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1182)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at org.apache.commons.digester.Digester.parse(Digester.java:1170)
at org.apache.catalina.startup.Catalina.start(Catalina.java:444)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:399)
at org.apache.catalina.startup.Catalina.process(Catalina.java:178)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:246)
Catalina.start: java.lang.ClassNotFoundException:
org.apache.catalina.ServerSocketFactory
java.lang.ClassNotFoundException:
org.apache.catalina.ServerSocketFactory
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:1763)
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:1785)
at
org.apache.commons.digester.Digester.endElement(Digester.java:760)
at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator
.java:1550)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java:1809)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1182)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at org.apache.commons.digester.Digester.parse(Digester.java:1170)
at org.apache.catalina.startup.Catalina.start(Catalina.java:444)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:399)
at org.apache.catalina.startup.Catalina.process(Catalina.java:178)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:246)

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: