Re: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Matt
Well, I've tried all sorts of configurations, so I was hoping to get a
clean example from someone who had it working.  I changed the stock Tomcat
5.5 server.xml file to add the following (within the pre-existing, as well
as the only, HOST tag for localhost, and I have tried with/without a slash
for path, and with forward or backward slashes in docbase):
CONTEXT path= docbase=C:/Inetpub/wwwroot/MYwebapps debug=0
reloadable=true /
...and I have edited the stock Tomcat 5.5 uriworkermap.properties file to
add the directory relative to the additional docbase (I've also tried
without the .jsp specificity at the end of the line to handle everything):
/MYjsp-examples/*.jsp
(the jk_1.2.8.exe installer puts it all in its own folders in
$CATALINA_HOME's parent, not within $CATALINA_HOME/bin, and also sets the
registry properly - anything else this nice installer does for me?  It
doesn't appear to set environment variables $CATALINA_HOME or JAVA_HOME -
do I need to do this manually?  The webapps examples work fine without
these variables set though, so is this a deprecated step?)

So, if I have copied the webapps folder (and everything in it) to the
C:\Inetpub\wwwroot folder and renamed it MYwebapps, and renamed
jsp-examples therein to be MYjsp-examples (and fixed the .html to point to
the right path), I would have thought that I could run examples from the
new directory as well.  I don't see any path info. (non-relative)
elsewhere that would cause problems and need to be changed?  However, if
uriworkermap.properties is edited properly, I get a Tomcat 404 error
starting with the docbase, when clicking any example (.jsp link; the .html
ones still work fine, since they're not handed-off to Tomcat) from the
main page:
http://localhost/MYwebapps/MYjsp-examples/index.html
...the same files still work fine if I go back to the original location:
http://localhost/jsp-examples

I've even tried making new HOST tags as well, but Tomcat won't start if
you try to define two HOST tags for the same system whether I use a
machine name, IP or whatever.

Perhaps I misread the docs somewhere, or there's more to it than the above
two steps, I'd love to know!

Thanks,
-Matt


On Tue, 22 Feb 2005, Michael Greer wrote:

 Why don't you show us your config file. This behavior work fine for me
 with 5.5.7, with Apache  mod_jk.

 On Feb 22, 2005, at 1:20 AM, Matt wrote:

  Is this simply not possible?  I have tried extrapolating form the docs
  (which seems to work fine under webapps/ or $CATALINA_HOME) but
  anything
  outside of it fails as badly as the other works perfectly, even if I
  try
  to swap-out webapps/ for an otuside docbase using the HOST tag
  already
  present.
 
  There's got to be a file or simple edit that I'm missing for this?
  Anyone?
 
  Thanks,
  -Matt
 
 
  On Sun, 20 Feb 2005, Matt wrote:
 
  OK, the docs out there are good, but they either concern old versions
  of
  IIS and/or Tomcat -OR- they concern the JK2 module (including this
  list's
  archives I have searched).
  If JK2 is NO LONGER SUPPORTED, why in the heck would I care to use it?
  So, I am using the very nice jk_1.2.8.exe installer.  With that, most
  of
  the steps found in the various, partially-helpful docs are already
  done!
  ;^)
 
  That said:
  I am using Win2K + IIS5, and also Win2K3 + IIS6, and in either case,
  also
  Tomcat 5.5:
  I can go to http://localhost and get my IIS index page.
  I can go to http://localhost:8080 and get my Tomcat index page.
  I can go to http://localhost/jsp-examples/index.html and run all the
  wonderful examples.
  HOWEVER, if I simply want to -ALSO- hand-off jsp pages to Tomcat that
  are
  in C:\Inetpub\wwwroot (and below) everything goes to hell.
 
  I have tried adding CONTEXT tags to server.xml until I turn blue in
  the
  face, and when I do so I get either 404 not found errors from Tomcat
  (can't find the subdirectory b/c I assume it is looking for it in
  webapps/, but then again it can't find it even if I copy the whole
  thing
  into webapps/) or The specified module could not be found message
  on the
  page (IIS result of a uriworkermap.properties issue).
  I have even tried editing the existing HOST tag to change webapps
  to C:/Inetpub/wwwroot and all sorts of folders below wwwroot.  In
  those
  cases, if I manage to edit the uriworkermap.properties file
  correctly, all
  I get is a blank page for any .jsp, while IIS still handles the other
  stuff just fine.
 
  So, instead of these outdated docs everyone keeps pointing to, does
  anyone
  have any simple instructions to get Tomcat to properly use a folder
  OUTSIDE of webapps, and ALONG WITH webapps to work (especially
  assuming
  you've already got the basics working just fine as I do)?
  I'd like to start by getting a copy of jsp-examples working in
  wwwroot/ if
  possible (which is also how I was testing in the situation above, if
  that
  means anything), rather than also confusing the situation by learning
  how to create apps myself at 

Re: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Michael Greer
Maybe take a look at the current $CATALINA_HOME/Catalina/localhost/  
context files. Delete the old ones for your webapp and examples, so it  
will reload from server.xml

On Feb 22, 2005, at 11:39 AM, Matt wrote:
Well, I've tried all sorts of configurations, so I was hoping to get a
clean example from someone who had it working.  I changed the stock  
Tomcat
5.5 server.xml file to add the following (within the pre-existing, as  
well
as the only, HOST tag for localhost, and I have tried with/without a  
slash
for path, and with forward or backward slashes in docbase):
CONTEXT path= docbase=C:/Inetpub/wwwroot/MYwebapps debug=0
reloadable=true /
...and I have edited the stock Tomcat 5.5 uriworkermap.properties file  
to
add the directory relative to the additional docbase (I've also tried
without the .jsp specificity at the end of the line to handle  
everything):
/MYjsp-examples/*.jsp
(the jk_1.2.8.exe installer puts it all in its own folders in
$CATALINA_HOME's parent, not within $CATALINA_HOME/bin, and also sets  
the
registry properly - anything else this nice installer does for me?  It
doesn't appear to set environment variables $CATALINA_HOME or  
JAVA_HOME -
do I need to do this manually?  The webapps examples work fine without
these variables set though, so is this a deprecated step?)

So, if I have copied the webapps folder (and everything in it) to the
C:\Inetpub\wwwroot folder and renamed it MYwebapps, and renamed
jsp-examples therein to be MYjsp-examples (and fixed the .html to  
point to
the right path), I would have thought that I could run examples from  
the
new directory as well.  I don't see any path info. (non-relative)
elsewhere that would cause problems and need to be changed?  However,  
if
uriworkermap.properties is edited properly, I get a Tomcat 404 error
starting with the docbase, when clicking any example (.jsp link; the  
.html
ones still work fine, since they're not handed-off to Tomcat) from the
main page:
http://localhost/MYwebapps/MYjsp-examples/index.html
...the same files still work fine if I go back to the original  
location:
http://localhost/jsp-examples

I've even tried making new HOST tags as well, but Tomcat won't start if
you try to define two HOST tags for the same system whether I use a
machine name, IP or whatever.
Perhaps I misread the docs somewhere, or there's more to it than the  
above
two steps, I'd love to know!

Thanks,
-Matt
On Tue, 22 Feb 2005, Michael Greer wrote:
Why don't you show us your config file. This behavior work fine for me
with 5.5.7, with Apache  mod_jk.
On Feb 22, 2005, at 1:20 AM, Matt wrote:
Is this simply not possible?  I have tried extrapolating form the  
docs
(which seems to work fine under webapps/ or $CATALINA_HOME) but
anything
outside of it fails as badly as the other works perfectly, even if I
try
to swap-out webapps/ for an otuside docbase using the HOST tag
already
present.

There's got to be a file or simple edit that I'm missing for this?
Anyone?
Thanks,
-Matt
On Sun, 20 Feb 2005, Matt wrote:
OK, the docs out there are good, but they either concern old  
versions
of
IIS and/or Tomcat -OR- they concern the JK2 module (including this
list's
archives I have searched).
If JK2 is NO LONGER SUPPORTED, why in the heck would I care to use  
it?
So, I am using the very nice jk_1.2.8.exe installer.  With that,  
most
of
the steps found in the various, partially-helpful docs are already
done!
;^)

That said:
I am using Win2K + IIS5, and also Win2K3 + IIS6, and in either case,
also
Tomcat 5.5:
I can go to http://localhost and get my IIS index page.
I can go to http://localhost:8080 and get my Tomcat index page.
I can go to http://localhost/jsp-examples/index.html and run all the
wonderful examples.
HOWEVER, if I simply want to -ALSO- hand-off jsp pages to Tomcat  
that
are
in C:\Inetpub\wwwroot (and below) everything goes to hell.

I have tried adding CONTEXT tags to server.xml until I turn blue in
the
face, and when I do so I get either 404 not found errors from Tomcat
(can't find the subdirectory b/c I assume it is looking for it in
webapps/, but then again it can't find it even if I copy the whole
thing
into webapps/) or The specified module could not be found message
on the
page (IIS result of a uriworkermap.properties issue).
I have even tried editing the existing HOST tag to change webapps
to C:/Inetpub/wwwroot and all sorts of folders below wwwroot.  In
those
cases, if I manage to edit the uriworkermap.properties file
correctly, all
I get is a blank page for any .jsp, while IIS still handles the  
other
stuff just fine.

So, instead of these outdated docs everyone keeps pointing to, does
anyone
have any simple instructions to get Tomcat to properly use a folder
OUTSIDE of webapps, and ALONG WITH webapps to work (especially
assuming
you've already got the basics working just fine as I do)?
I'd like to start by getting a copy of jsp-examples working in
wwwroot/ if
possible (which is also how I was testing in the situation above, if

RE: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Wendy . Olson
Hi Matt,

I'm not sure if this would solve your problem, but I have my server.xml set up 
with the following configuration:


Host name=localhost debug=0 appBase=webapps/myApp
unpackWARs=false autoDeploy=true
xmlValidation=true xmlNamespaceAware=true

Context path= docBase= debug=0 reloadable=true crossContext=true 
/

!-- context path for external ini directory -- 
Context path=/ini docBase=c:\\myApp\c\releases\ini debug=0
 reloadable=true crossContext=false /

!-- context path for external lib directory -- 
Context path=/lib docBase=c:\\myApp\c\releases\lib debug=0
 reloadable=true crossContext=false /

/Host


This means my root webapp for http://localhost resolves to webapps/myApp, and 
the http://localhost/ini url goes to c:\\koba\c\releases\ini, etc.

When we first set this up Tomcat had problems starting up because it was 
reading in old web.xml files under the Tomcat/conf/Catalina... dir(s) but it 
couldn't find that path under Tomcat/webapps/myApp/.  So we had to remove those 
old xml files (since the localhost root no longer went to Tomcat/webapps/).


As a test, I just tried directing my Host's appBase to an external directory, 
and it worked for me.  For that test I configured server.xml per the following:

Host name=localhost debug=0 appBase=c:\\myApp\c\releases\ini
  unpackWARs=false autoDeploy=true
  xmlValidation=true xmlNamespaceAware=true

  Context path= docBase= debug=0 reloadable=true 
crossContext=true /

/Host


I am running Tomcat 5.0.25.
- Wendy

p.s. The Apache webserver allows you to manage aliases and the like better, if 
you're in a position to install that in front of Tomcat.


-Original Message-
From: Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 22, 2005 11:40 AM
To: Tomcat Users List
Subject: Re: Tomcat 5.5 working, BUT not outside of webapps/


Well, I've tried all sorts of configurations, so I was hoping to get a
clean example from someone who had it working.  I changed the stock Tomcat
5.5 server.xml file to add the following (within the pre-existing, as well
as the only, HOST tag for localhost, and I have tried with/without a slash
for path, and with forward or backward slashes in docbase):
CONTEXT path= docbase=C:/Inetpub/wwwroot/MYwebapps debug=0
reloadable=true /
...and I have edited the stock Tomcat 5.5 uriworkermap.properties file to
add the directory relative to the additional docbase (I've also tried
without the .jsp specificity at the end of the line to handle everything):
/MYjsp-examples/*.jsp
(the jk_1.2.8.exe installer puts it all in its own folders in
$CATALINA_HOME's parent, not within $CATALINA_HOME/bin, and also sets the
registry properly - anything else this nice installer does for me?  It
doesn't appear to set environment variables $CATALINA_HOME or JAVA_HOME -
do I need to do this manually?  The webapps examples work fine without
these variables set though, so is this a deprecated step?)

So, if I have copied the webapps folder (and everything in it) to the
C:\Inetpub\wwwroot folder and renamed it MYwebapps, and renamed
jsp-examples therein to be MYjsp-examples (and fixed the .html to point to
the right path), I would have thought that I could run examples from the
new directory as well.  I don't see any path info. (non-relative)
elsewhere that would cause problems and need to be changed?  However, if
uriworkermap.properties is edited properly, I get a Tomcat 404 error
starting with the docbase, when clicking any example (.jsp link; the .html
ones still work fine, since they're not handed-off to Tomcat) from the
main page:
http://localhost/MYwebapps/MYjsp-examples/index.html
...the same files still work fine if I go back to the original location:
http://localhost/jsp-examples

I've even tried making new HOST tags as well, but Tomcat won't start if
you try to define two HOST tags for the same system whether I use a
machine name, IP or whatever.

Perhaps I misread the docs somewhere, or there's more to it than the above
two steps, I'd love to know!

Thanks,
-Matt


On Tue, 22 Feb 2005, Michael Greer wrote:

 Why don't you show us your config file. This behavior work fine for me
 with 5.5.7, with Apache  mod_jk.

 On Feb 22, 2005, at 1:20 AM, Matt wrote:

  Is this simply not possible?  I have tried extrapolating form the docs
  (which seems to work fine under webapps/ or $CATALINA_HOME) but
  anything
  outside of it fails as badly as the other works perfectly, even if I
  try
  to swap-out webapps/ for an otuside docbase using the HOST tag
  already
  present.
 
  There's got to be a file or simple edit that I'm missing for this?
  Anyone?
 
  Thanks,
  -Matt
 
 
  On Sun, 20 Feb 2005, Matt wrote:
 
  OK, the docs out there are good, but they either concern old versions
  of
  IIS

Re: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Matt
The original $CATALINA_HOME/webapps works fine, yes, but nothing will work
outside of that, so I'm just looking for the steps (and files I need to
edit) to have my own webapps work outside of $CATALINA_HOME/webapps.
That's all - it's quite simple, really.  C:\Inetpub\wwwroot is just a
sample path on my Windows box, so how would I get Tomcat to also work on
files in there, not just $CATALINA_HOME/webapps?  The CONTEXT tag below is
one sample of what I've tried (in server.xml), but it does *not* work.  I
have also edited uriworkermap.properties, but when I do that, Tomcat says
it can't find any resources in that location, so the issue is how to
setup another web applications area/folder/directory properly,
step-by-step, file-by-file.  It seems it shouldn't take more than 5 steps
at most, no?

If it helps, recall that I have setup Tomcat, jk_1.2.8 and my web server
up out of the box and they work just fine with the stock usage and I can
run jsp-examples, BUT I now want to *add* another location besides
$CATALINA_HOME/webapps and have jsp files and servlets work in there as
well, and that location could be (for example's sake) C:\Inetpub\wwwroot
(and anywhere below).

You threw me off when you mentioned $CATALINA_HOME/Catalina/host/some
file, b/c I *do* have $CATALINA_HOME/localhost/manager.xml, but am
completely clueless as to what that file has to do with server.xml.  You
say I have to delete it to have any of my changes in server.xml to
actually take?  That's the clarification I was looking for, but if I can
address the original issue above (whether it includes this as part of it
ot not) then that'd be the solution with which I'm struggling.

Thanks,
-Matt


On Tue, 22 Feb 2005, Michael Greer wrote:

 Ah, I see the problem ! It is working fine, and following your config:
  CONTEXT path= docbase=C:/Inetpub/wwwroot/MYwebapps debug=0
  reloadable=true /

 The path says how to access the context (ie, the URL path from the
 root of the serv).

 Maybe I'm wrong. I can't keep track of what works and does not in your
 issue. If you can reach the apps at the old address, then the docbase
 property works.

 On Feb 22, 2005, at 2:55 PM, Matt wrote:

  There is a folder called localhost and in there is manager.xml
  Do I destroy this folder and file?  SOmeone had mentioned adding a
  site.xml file in there, and I didn;t see anything in the docs re: this
  in
  terms of adding contexts?
 
  Thanks for clarifying,
  -Matt


Matthew Kozak
Rutgers University-Camden
[EMAIL PROTECTED]

**
 They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.  -Ben Franklin
**

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Matt
OK, we've at least gotten to the point where I can now run the examples
from my own directory outside of $CATALINA_HOME/webapps, and by ONLY
editing server.xml and uriworkermap.properties slightly, and NOTHING
ELSE, which is not only nice, but also what I expected all along!
(THANK YOU!THANK YOU!THANK YOU!)*

*HOWEVER, now that I made the changes you recommended, the webapps area
now is NOT FOUND when using plain URL's.  I get a (Tomcat-based) directory
listing when using the following URL (instead of the Tomcat welcome page):
http://localhost:8080
...which includes my outside folder and then all of the folders in
$CATALINA_HOME/webapps, AND if I go deeper into any of these listed
directories with the explicit port :8080 set it works, BUT if I try the
following URL:
http://localhost/jsp-examples
...then I get a 404 page not found error (not a Tomcat page - standard
IE stuff).
With or without the :8080 port in my URL, my outside directory can be
found just fine:
http://localhost/JSP/MYwebapps/MYjsp-examples/index.html (and so on)
...so I have the inverse problem.
Good grief!  Can't we have both?

Here's the beginning of my HOST tag through the CONTEXT (everything else
in server.xml is out-of-the-box, unless jk_1.2.8.exe does anything here as
well):
  Host name=localhost appBase=webapps
   unpackWARs=true autoDeploy=true
   xmlValidation=false xmlNamespaceAware=false

   Context path= docBase= debug=0 reloadable=true
crossContext=true /

   Context path=/JSP docbase=C:/Inetpub/wwwroot/JSP debug=0
reloadable=true crossContext=false /

...the trick seems to be in the overlapping ending directory in path and
docbase, which is kinda annoying since EVERY example I found showed path
set to  or / - hence my frustration up to this point.  I have tried
removing the first CONTEXT (seems weird with path and docbase both set to
).  When I remove that, I get the same results - so what is this CONTEXT
for, if anything?

My uriworkermap.properties file is as follows:
# uriworker.properties -
#
# This file provides sample mappings for example
# ajp13w worker defined in workermap.properties.minimal

/servlets-examples/*=ajp13w
/jsp-examples/*.jsp=ajp13w
/*.jsp=ajp13w
/JSP/*.jsp=ajp13w

# Now filter out all .jpeg files inside that context
# For no mapping the url has to start with exclamation (!)

!/servlets-examples/*.jpeg=ajp13w

So, I'm still trying to get BOTH to work right, but making some progress!
-Matt


On Tue, 22 Feb 2005 [EMAIL PROTECTED] wrote:

 Hi Matt,

 I'm not sure if this would solve your problem, but I have my server.xml set 
 up with the following configuration:

 
 Host name=localhost debug=0 appBase=webapps/myApp
 unpackWARs=false autoDeploy=true
 xmlValidation=true xmlNamespaceAware=true

 Context path= docBase= debug=0 reloadable=true 
 crossContext=true /

 !-- context path for external ini directory --
 Context path=/ini docBase=c:\\myApp\c\releases\ini debug=0
  reloadable=true crossContext=false /

 !-- context path for external lib directory --
 Context path=/lib docBase=c:\\myApp\c\releases\lib debug=0
  reloadable=true crossContext=false /

 /Host
 

 This means my root webapp for http://localhost resolves to webapps/myApp, and 
 the http://localhost/ini url goes to c:\\koba\c\releases\ini, etc.

 When we first set this up Tomcat had problems starting up because it was 
 reading in old web.xml files under the Tomcat/conf/Catalina... dir(s) but it 
 couldn't find that path under Tomcat/webapps/myApp/.  So we had to remove 
 those old xml files (since the localhost root no longer went to 
 Tomcat/webapps/).


 As a test, I just tried directing my Host's appBase to an external directory, 
 and it worked for me.  For that test I configured server.xml per the 
 following:

 Host name=localhost debug=0 appBase=c:\\myApp\c\releases\ini
   unpackWARs=false autoDeploy=true
   xmlValidation=true xmlNamespaceAware=true

   Context path= docBase= debug=0 reloadable=true 
 crossContext=true /

 /Host


 I am running Tomcat 5.0.25.
 - Wendy

 p.s. The Apache webserver allows you to manage aliases and the like better, 
 if you're in a position to install that in front of Tomcat.


 -Original Message-
 From: Matt [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, February 22, 2005 11:40 AM
 To: Tomcat Users List
 Subject: Re: Tomcat 5.5 working, BUT not outside of webapps/


 Well, I've tried all sorts of configurations, so I was hoping to get a
 clean example from someone who had it working.  I changed the stock Tomcat
 5.5 server.xml file to add the following (within the pre-existing, as well
 as the only, HOST tag for localhost, and I have tried with/without a slash
 for path, and with forward or backward slashes in docbase):
 CONTEXT path= docbase=C:/Inetpub

RE: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Matt
 up because it was 
  reading in old web.xml files under the Tomcat/conf/Catalina... dir(s) but 
  it couldn't find that path under Tomcat/webapps/myApp/.  So we had to 
  remove those old xml files (since the localhost root no longer went to 
  Tomcat/webapps/).
 
 
  As a test, I just tried directing my Host's appBase to an external 
  directory, and it worked for me.  For that test I configured server.xml per 
  the following:
 
  Host name=localhost debug=0 appBase=c:\\myApp\c\releases\ini
unpackWARs=false autoDeploy=true
xmlValidation=true xmlNamespaceAware=true
 
Context path= docBase= debug=0 reloadable=true 
  crossContext=true /
 
  /Host
 
 
  I am running Tomcat 5.0.25.
  - Wendy
 
  p.s. The Apache webserver allows you to manage aliases and the like better, 
  if you're in a position to install that in front of Tomcat.
 
 
  -Original Message-
  From: Matt [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, February 22, 2005 11:40 AM
  To: Tomcat Users List
  Subject: Re: Tomcat 5.5 working, BUT not outside of webapps/
 
 
  Well, I've tried all sorts of configurations, so I was hoping to get a
  clean example from someone who had it working.  I changed the stock Tomcat
  5.5 server.xml file to add the following (within the pre-existing, as well
  as the only, HOST tag for localhost, and I have tried with/without a slash
  for path, and with forward or backward slashes in docbase):
  CONTEXT path= docbase=C:/Inetpub/wwwroot/MYwebapps debug=0
  reloadable=true /
  ...and I have edited the stock Tomcat 5.5 uriworkermap.properties file to
  add the directory relative to the additional docbase (I've also tried
  without the .jsp specificity at the end of the line to handle everything):
  /MYjsp-examples/*.jsp
  (the jk_1.2.8.exe installer puts it all in its own folders in
  $CATALINA_HOME's parent, not within $CATALINA_HOME/bin, and also sets the
  registry properly - anything else this nice installer does for me?  It
  doesn't appear to set environment variables $CATALINA_HOME or JAVA_HOME -
  do I need to do this manually?  The webapps examples work fine without
  these variables set though, so is this a deprecated step?)
 
  So, if I have copied the webapps folder (and everything in it) to the
  C:\Inetpub\wwwroot folder and renamed it MYwebapps, and renamed
  jsp-examples therein to be MYjsp-examples (and fixed the .html to point to
  the right path), I would have thought that I could run examples from the
  new directory as well.  I don't see any path info. (non-relative)
  elsewhere that would cause problems and need to be changed?  However, if
  uriworkermap.properties is edited properly, I get a Tomcat 404 error
  starting with the docbase, when clicking any example (.jsp link; the .html
  ones still work fine, since they're not handed-off to Tomcat) from the
  main page:
  http://localhost/MYwebapps/MYjsp-examples/index.html
  ...the same files still work fine if I go back to the original location:
  http://localhost/jsp-examples
 
  I've even tried making new HOST tags as well, but Tomcat won't start if
  you try to define two HOST tags for the same system whether I use a
  machine name, IP or whatever.
 
  Perhaps I misread the docs somewhere, or there's more to it than the above
  two steps, I'd love to know!
 
  Thanks,
  -Matt
 
 
  On Tue, 22 Feb 2005, Michael Greer wrote:
 
   Why don't you show us your config file. This behavior work fine for me
   with 5.5.7, with Apache  mod_jk.
  
   On Feb 22, 2005, at 1:20 AM, Matt wrote:
  
Is this simply not possible?  I have tried extrapolating form the docs
(which seems to work fine under webapps/ or $CATALINA_HOME) but
anything
outside of it fails as badly as the other works perfectly, even if I
try
to swap-out webapps/ for an otuside docbase using the HOST tag
already
present.
   
There's got to be a file or simple edit that I'm missing for this?
Anyone?
   
Thanks,
-Matt
   
   
On Sun, 20 Feb 2005, Matt wrote:
   
OK, the docs out there are good, but they either concern old versions
of
IIS and/or Tomcat -OR- they concern the JK2 module (including this
list's
archives I have searched).
If JK2 is NO LONGER SUPPORTED, why in the heck would I care to use it?
So, I am using the very nice jk_1.2.8.exe installer.  With that, most
of
the steps found in the various, partially-helpful docs are already
done!
;^)
   
That said:
I am using Win2K + IIS5, and also Win2K3 + IIS6, and in either case,
also
Tomcat 5.5:
I can go to http://localhost and get my IIS index page.
I can go to http://localhost:8080 and get my Tomcat index page.
I can go to http://localhost/jsp-examples/index.html and run all the
wonderful examples.
HOWEVER, if I simply want to -ALSO- hand-off jsp pages to Tomcat that
are
in C:\Inetpub\wwwroot (and below) everything goes to hell.
   
I have tried adding CONTEXT tags

RE: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-22 Thread Matt
 to 
   Tomcat/webapps/).
  
  
   As a test, I just tried directing my Host's appBase to an external 
   directory, and it worked for me.  For that test I configured server.xml 
   per the following:
  
   Host name=localhost debug=0 appBase=c:\\myApp\c\releases\ini
 unpackWARs=false autoDeploy=true
 xmlValidation=true xmlNamespaceAware=true
  
 Context path= docBase= debug=0 reloadable=true 
   crossContext=true /
  
   /Host
  
  
   I am running Tomcat 5.0.25.
   - Wendy
  
   p.s. The Apache webserver allows you to manage aliases and the like 
   better, if you're in a position to install that in front of Tomcat.
  
  
   -Original Message-
   From: Matt [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, February 22, 2005 11:40 AM
   To: Tomcat Users List
   Subject: Re: Tomcat 5.5 working, BUT not outside of webapps/
  
  
   Well, I've tried all sorts of configurations, so I was hoping to get a
   clean example from someone who had it working.  I changed the stock Tomcat
   5.5 server.xml file to add the following (within the pre-existing, as well
   as the only, HOST tag for localhost, and I have tried with/without a slash
   for path, and with forward or backward slashes in docbase):
   CONTEXT path= docbase=C:/Inetpub/wwwroot/MYwebapps debug=0
   reloadable=true /
   ...and I have edited the stock Tomcat 5.5 uriworkermap.properties file to
   add the directory relative to the additional docbase (I've also tried
   without the .jsp specificity at the end of the line to handle everything):
   /MYjsp-examples/*.jsp
   (the jk_1.2.8.exe installer puts it all in its own folders in
   $CATALINA_HOME's parent, not within $CATALINA_HOME/bin, and also sets the
   registry properly - anything else this nice installer does for me?  It
   doesn't appear to set environment variables $CATALINA_HOME or JAVA_HOME -
   do I need to do this manually?  The webapps examples work fine without
   these variables set though, so is this a deprecated step?)
  
   So, if I have copied the webapps folder (and everything in it) to the
   C:\Inetpub\wwwroot folder and renamed it MYwebapps, and renamed
   jsp-examples therein to be MYjsp-examples (and fixed the .html to point to
   the right path), I would have thought that I could run examples from the
   new directory as well.  I don't see any path info. (non-relative)
   elsewhere that would cause problems and need to be changed?  However, if
   uriworkermap.properties is edited properly, I get a Tomcat 404 error
   starting with the docbase, when clicking any example (.jsp link; the .html
   ones still work fine, since they're not handed-off to Tomcat) from the
   main page:
   http://localhost/MYwebapps/MYjsp-examples/index.html
   ...the same files still work fine if I go back to the original location:
   http://localhost/jsp-examples
  
   I've even tried making new HOST tags as well, but Tomcat won't start if
   you try to define two HOST tags for the same system whether I use a
   machine name, IP or whatever.
  
   Perhaps I misread the docs somewhere, or there's more to it than the above
   two steps, I'd love to know!
  
   Thanks,
   -Matt
  
  
   On Tue, 22 Feb 2005, Michael Greer wrote:
  
Why don't you show us your config file. This behavior work fine for me
with 5.5.7, with Apache  mod_jk.
   
On Feb 22, 2005, at 1:20 AM, Matt wrote:
   
 Is this simply not possible?  I have tried extrapolating form the docs
 (which seems to work fine under webapps/ or $CATALINA_HOME) but
 anything
 outside of it fails as badly as the other works perfectly, even if I
 try
 to swap-out webapps/ for an otuside docbase using the HOST tag
 already
 present.

 There's got to be a file or simple edit that I'm missing for this?
 Anyone?

 Thanks,
 -Matt


 On Sun, 20 Feb 2005, Matt wrote:

 OK, the docs out there are good, but they either concern old versions
 of
 IIS and/or Tomcat -OR- they concern the JK2 module (including this
 list's
 archives I have searched).
 If JK2 is NO LONGER SUPPORTED, why in the heck would I care to use 
 it?
 So, I am using the very nice jk_1.2.8.exe installer.  With that, most
 of
 the steps found in the various, partially-helpful docs are already
 done!
 ;^)

 That said:
 I am using Win2K + IIS5, and also Win2K3 + IIS6, and in either case,
 also
 Tomcat 5.5:
 I can go to http://localhost and get my IIS index page.
 I can go to http://localhost:8080 and get my Tomcat index page.
 I can go to http://localhost/jsp-examples/index.html and run all the
 wonderful examples.
 HOWEVER, if I simply want to -ALSO- hand-off jsp pages to Tomcat that
 are
 in C:\Inetpub\wwwroot (and below) everything goes to hell.

 I have tried adding CONTEXT tags to server.xml until I turn blue in
 the
 face, and when I do so I get either 404 not found errors from

Re: Tomcat 5.5 working, BUT not outside of webapps/

2005-02-21 Thread Michael Greer
Why don't you show us your config file. This behavior work fine for me  
with 5.5.7, with Apache  mod_jk.

On Feb 22, 2005, at 1:20 AM, Matt wrote:
Is this simply not possible?  I have tried extrapolating form the docs
(which seems to work fine under webapps/ or $CATALINA_HOME) but  
anything
outside of it fails as badly as the other works perfectly, even if I  
try
to swap-out webapps/ for an otuside docbase using the HOST tag  
already
present.

There's got to be a file or simple edit that I'm missing for this?
Anyone?
Thanks,
-Matt
On Sun, 20 Feb 2005, Matt wrote:
OK, the docs out there are good, but they either concern old versions  
of
IIS and/or Tomcat -OR- they concern the JK2 module (including this  
list's
archives I have searched).
If JK2 is NO LONGER SUPPORTED, why in the heck would I care to use it?
So, I am using the very nice jk_1.2.8.exe installer.  With that, most  
of
the steps found in the various, partially-helpful docs are already  
done!
;^)

That said:
I am using Win2K + IIS5, and also Win2K3 + IIS6, and in either case,  
also
Tomcat 5.5:
I can go to http://localhost and get my IIS index page.
I can go to http://localhost:8080 and get my Tomcat index page.
I can go to http://localhost/jsp-examples/index.html and run all the
wonderful examples.
HOWEVER, if I simply want to -ALSO- hand-off jsp pages to Tomcat that  
are
in C:\Inetpub\wwwroot (and below) everything goes to hell.

I have tried adding CONTEXT tags to server.xml until I turn blue in  
the
face, and when I do so I get either 404 not found errors from Tomcat
(can't find the subdirectory b/c I assume it is looking for it in
webapps/, but then again it can't find it even if I copy the whole  
thing
into webapps/) or The specified module could not be found message  
on the
page (IIS result of a uriworkermap.properties issue).
I have even tried editing the existing HOST tag to change webapps
to C:/Inetpub/wwwroot and all sorts of folders below wwwroot.  In  
those
cases, if I manage to edit the uriworkermap.properties file  
correctly, all
I get is a blank page for any .jsp, while IIS still handles the other
stuff just fine.

So, instead of these outdated docs everyone keeps pointing to, does  
anyone
have any simple instructions to get Tomcat to properly use a folder
OUTSIDE of webapps, and ALONG WITH webapps to work (especially  
assuming
you've already got the basics working just fine as I do)?
I'd like to start by getting a copy of jsp-examples working in  
wwwroot/ if
possible (which is also how I was testing in the situation above, if  
that
means anything), rather than also confusing the situation by learning
how to create apps myself at the same time.  Perhaps that has caused  
my
problem - maybe the issue lies in a web.xml file somewhere for the
jsp-examples (I;ve even copied all of webapps to wwwroot to try and  
get
that to work, but no luck).

Thanks,
Matthew Kozak
Rutgers University-Camden
[EMAIL PROTECTED]
** 

 They that can give up essential liberty to obtain a little temporary
	safety deserve neither liberty nor safety.  -Ben Franklin
** 



Matthew Kozak
Rutgers University-Camden
[EMAIL PROTECTED]
*** 
***
 They that can give up essential liberty to obtain a little temporary
	safety deserve neither liberty nor safety.  -Ben Franklin
*** 
***

-
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: Tomcat not working

2003-07-31 Thread Shapira, Yoav

Howdy,
My mail reader doesn't like your attachment.  In general, instead of
posting attachments post the relevant bits from the file.  In this case,
since you have no idea what you did wrong, why not just start with a new
installation of tomcat?

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 8:52 AM
To: [EMAIL PROTECTED]
Subject: Tomcat not working

Greetings,
I have made some kinda change but I can't figure out what I did wrong.
I've
attached a copy of my server.xml .  This site is
http://gdttest.mgnetwork.com:8080/AdWebster
Can someone look to see if there's something wrong with my server.xml
file?

Thanks,
Bobbie

Bobbie Atristain
Internet Systems Administrator
Media General, INC.
804.649.6156





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: Tomcat not working properly

2003-07-28 Thread Reynir Hübner
Hi, 

By default it should process your jsp code, please give us more info on your setup. 

-reynir



 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] 
 Sent: 28. júlí 2003 17:27
 To: [EMAIL PROTECTED]
 Subject: Tomcat not working properly
 
 
 Greetings,
  My index.jsp page running under tomcat 4.1.12 shows code  
 https://placeanad.classifiedmarketplace.net/AdWebster/
 
  What do I need to do to the conf file to make it process the jsp?
 
  Thanks,
  Bobbie
 
  Bobbie Atristain
  Internet Systems Administrator
 
 
 
 -
 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: Tomcat not working properly

2003-07-28 Thread batristain
This is how it is set up

VirtualHost 207.243.40.37:443
DocumentRoot /usr/local/jakarta-tomcat-4.1.12/webapps
ServerName placeanad.classifiedmarketplace.net
ErrorLog logs/placeanadclassi.com-error_log
CustomLog logs/placeanadclassi.com-access_log common
SSLEnable
SSLCertificateFile /usr/local/apache/certs/nc1public.cert
SSLCertificateKeyFile /usr/local/apache/certs/nc2private.key
/VirtualHost

I have tomcat 4.1.12 running on the server.  Before we went to the ssl version
it was processing the code fine via port 8080 but now that it has to go through
443 it doesn't work anymore.

Thanks,
Bobbie

-Original Message-
From: Reynir Hübner [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 28, 2003 1:25 PM
To: Tomcat Users List
Subject: RE: Tomcat not working properly


Hi, 

By default it should process your jsp code, please give us more info on your
setup. 

-reynir



 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] 
 Sent: 28. júlí 2003 17:27
 To: [EMAIL PROTECTED]
 Subject: Tomcat not working properly
 
 
 Greetings,
  My index.jsp page running under tomcat 4.1.12 shows code
 https://placeanad.classifiedmarketplace.net/AdWebster/
 
  What do I need to do to the conf file to make it process the jsp?
 
  Thanks,
  Bobbie
 
  Bobbie Atristain
  Internet Systems Administrator
 
 
 
 -
 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: Tomcat not working properly

2003-07-28 Thread John Turner
You have to install an Apache connector (mod_jk.so or mod_jk2.so) and 
configure it to send certain requests to Tomcat.  Apache does not do 
this by default.

http://jakarta.apache.org/tomcat/faq/connectors.html

John

[EMAIL PROTECTED] wrote:

This is how it is set up

VirtualHost 207.243.40.37:443
DocumentRoot /usr/local/jakarta-tomcat-4.1.12/webapps
ServerName placeanad.classifiedmarketplace.net
ErrorLog logs/placeanadclassi.com-error_log
CustomLog logs/placeanadclassi.com-access_log common
SSLEnable
SSLCertificateFile /usr/local/apache/certs/nc1public.cert
SSLCertificateKeyFile /usr/local/apache/certs/nc2private.key
/VirtualHost
I have tomcat 4.1.12 running on the server.  Before we went to the ssl version
it was processing the code fine via port 8080 but now that it has to go through
443 it doesn't work anymore.
Thanks,
Bobbie
-Original Message-
From: Reynir Hübner [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 28, 2003 1:25 PM
To: Tomcat Users List
Subject: RE: Tomcat not working properly

Hi, 

By default it should process your jsp code, please give us more info on your
setup. 

-reynir




-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: 28. júlí 2003 17:27
To: [EMAIL PROTECTED]
Subject: Tomcat not working properly

Greetings,
My index.jsp page running under tomcat 4.1.12 shows code
https://placeanad.classifiedmarketplace.net/AdWebster/
What do I need to do to the conf file to make it process the jsp?

Thanks,
Bobbie
Bobbie Atristain
Internet Systems Administrator


-
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: Tomcat not working properly

2003-07-28 Thread batristain
I'm trying to do that but in the connector build when I run buildconf.sh it
doesn't find the configure.ac and there fore doesn't allow me to configure the
connector

Here's the list of errors that I get

 cd native
# ./buildconf.sh
libtoolize --force --automake --copy
libtoolize: `configure.ac' does not exist
Try `libtoolize --help' for more information.
aclocal
aclocal: `configure.ac' or `configure.in' is required
automake -a --foreign -i --copy
automake: `configure.ac' or `configure.in' is required
autoconf
autoconf: no input file
# ./configure
ksh: ./configure:  not found
# chmod 755 buildconf.sh
# ./buildconf.sh
libtoolize --force --automake --copy
libtoolize: `configure.ac' does not exist
Try `libtoolize --help' for more information.
aclocal
aclocal: `configure.ac' or `configure.in' is required
automake -a --foreign -i --copy
automake: `configure.ac' or `configure.in' is required
autoconf
autoconf: no input file
#


-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 28, 2003 2:31 PM
To: Tomcat Users List
Subject: Re: Tomcat not working properly



You have to install an Apache connector (mod_jk.so or mod_jk2.so) and 
configure it to send certain requests to Tomcat.  Apache does not do 
this by default.

http://jakarta.apache.org/tomcat/faq/connectors.html

John

[EMAIL PROTECTED] wrote:

 This is how it is set up
 
 VirtualHost 207.243.40.37:443
 DocumentRoot /usr/local/jakarta-tomcat-4.1.12/webapps
 ServerName placeanad.classifiedmarketplace.net
 ErrorLog logs/placeanadclassi.com-error_log
 CustomLog logs/placeanadclassi.com-access_log common
 SSLEnable
 SSLCertificateFile /usr/local/apache/certs/nc1public.cert
 SSLCertificateKeyFile /usr/local/apache/certs/nc2private.key
 /VirtualHost
 
 I have tomcat 4.1.12 running on the server.  Before we went to the ssl 
 version it was processing the code fine via port 8080 but now that it 
 has to go through 443 it doesn't work anymore.
 
 Thanks,
 Bobbie
 
 -Original Message-
 From: Reynir Hübner [mailto:[EMAIL PROTECTED]
 Sent: Monday, July 28, 2003 1:25 PM
 To: Tomcat Users List
 Subject: RE: Tomcat not working properly
 
 
 Hi,
 
 By default it should process your jsp code, please give us more info 
 on your setup.
 
 -reynir
 
 
 
 
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 28. júlí 2003 17:27
To: [EMAIL PROTECTED]
Subject: Tomcat not working properly


Greetings,
 My index.jsp page running under tomcat 4.1.12 shows code
https://placeanad.classifiedmarketplace.net/AdWebster/

 What do I need to do to the conf file to make it process the jsp?

 Thanks,
 Bobbie

 Bobbie Atristain
 Internet Systems Administrator



-
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]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat not working properly

2003-07-28 Thread John Turner
The obvious question:  What does libtoolize --help tell you?

Is this Linux?  What flavor?

Do you need ksh?  Have you tried this in sh or bash?  I'm not saying it 
will make a difference (it shouldn't), but it might.

John

[EMAIL PROTECTED] wrote:

I'm trying to do that but in the connector build when I run buildconf.sh it
doesn't find the configure.ac and there fore doesn't allow me to configure the
connector
Here's the list of errors that I get

 cd native
# ./buildconf.sh
libtoolize --force --automake --copy
libtoolize: `configure.ac' does not exist
Try `libtoolize --help' for more information.
aclocal
aclocal: `configure.ac' or `configure.in' is required
automake -a --foreign -i --copy
automake: `configure.ac' or `configure.in' is required
autoconf
autoconf: no input file
# ./configure
ksh: ./configure:  not found
# chmod 755 buildconf.sh
# ./buildconf.sh
libtoolize --force --automake --copy
libtoolize: `configure.ac' does not exist
Try `libtoolize --help' for more information.
aclocal
aclocal: `configure.ac' or `configure.in' is required
automake -a --foreign -i --copy
automake: `configure.ac' or `configure.in' is required
autoconf
autoconf: no input file
#
-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 28, 2003 2:31 PM
To: Tomcat Users List
Subject: Re: Tomcat not working properly



You have to install an Apache connector (mod_jk.so or mod_jk2.so) and 
configure it to send certain requests to Tomcat.  Apache does not do 
this by default.

http://jakarta.apache.org/tomcat/faq/connectors.html

John

[EMAIL PROTECTED] wrote:


This is how it is set up

VirtualHost 207.243.40.37:443
   DocumentRoot /usr/local/jakarta-tomcat-4.1.12/webapps
   ServerName placeanad.classifiedmarketplace.net
   ErrorLog logs/placeanadclassi.com-error_log
   CustomLog logs/placeanadclassi.com-access_log common
   SSLEnable
   SSLCertificateFile /usr/local/apache/certs/nc1public.cert
   SSLCertificateKeyFile /usr/local/apache/certs/nc2private.key
/VirtualHost
I have tomcat 4.1.12 running on the server.  Before we went to the ssl 
version it was processing the code fine via port 8080 but now that it 
has to go through 443 it doesn't work anymore.

Thanks,
Bobbie
-Original Message-
From: Reynir Hübner [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2003 1:25 PM
To: Tomcat Users List
Subject: RE: Tomcat not working properly
Hi,

By default it should process your jsp code, please give us more info 
on your setup.

-reynir





-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 28. júlí 2003 17:27
To: [EMAIL PROTECTED]
Subject: Tomcat not working properly
Greetings,
My index.jsp page running under tomcat 4.1.12 shows code
https://placeanad.classifiedmarketplace.net/AdWebster/
What do I need to do to the conf file to make it process the jsp?

Thanks,
Bobbie
Bobbie Atristain
Internet Systems Administrator


-
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]
-
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: Tomcat not working behind a NAT?

2003-07-25 Thread Erin Dalzell
For this particular Servlet call we are not accessing any databases.

DTDs? Not really familiar with those...I will check.

I don't think we are trying to resolve hosts.

Here is something we got from our client:
--
The sniffer log showed the NATed address in one of the http requests ...
following along the line of tomcat not using a localhost for addressing
requests even if they're local to the system ...

What options are there to specify the address for tomcat under which to
start ? It must perform a lookup on DNS to translate the address, can we use
the /etc/hosts file to create a 'fixed' address that won't be affected by
DNS ? This may not resolve it either ... as which one would you actually put
in to allow both 'local' access vs 'outside' access ... 
--


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699


-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 5:46 PM
To: Tomcat Users List
Subject: Re: Tomcat not working behind a NAT?


It shouldn't use high ports.
Are you running any database services or other services?
Are your dtd's not correct and its trying actually pull foriegn assets via
http?
Are you trying to resolve hosts in your access log? (or similar)

Use your sniffer to see the type of request being performed on the hight
port.

-Tim

Erin Dalzell wrote:
 Hi there,
 
 We have just discovered that our tomcat web app is not working correctly
 behind a NAT. Our actual web app works fine, but when we try to access our
 management pages via http. It doesn't work. Any static pages are served up
 correctly through our defined tomcat port (6300), but any dynamic content
 (to several different servlets) don't work.
 
 When we run a sniffer, it looks like tomcat tries to communicate with
itself
 on a very high (and random) port. For example, if our tomcat is accessible
 locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
 withing our network (10.10.x.x) everything works fine and tomcat is able
to
 talk to itself on port 45000. But if I access it from an external site,
 tomcat tries to communicate with itself on the 204.1.1.1 address and the
NAT
 doesn't like it.
 
 So, I have a few questions:
   1) why doesn't tomcat (we are using version 4) use localhost to
 communicate with itself?
   2) anyone else seen this problem?
   3) can the high port be configured?
 
 Thoughts? 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of this
e-mail or any attachments is strictly prohibited.  If you have received this
email in error, please immediately notify me by return email and by phone at
604-273-9146, permanently delete the original and any copy of this email and
any attachments from your systems and destroy any printouts of them.


RE: Tomcat not working behind a NAT?

2003-07-25 Thread Eric J. Pinnell
I still think you are barking up the wrong tree here.  If I had to guess I
would say that 95% of all internet faceing Tomcat servers are behind
some kind of NAT device.

One thing to consider.  NAT only translates the IP in the IP header and
doesn't change the data payload.  So if you are, for whatever reason,
using an IP address that is getting sent along in the payload and trying
to redirect to it or whatever, NAT won't change that.

Kinda how SQLNet doesn't like NAT devices.  Because the users IP is
embedded in the payload as part of the protocol.  So it goofs up when the
IP header and the IP in the payload don't match.

But what you are thinking below is the first thing I would do.  Make sure
the machine on the outside see's the correct hostname/IP number and the
machine on the inside see's that same hostname as the inside IP address.
You can do that via the hosts file if you like.

-e

On Fri, 25 Jul 2003, Erin Dalzell wrote:

 For this particular Servlet call we are not accessing any databases.

 DTDs? Not really familiar with those...I will check.

 I don't think we are trying to resolve hosts.

 Here is something we got from our client:
 --
 The sniffer log showed the NATed address in one of the http requests ...
 following along the line of tomcat not using a localhost for addressing
 requests even if they're local to the system ...

 What options are there to specify the address for tomcat under which to
 start ? It must perform a lookup on DNS to translate the address, can we use
 the /etc/hosts file to create a 'fixed' address that won't be affected by
 DNS ? This may not resolve it either ... as which one would you actually put
 in to allow both 'local' access vs 'outside' access ...
 --

 
 Erin Dalzell
 eXpresso Product Specialist
 Epic Data
 604.207.7699


 -Original Message-
 From: Tim Funk [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 24, 2003 5:46 PM
 To: Tomcat Users List
 Subject: Re: Tomcat not working behind a NAT?


 It shouldn't use high ports.
 Are you running any database services or other services?
 Are your dtd's not correct and its trying actually pull foriegn assets via
 http?
 Are you trying to resolve hosts in your access log? (or similar)

 Use your sniffer to see the type of request being performed on the hight
 port.

 -Tim

 Erin Dalzell wrote:
  Hi there,
 
  We have just discovered that our tomcat web app is not working correctly
  behind a NAT. Our actual web app works fine, but when we try to access our
  management pages via http. It doesn't work. Any static pages are served up
  correctly through our defined tomcat port (6300), but any dynamic content
  (to several different servlets) don't work.
 
  When we run a sniffer, it looks like tomcat tries to communicate with
 itself
  on a very high (and random) port. For example, if our tomcat is accessible
  locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
  withing our network (10.10.x.x) everything works fine and tomcat is able
 to
  talk to itself on port 45000. But if I access it from an external site,
  tomcat tries to communicate with itself on the 204.1.1.1 address and the
 NAT
  doesn't like it.
 
  So, I have a few questions:
  1) why doesn't tomcat (we are using version 4) use localhost to
  communicate with itself?
  2) anyone else seen this problem?
  3) can the high port be configured?
 
  Thoughts?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 This email and any attachments are intended only for use by the addressees
 named in this email and may contain legally privileged and/or confidential
 information.  If you are not the intended recipient of this email, you are
 hereby notified that any use, dissemination, distribution or copying of this
 e-mail or any attachments is strictly prohibited.  If you have received this
 email in error, please immediately notify me by return email and by phone at
 604-273-9146, permanently delete the original and any copy of this email and
 any attachments from your systems and destroy any printouts of them.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat not working behind a NAT?

2003-07-25 Thread Erin Dalzell
OK, I have a question for all the Tomcat gurus out there.

Here is my scenario:
* tomcat machine is behind NAT
* internal ip address is 2.2.2.2 (ip changed to protect the
innocent!)
* external ip is 3.3.3.3
* client accesses servlet with ip 3.3.3.3.
* inside servlet we call RequestDispatcher rd =
getServletContext().getRequestDispatcher( /another_page.jsp );
* then we call rd.forward( orig_request, response );

My question is, is that forward call a full http request? If so, what ip
address will it use? I think that it is trying to use the 3.3.3.3 address
and the NAT doesn't like it.

Thoughts?

Thanks

emd


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699


-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2003 10:05 AM
To: Tomcat Users List
Subject: RE: Tomcat not working behind a NAT?


I still think you are barking up the wrong tree here.  If I had to guess I
would say that 95% of all internet faceing Tomcat servers are behind
some kind of NAT device.

One thing to consider.  NAT only translates the IP in the IP header and
doesn't change the data payload.  So if you are, for whatever reason,
using an IP address that is getting sent along in the payload and trying
to redirect to it or whatever, NAT won't change that.

Kinda how SQLNet doesn't like NAT devices.  Because the users IP is
embedded in the payload as part of the protocol.  So it goofs up when the
IP header and the IP in the payload don't match.

But what you are thinking below is the first thing I would do.  Make sure
the machine on the outside see's the correct hostname/IP number and the
machine on the inside see's that same hostname as the inside IP address.
You can do that via the hosts file if you like.

-e

On Fri, 25 Jul 2003, Erin Dalzell wrote:

 For this particular Servlet call we are not accessing any databases.

 DTDs? Not really familiar with those...I will check.

 I don't think we are trying to resolve hosts.

 Here is something we got from our client:
 --
 The sniffer log showed the NATed address in one of the http requests ...
 following along the line of tomcat not using a localhost for addressing
 requests even if they're local to the system ...

 What options are there to specify the address for tomcat under which to
 start ? It must perform a lookup on DNS to translate the address, can we
use
 the /etc/hosts file to create a 'fixed' address that won't be affected by
 DNS ? This may not resolve it either ... as which one would you actually
put
 in to allow both 'local' access vs 'outside' access ...
 --

 
 Erin Dalzell
 eXpresso Product Specialist
 Epic Data
 604.207.7699


 -Original Message-
 From: Tim Funk [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 24, 2003 5:46 PM
 To: Tomcat Users List
 Subject: Re: Tomcat not working behind a NAT?


 It shouldn't use high ports.
 Are you running any database services or other services?
 Are your dtd's not correct and its trying actually pull foriegn assets via
 http?
 Are you trying to resolve hosts in your access log? (or similar)

 Use your sniffer to see the type of request being performed on the hight
 port.

 -Tim

 Erin Dalzell wrote:
  Hi there,
 
  We have just discovered that our tomcat web app is not working correctly
  behind a NAT. Our actual web app works fine, but when we try to access
our
  management pages via http. It doesn't work. Any static pages are served
up
  correctly through our defined tomcat port (6300), but any dynamic
content
  (to several different servlets) don't work.
 
  When we run a sniffer, it looks like tomcat tries to communicate with
 itself
  on a very high (and random) port. For example, if our tomcat is
accessible
  locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
  withing our network (10.10.x.x) everything works fine and tomcat is able
 to
  talk to itself on port 45000. But if I access it from an external site,
  tomcat tries to communicate with itself on the 204.1.1.1 address and the
 NAT
  doesn't like it.
 
  So, I have a few questions:
  1) why doesn't tomcat (we are using version 4) use localhost to
  communicate with itself?
  2) anyone else seen this problem?
  3) can the high port be configured?
 
  Thoughts?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 This email and any attachments are intended only for use by the addressees
 named in this email and may contain legally privileged and/or confidential
 information.  If you are not the intended recipient of this email, you are
 hereby notified that any use, dissemination, distribution or copying of
this
 e-mail or any attachments is strictly prohibited.  If you have received
this
 email in error, please immediately notify me by return email and by phone
at
 604-273-9146

RE: Tomcat not working behind a NAT?

2003-07-25 Thread Lawrence, Gabriel
Does setting the proxyName help?

See docs at:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/coyote.html



-Original Message-
From: Erin Dalzell [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 25, 2003 4:31 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat not working behind a NAT?

OK, I have a question for all the Tomcat gurus out there.

Here is my scenario:
* tomcat machine is behind NAT
* internal ip address is 2.2.2.2 (ip changed to protect the
innocent!)
* external ip is 3.3.3.3
* client accesses servlet with ip 3.3.3.3.
* inside servlet we call RequestDispatcher rd =
getServletContext().getRequestDispatcher( /another_page.jsp );
* then we call rd.forward( orig_request, response );

My question is, is that forward call a full http request? If so, what ip
address will it use? I think that it is trying to use the 3.3.3.3
address
and the NAT doesn't like it.

Thoughts?

Thanks

emd


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699


-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2003 10:05 AM
To: Tomcat Users List
Subject: RE: Tomcat not working behind a NAT?


I still think you are barking up the wrong tree here.  If I had to guess
I
would say that 95% of all internet faceing Tomcat servers are behind
some kind of NAT device.

One thing to consider.  NAT only translates the IP in the IP header and
doesn't change the data payload.  So if you are, for whatever reason,
using an IP address that is getting sent along in the payload and trying
to redirect to it or whatever, NAT won't change that.

Kinda how SQLNet doesn't like NAT devices.  Because the users IP is
embedded in the payload as part of the protocol.  So it goofs up when
the
IP header and the IP in the payload don't match.

But what you are thinking below is the first thing I would do.  Make
sure
the machine on the outside see's the correct hostname/IP number and the
machine on the inside see's that same hostname as the inside IP address.
You can do that via the hosts file if you like.

-e

On Fri, 25 Jul 2003, Erin Dalzell wrote:

 For this particular Servlet call we are not accessing any databases.

 DTDs? Not really familiar with those...I will check.

 I don't think we are trying to resolve hosts.

 Here is something we got from our client:
 --
 The sniffer log showed the NATed address in one of the http requests
...
 following along the line of tomcat not using a localhost for
addressing
 requests even if they're local to the system ...

 What options are there to specify the address for tomcat under which
to
 start ? It must perform a lookup on DNS to translate the address, can
we
use
 the /etc/hosts file to create a 'fixed' address that won't be affected
by
 DNS ? This may not resolve it either ... as which one would you
actually
put
 in to allow both 'local' access vs 'outside' access ...
 --

 
 Erin Dalzell
 eXpresso Product Specialist
 Epic Data
 604.207.7699


 -Original Message-
 From: Tim Funk [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 24, 2003 5:46 PM
 To: Tomcat Users List
 Subject: Re: Tomcat not working behind a NAT?


 It shouldn't use high ports.
 Are you running any database services or other services?
 Are your dtd's not correct and its trying actually pull foriegn assets
via
 http?
 Are you trying to resolve hosts in your access log? (or similar)

 Use your sniffer to see the type of request being performed on the
hight
 port.

 -Tim

 Erin Dalzell wrote:
  Hi there,
 
  We have just discovered that our tomcat web app is not working
correctly
  behind a NAT. Our actual web app works fine, but when we try to
access
our
  management pages via http. It doesn't work. Any static pages are
served
up
  correctly through our defined tomcat port (6300), but any dynamic
content
  (to several different servlets) don't work.
 
  When we run a sniffer, it looks like tomcat tries to communicate
with
 itself
  on a very high (and random) port. For example, if our tomcat is
accessible
  locally as 10.10.10.10 and externally as 204.1.1.1 and we access
from
  withing our network (10.10.x.x) everything works fine and tomcat is
able
 to
  talk to itself on port 45000. But if I access it from an external
site,
  tomcat tries to communicate with itself on the 204.1.1.1 address and
the
 NAT
  doesn't like it.
 
  So, I have a few questions:
  1) why doesn't tomcat (we are using version 4) use localhost to
  communicate with itself?
  2) anyone else seen this problem?
  3) can the high port be configured?
 
  Thoughts?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 This email and any attachments are intended only for use by the
addressees
 named in this email and may contain legally privileged and/or
confidential
 information.  If you

Re: Tomcat not working behind a NAT?

2003-07-25 Thread Tim Funk
No, forward is an internal forward. It does not leave the JVM. In fact, it 
doesn't leave the servlet context.

-Tim

Erin Dalzell wrote:
OK, I have a question for all the Tomcat gurus out there.

Here is my scenario:
* tomcat machine is behind NAT
* internal ip address is 2.2.2.2 (ip changed to protect the
innocent!)
* external ip is 3.3.3.3
* client accesses servlet with ip 3.3.3.3.
* inside servlet we call RequestDispatcher rd =
getServletContext().getRequestDispatcher( /another_page.jsp );
* then we call rd.forward( orig_request, response );
My question is, is that forward call a full http request? If so, what ip
address will it use? I think that it is trying to use the 3.3.3.3 address
and the NAT doesn't like it.
Thoughts?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Tomcat not working behind a NAT?

2003-07-25 Thread Eric J. Pinnell
 My question is, is that forward call a full http request? If so, what ip
 address will it use? I think that it is trying to use the 3.3.3.3 address
 and the NAT doesn't like it.


Well ya.  That's kinda what I've been saying.  Don't hardwire the IP.  So
instead of using an IP use a hostname.  For example www.myapp.com =
3.3.3.3 on the external DNS.

Then on your Tomcat systems host file (or internal DNS) put

2.2.2.2 www.myapp.com

So when/if Tomcat need to use the URL for some reason when it goes to
resolve the IP it gets the correct internal IP number.

-e

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat not working behind a NAT?

2003-07-25 Thread Erin Dalzell
Well, something is getting out far enough for the NAT to swallow it!

I have managed to upgrade our app to Tomcat 4.0.6 and I will turn up the
debugging info and then trace through the code to learn more about it.

All we do is call a JSP. And that is it. But somehow, the NAT doesn't like
it!!

Thanks

emd


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699


-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2003 4:49 PM
To: Tomcat Users List
Subject: Re: Tomcat not working behind a NAT?


No, forward is an internal forward. It does not leave the JVM. In fact, it 
doesn't leave the servlet context.

-Tim

Erin Dalzell wrote:
 OK, I have a question for all the Tomcat gurus out there.
 
 Here is my scenario:
   * tomcat machine is behind NAT
   * internal ip address is 2.2.2.2 (ip changed to protect the
 innocent!)
   * external ip is 3.3.3.3
   * client accesses servlet with ip 3.3.3.3.
   * inside servlet we call RequestDispatcher rd =
 getServletContext().getRequestDispatcher( /another_page.jsp );
   * then we call rd.forward( orig_request, response );
 
 My question is, is that forward call a full http request? If so, what ip
 address will it use? I think that it is trying to use the 3.3.3.3
address
 and the NAT doesn't like it.
 
 Thoughts?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of this
e-mail or any attachments is strictly prohibited.  If you have received this
email in error, please immediately notify me by return email and by phone at
604-273-9146, permanently delete the original and any copy of this email and
any attachments from your systems and destroy any printouts of them.


Re: Tomcat not working behind a NAT?

2003-07-24 Thread Eric J. Pinnell
Hi,

I was unaware that tomcat connects to itself on a high port.  Never the
less, Tomcat should be completely unaware of the 204.1.1.1 address.  If
your NAT is totally transparent the only place that IP lives is on the
external interface of your firewall/NAT device.  I don't see how that IP
could sneak back there.

Unless, and I'm going to guess here, your application is looking at the
URI of the request and doing something with it.  In that case you should
use IP numbers and have internal vs. external DNS (or /etc/hosts) set up
with the different IP numbers (one for the inside value and one with the
10.x.x.x inside value).  So that way if it tries to connect to the same
URI that was in the request it will get the right 10.x.x.x IP number.

I don't know if that helped or not.

-e


On Thu, 24 Jul 2003, Erin Dalzell wrote:

 Hi there,

 We have just discovered that our tomcat web app is not working correctly
 behind a NAT. Our actual web app works fine, but when we try to access our
 management pages via http. It doesn't work. Any static pages are served up
 correctly through our defined tomcat port (6300), but any dynamic content
 (to several different servlets) don't work.

 When we run a sniffer, it looks like tomcat tries to communicate with itself
 on a very high (and random) port. For example, if our tomcat is accessible
 locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
 withing our network (10.10.x.x) everything works fine and tomcat is able to
 talk to itself on port 45000. But if I access it from an external site,
 tomcat tries to communicate with itself on the 204.1.1.1 address and the NAT
 doesn't like it.

 So, I have a few questions:
   1) why doesn't tomcat (we are using version 4) use localhost to
 communicate with itself?
   2) anyone else seen this problem?
   3) can the high port be configured?

 Thoughts?

 Thanks

 emd

 
 Erin Dalzell
 eXpresso Product Specialist
 Epic Data
 604.207.7699


 This email and any attachments are intended only for use by the addressees
 named in this email and may contain legally privileged and/or confidential
 information.  If you are not the intended recipient of this email, you are
 hereby notified that any use, dissemination, distribution or copying of this
 e-mail or any attachments is strictly prohibited.  If you have received this
 email in error, please immediately notify me by return email and by phone at
 604-273-9146, permanently delete the original and any copy of this email and
 any attachments from your systems and destroy any printouts of them.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat not working behind a NAT?

2003-07-24 Thread John Turner
Made sense to me. :)

John

Eric J. Pinnell wrote:

Hi,

I was unaware that tomcat connects to itself on a high port.  Never the
less, Tomcat should be completely unaware of the 204.1.1.1 address.  If
your NAT is totally transparent the only place that IP lives is on the
external interface of your firewall/NAT device.  I don't see how that IP
could sneak back there.
Unless, and I'm going to guess here, your application is looking at the
URI of the request and doing something with it.  In that case you should
use IP numbers and have internal vs. external DNS (or /etc/hosts) set up
with the different IP numbers (one for the inside value and one with the
10.x.x.x inside value).  So that way if it tries to connect to the same
URI that was in the request it will get the right 10.x.x.x IP number.
I don't know if that helped or not.

-e

On Thu, 24 Jul 2003, Erin Dalzell wrote:


Hi there,

We have just discovered that our tomcat web app is not working correctly
behind a NAT. Our actual web app works fine, but when we try to access our
management pages via http. It doesn't work. Any static pages are served up
correctly through our defined tomcat port (6300), but any dynamic content
(to several different servlets) don't work.
When we run a sniffer, it looks like tomcat tries to communicate with itself
on a very high (and random) port. For example, if our tomcat is accessible
locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
withing our network (10.10.x.x) everything works fine and tomcat is able to
talk to itself on port 45000. But if I access it from an external site,
tomcat tries to communicate with itself on the 204.1.1.1 address and the NAT
doesn't like it.
So, I have a few questions:
1) why doesn't tomcat (we are using version 4) use localhost to
communicate with itself?
2) anyone else seen this problem?
3) can the high port be configured?
Thoughts?

Thanks

emd


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699
This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of this
e-mail or any attachments is strictly prohibited.  If you have received this
email in error, please immediately notify me by return email and by phone at
604-273-9146, permanently delete the original and any copy of this email and
any attachments from your systems and destroy any printouts of them.


-
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: Tomcat not working behind a NAT?

2003-07-24 Thread Eric J. Pinnell
Heh.. ya.  That didn't all come out right.

Use a host name instead of IP numbers and have internal and external DNS
set up with the internal and external IP numbers of the host respectively.

That's better.

-e

On Thu, 24 Jul 2003, John Turner wrote:


 Made sense to me. :)

 John

 Eric J. Pinnell wrote:

  Hi,
 
  I was unaware that tomcat connects to itself on a high port.  Never the
  less, Tomcat should be completely unaware of the 204.1.1.1 address.  If
  your NAT is totally transparent the only place that IP lives is on the
  external interface of your firewall/NAT device.  I don't see how that IP
  could sneak back there.
 
  Unless, and I'm going to guess here, your application is looking at the
  URI of the request and doing something with it.  In that case you should
  use IP numbers and have internal vs. external DNS (or /etc/hosts) set up
  with the different IP numbers (one for the inside value and one with the
  10.x.x.x inside value).  So that way if it tries to connect to the same
  URI that was in the request it will get the right 10.x.x.x IP number.
 
  I don't know if that helped or not.
 
  -e
 
 
  On Thu, 24 Jul 2003, Erin Dalzell wrote:
 
 
 Hi there,
 
 We have just discovered that our tomcat web app is not working correctly
 behind a NAT. Our actual web app works fine, but when we try to access our
 management pages via http. It doesn't work. Any static pages are served up
 correctly through our defined tomcat port (6300), but any dynamic content
 (to several different servlets) don't work.
 
 When we run a sniffer, it looks like tomcat tries to communicate with itself
 on a very high (and random) port. For example, if our tomcat is accessible
 locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
 withing our network (10.10.x.x) everything works fine and tomcat is able to
 talk to itself on port 45000. But if I access it from an external site,
 tomcat tries to communicate with itself on the 204.1.1.1 address and the NAT
 doesn't like it.
 
 So, I have a few questions:
 1) why doesn't tomcat (we are using version 4) use localhost to
 communicate with itself?
 2) anyone else seen this problem?
 3) can the high port be configured?
 
 Thoughts?
 
 Thanks
 
 emd
 
 
 Erin Dalzell
 eXpresso Product Specialist
 Epic Data
 604.207.7699
 
 
 This email and any attachments are intended only for use by the addressees
 named in this email and may contain legally privileged and/or confidential
 information.  If you are not the intended recipient of this email, you are
 hereby notified that any use, dissemination, distribution or copying of this
 e-mail or any attachments is strictly prohibited.  If you have received this
 email in error, please immediately notify me by return email and by phone at
 604-273-9146, permanently delete the original and any copy of this email and
 any attachments from your systems and destroy any printouts of them.
 
 
 
  -
  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: Tomcat not working behind a NAT?

2003-07-24 Thread Erin Dalzell
Ah yes, but I think tomcat does know what address was used to connect to
it. If I connect to tomcat via 204.1.1.1, doesn't tomcat then think that
that is its ip address and when it tries to open an IP connection to itself,
it uses that IP address? If that were the case, then when it tried to make
the connection it would fail as the NAT doesn't like connections that go out
and then back in.

That make any sense?

emd 


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699


-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 12:52 PM
To: Tomcat Users List
Subject: Re: Tomcat not working behind a NAT?


Hi,

I was unaware that tomcat connects to itself on a high port.  Never the
less, Tomcat should be completely unaware of the 204.1.1.1 address.  If
your NAT is totally transparent the only place that IP lives is on the
external interface of your firewall/NAT device.  I don't see how that IP
could sneak back there.

Unless, and I'm going to guess here, your application is looking at the
URI of the request and doing something with it.  In that case you should
use IP numbers and have internal vs. external DNS (or /etc/hosts) set up
with the different IP numbers (one for the inside value and one with the
10.x.x.x inside value).  So that way if it tries to connect to the same
URI that was in the request it will get the right 10.x.x.x IP number.

I don't know if that helped or not.

-e


On Thu, 24 Jul 2003, Erin Dalzell wrote:

 Hi there,

 We have just discovered that our tomcat web app is not working correctly
 behind a NAT. Our actual web app works fine, but when we try to access our
 management pages via http. It doesn't work. Any static pages are served up
 correctly through our defined tomcat port (6300), but any dynamic content
 (to several different servlets) don't work.

 When we run a sniffer, it looks like tomcat tries to communicate with
itself
 on a very high (and random) port. For example, if our tomcat is accessible
 locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
 withing our network (10.10.x.x) everything works fine and tomcat is able
to
 talk to itself on port 45000. But if I access it from an external site,
 tomcat tries to communicate with itself on the 204.1.1.1 address and the
NAT
 doesn't like it.

 So, I have a few questions:
   1) why doesn't tomcat (we are using version 4) use localhost to
 communicate with itself?
   2) anyone else seen this problem?
   3) can the high port be configured?

 Thoughts?

 Thanks

 emd

 
 Erin Dalzell
 eXpresso Product Specialist
 Epic Data
 604.207.7699


 This email and any attachments are intended only for use by the addressees
 named in this email and may contain legally privileged and/or confidential
 information.  If you are not the intended recipient of this email, you are
 hereby notified that any use, dissemination, distribution or copying of
this
 e-mail or any attachments is strictly prohibited.  If you have received
this
 email in error, please immediately notify me by return email and by phone
at
 604-273-9146, permanently delete the original and any copy of this email
and
 any attachments from your systems and destroy any printouts of them.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of this
e-mail or any attachments is strictly prohibited.  If you have received this
email in error, please immediately notify me by return email and by phone at
604-273-9146, permanently delete the original and any copy of this email and
any attachments from your systems and destroy any printouts of them.


Re: Tomcat not working behind a NAT?

2003-07-24 Thread John Turner
That isn't how NAT works.  Tomcat doesn't know anything about the 204.* 
address if the router is doing the NAT properly.  The address Tomcat 
will see for the request is the router's internal Ip address.

John

Erin Dalzell wrote:

Ah yes, but I think tomcat does know what address was used to connect to
it. If I connect to tomcat via 204.1.1.1, doesn't tomcat then think that
that is its ip address and when it tries to open an IP connection to itself,
it uses that IP address? If that were the case, then when it tried to make
the connection it would fail as the NAT doesn't like connections that go out
and then back in.
That make any sense?

emd 


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699
-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 12:52 PM
To: Tomcat Users List
Subject: Re: Tomcat not working behind a NAT?
Hi,

I was unaware that tomcat connects to itself on a high port.  Never the
less, Tomcat should be completely unaware of the 204.1.1.1 address.  If
your NAT is totally transparent the only place that IP lives is on the
external interface of your firewall/NAT device.  I don't see how that IP
could sneak back there.
Unless, and I'm going to guess here, your application is looking at the
URI of the request and doing something with it.  In that case you should
use IP numbers and have internal vs. external DNS (or /etc/hosts) set up
with the different IP numbers (one for the inside value and one with the
10.x.x.x inside value).  So that way if it tries to connect to the same
URI that was in the request it will get the right 10.x.x.x IP number.
I don't know if that helped or not.

-e

On Thu, 24 Jul 2003, Erin Dalzell wrote:


Hi there,

We have just discovered that our tomcat web app is not working correctly
behind a NAT. Our actual web app works fine, but when we try to access our
management pages via http. It doesn't work. Any static pages are served up
correctly through our defined tomcat port (6300), but any dynamic content
(to several different servlets) don't work.
When we run a sniffer, it looks like tomcat tries to communicate with
itself

on a very high (and random) port. For example, if our tomcat is accessible
locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
withing our network (10.10.x.x) everything works fine and tomcat is able
to

talk to itself on port 45000. But if I access it from an external site,
tomcat tries to communicate with itself on the 204.1.1.1 address and the
NAT

doesn't like it.

So, I have a few questions:
1) why doesn't tomcat (we are using version 4) use localhost to
communicate with itself?
2) anyone else seen this problem?
3) can the high port be configured?
Thoughts?

Thanks

emd


Erin Dalzell
eXpresso Product Specialist
Epic Data
604.207.7699
This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of
this

e-mail or any attachments is strictly prohibited.  If you have received
this

email in error, please immediately notify me by return email and by phone
at

604-273-9146, permanently delete the original and any copy of this email
and

any attachments from your systems and destroy any printouts of them.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of this
e-mail or any attachments is strictly prohibited.  If you have received this
email in error, please immediately notify me by return email and by phone at
604-273-9146, permanently delete the original and any copy of this email and
any attachments from your systems and destroy any printouts of them.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Tomcat not working behind a NAT?

2003-07-24 Thread John Turner
Sorry, I'm on crack.  Tomcat will see the actual client IP address for 
the request.

John

John Turner wrote:

That isn't how NAT works.  Tomcat doesn't know anything about the 204.* 
address if the router is doing the NAT properly.  The address Tomcat 
will see for the request is the router's internal Ip address.

John

Erin Dalzell wrote:

Ah yes, but I think tomcat does know what address was used to 
connect to
it. If I connect to tomcat via 204.1.1.1, doesn't tomcat then think that
that is its ip address and when it tries to open an IP connection to 
itself,
it uses that IP address? If that were the case, then when it tried to 
make
the connection it would fail as the NAT doesn't like connections that 
go out
and then back in.

That make any sense?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Tomcat not working behind a NAT?

2003-07-24 Thread Tim Funk
It shouldn't use high ports.
Are you running any database services or other services?
Are your dtd's not correct and its trying actually pull foriegn assets via http?
Are you trying to resolve hosts in your access log? (or similar)
Use your sniffer to see the type of request being performed on the hight port.

-Tim

Erin Dalzell wrote:
Hi there,

We have just discovered that our tomcat web app is not working correctly
behind a NAT. Our actual web app works fine, but when we try to access our
management pages via http. It doesn't work. Any static pages are served up
correctly through our defined tomcat port (6300), but any dynamic content
(to several different servlets) don't work.
When we run a sniffer, it looks like tomcat tries to communicate with itself
on a very high (and random) port. For example, if our tomcat is accessible
locally as 10.10.10.10 and externally as 204.1.1.1 and we access from
withing our network (10.10.x.x) everything works fine and tomcat is able to
talk to itself on port 45000. But if I access it from an external site,
tomcat tries to communicate with itself on the 204.1.1.1 address and the NAT
doesn't like it.
So, I have a few questions:
1) why doesn't tomcat (we are using version 4) use localhost to
communicate with itself?
2) anyone else seen this problem?
3) can the high port be configured?
Thoughts? 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: tomcat not working

2002-10-24 Thread PELOQUIN,JEFFREY (HP-Boise,ex1)
Do you have an index.html file in your ROOT context/webapp?
most likely /opt/jakarta/webapps/ROOT/index.html
What do you get if you try http://ip_address:8080/ without specifying a
file?


Also for your HP-UX machine did you use the apache/tomcat depot provided by
HP or did you download the files from apache and jakarta websites?  If the
latter how much trouble did you have compiling the connector between apache
and tomcat?  This does not have to do with your problem but I am simply
curious as I use HP-UX machines, as well.

Jeff

-Original Message-
From: Vishal Gupta [mailto:vhgupta1;yahoo.com]
Sent: Thursday, October 24, 2002 3:57 AM
To: [EMAIL PROTECTED]
Subject: tomcat not working



Hi All,

I have installed tomcat/apache on HP-UX machine.

Apache is working fine but i can't see the tomcat home page at
://ip_address:8080/index.html

error is below. I have checked all the conf files in conf
directory.everything seems to be OK please suggest the solution.

 Regards,

Vishal
Apache Tomcat/4.0.4 - HTTP Status 404 - /index.html
 

type Status report

message /index.html

description The requested resource (/index.html) is not available.



-
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site

--
To unsubscribe, e-mail:   mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org




RE: tomcat not working

2002-10-24 Thread Vishal Gupta

Pls see below..
Thanks and regards,
Vishal
 PELOQUIN,JEFFREY (HP-Boise,ex1) [EMAIL PROTECTED] wrote:
Do you have an index.html file in your ROOT context/webapp?

..yes its there 

..I suspect some configuration or user right as it says resource not available..i made 
its owner as tomcat and permissions are 777..

...pls advice as it must be a simple problem...and i am a novice with hp 
systems.but i have checked min. config mentioned in running.txt and everything 
seems to be ok


most likely /opt/jakarta/webapps/ROOT/index.html
What do you get if you try http://ip_address:8080/ without specifying a
file?

...I still get the same error




Also for your HP-UX machine did you use the apache/tomcat depot provided by
HP or did you download the files from apache and jakarta websites? If the
latter how much trouble did you have compiling the connector between apache
and tomcat? This does not have to do with your problem but I am simply
curious as I use HP-UX machines, as well.


..apache jakarta file gave me some error so i used the depot for that but tomcat 
installation was smooth from jakarta binary file
Jeff

-Original Message-
From: Vishal Gupta [mailto:vhgupta1;yahoo.com]
Sent: Thursday, October 24, 2002 3:57 AM
To: [EMAIL PROTECTED]
Subject: tomcat not working



Hi All,

I have installed tomcat/apache on HP-UX machine.

Apache is working fine but i can't see the tomcat home page at
://ip_address:8080/index.html

error is below. I have checked all the conf files in conf
directory.everything seems to be OK please suggest the solution.

Regards,

Vishal
Apache Tomcat/4.0.4 - HTTP Status 404 - /index.html


type Status report

message /index.html

description The requested resource (/index.html) is not available.



-
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site

--
To unsubscribe, e-mail: 
For additional commands, e-mail: 



Vishal Gupta
Schlumberger Measurement  Systems India Ltd 
10th Floor, HMG Ambassador
Bangalore 560 025
Tel: +91 98451 32104 off: +91 80 2075052-55 Ext: 117 Fax:+91 80 2075056 
E-Mail :- [EMAIL PROTECTED] and   [EMAIL PROTECTED]


-
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site


Re: Tomcat Current Working Directory

2002-08-17 Thread Larry Meadors

 Is there a way to configure Tomcat 4.0.4's 
 current working directory to point to 
 sub-directory of the webapps folder, 
 rather than /bin?

I hate to answer a question with a question, but here goes: Why would
you want to do that?

Larry


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Tomcat Current Working Directory

2002-08-16 Thread David Makepeace

If running as NT service, there is a registry string
that you can create named Current Directory and you
can give it a value of anything you like. Not sure how
to implement with batch file.

--- Callahan, Gerard
[EMAIL PROTECTED] wrote:
 Is there a way to configure Tomcat 4.0.4's current
 working directory to 
 point to sub directory of the webapps folder, rather
 than /bin?
 
 Thanks,
 
 Gerard Callahan
 SAIC
 [EMAIL PROTECTED]
 
 
 --
 To unsubscribe, e-mail:  
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
 mailto:[EMAIL PROTECTED]
 


__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: tomcat +iis working

2001-11-13 Thread Nihar

Hi!

 Well, not much..few things are required like creating virtual directory
under the web site with executable rights and one registry setting  are
required..

regards
-NIHAR

-Original Message-
From: Steve Vu [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 11, 2001 12:03 PM
To: Tomcat Users List
Subject: RE: tomcat +iis working


That's cool Nihar.  The thing you said that interests me is using both ASP
and JSP.
Did you have to do any special configuration after connecting IIs to Tomcat?
We are using ASP at work but may consider using JSP, so being able to do
this would make the transition a lot easier.

I'm guessing that there's not too much config necessary?  IIS automatically
handles ASP and Tomcat takes all JSP requests?

Thanks for any info.  The more detail the beter.

Thanks much,
Steve

-Original Message-
From: Nihar [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 10, 2001 7:29 PM
To: Tomcat Users List
Subject: RE: tomcat +iis working


tomact version 3.2.1 !!

-Original Message-
From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 11, 2001 4:24 AM
To: 'Tomcat Users List'
Subject: RE: tomcat +iis working


Which version of tomcat?

Saludos ,
Ignacio J. Ortega


 -Mensaje original-
 De: Nihar [mailto:[EMAIL PROTECTED]]
 Enviado el: sábado 10 de noviembre de 2001 23:49
 Para: tomcat
 Asunto: tomcat +iis working


 Hi gurus,

 Finally my tomcat and iis integration works. I spend near
 about 8 hours on
 this and now willing to help people who is having difficulty in this.
  I am running around 30 virtual domains on iis(windows nt)
 serving jsp and
 asp functionality.

 regards
 -NIHAR


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



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



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


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



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




Re: tomcat not working totally...

2001-02-27 Thread Corey A. Johnson

What JDK version do you have installed?  It looks to me like the file
tools.jar is not in your CLASSPATH.

Should be located in JAVA_HOME/lib

Let me know if that helps.

Cj

Andrew Y Ng wrote:

 Hi, I'm new to tomcat, I am running NetBSD 1.4.1 (sorry, no time
 to upgrade) on i386, with the apache-1.3.17.1 package. I installed
 the jakarta-tomcat-3.1.1 binary package and ran the startup
 script. I tried out the JSP and servlet examples and some
 of them did not work, I suspect it's a CLASSPATH problem but
 after looking at the tomcat.sh script, i think all i need
 is JAVA_HOME to be set right, and the script sets CLASSPATH
 so at least JSP and servlet engines would run.

 If you guys can take a look at http://guadalupe.rem.cmu.edu:8080
 and give me ideas as to what's wrong, i'd really appreciate that.
 I have a feeling that this is something trivial and you guys
 have probably seen this many times. Thanks!

 /ayn

 --
 Andrew Y Ng  |  [EMAIL PROTECTED]  |  http://andrew.Ngbert.org/
 --
   (-) please finger [EMAIL PROTECTED] if u need more info...

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

--
Corey A. Johnson
Creative Network Innovations
http://www.cniweb.net/
1-800-CNi-5547 ** 1-321-259-1984



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: tomcat not working totally...

2001-02-27 Thread Andrew Y Ng

java -version gives me:
java version "1.1.6"

there is not a tools.jar anywhere, maybe i need to update my JDK?

/ayn


On Tue, 27 Feb 2001, Corey A. Johnson wrote:

 What JDK version do you have installed?  It looks to me like the file
 tools.jar is not in your CLASSPATH.
 
 Should be located in JAVA_HOME/lib
 
 Let me know if that helps.
 
 Cj
 
 Andrew Y Ng wrote:
 
  Hi, I'm new to tomcat, I am running NetBSD 1.4.1 (sorry, no time
  to upgrade) on i386, with the apache-1.3.17.1 package. I installed
  the jakarta-tomcat-3.1.1 binary package and ran the startup
  script. I tried out the JSP and servlet examples and some
  of them did not work, I suspect it's a CLASSPATH problem but
  after looking at the tomcat.sh script, i think all i need
  is JAVA_HOME to be set right, and the script sets CLASSPATH
  so at least JSP and servlet engines would run.
 
  If you guys can take a look at http://guadalupe.rem.cmu.edu:8080
  and give me ideas as to what's wrong, i'd really appreciate that.
  I have a feeling that this is something trivial and you guys
  have probably seen this many times. Thanks!
 
  /ayn
 
  --
  Andrew Y Ng  |  [EMAIL PROTECTED]  |  http://andrew.Ngbert.org/
  --
(-) please finger [EMAIL PROTECTED] if u need more info...
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, email: [EMAIL PROTECTED]
 
 --
 Corey A. Johnson
 Creative Network Innovations
 http://www.cniweb.net/
 1-800-CNi-5547 ** 1-321-259-1984
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]
 


--
Andrew Y Ng  |  [EMAIL PROTECTED]  |  http://andrew.Ngbert.org/
--
  (-) please finger [EMAIL PROTECTED] if u need more info...


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: tomcat not working totally...

2001-02-27 Thread Corey A. Johnson

Yep.  That will do it.  Grab JDK 1.2..  That will take care of your problem.

Cj

Andrew Y Ng wrote:

 java -version gives me:
 java version "1.1.6"

 there is not a tools.jar anywhere, maybe i need to update my JDK?

 /ayn

 On Tue, 27 Feb 2001, Corey A. Johnson wrote:

  What JDK version do you have installed?  It looks to me like the file
  tools.jar is not in your CLASSPATH.
 
  Should be located in JAVA_HOME/lib
 
  Let me know if that helps.
 
  Cj
 
  Andrew Y Ng wrote:
 
   Hi, I'm new to tomcat, I am running NetBSD 1.4.1 (sorry, no time
   to upgrade) on i386, with the apache-1.3.17.1 package. I installed
   the jakarta-tomcat-3.1.1 binary package and ran the startup
   script. I tried out the JSP and servlet examples and some
   of them did not work, I suspect it's a CLASSPATH problem but
   after looking at the tomcat.sh script, i think all i need
   is JAVA_HOME to be set right, and the script sets CLASSPATH
   so at least JSP and servlet engines would run.
  
   If you guys can take a look at http://guadalupe.rem.cmu.edu:8080
   and give me ideas as to what's wrong, i'd really appreciate that.
   I have a feeling that this is something trivial and you guys
   have probably seen this many times. Thanks!
  
   /ayn
  
   --
   Andrew Y Ng  |  [EMAIL PROTECTED]  |  http://andrew.Ngbert.org/
   --
 (-) please finger [EMAIL PROTECTED] if u need more info...
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, email: [EMAIL PROTECTED]
 
  --
  Corey A. Johnson
  Creative Network Innovations
  http://www.cniweb.net/
  1-800-CNi-5547 ** 1-321-259-1984
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, email: [EMAIL PROTECTED]
 

 --
 Andrew Y Ng  |  [EMAIL PROTECTED]  |  http://andrew.Ngbert.org/
 --
   (-) please finger [EMAIL PROTECTED] if u need more info...

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

--
Corey A. Johnson
Creative Network Innovations
http://www.cniweb.net/
1-800-CNi-5547 ** 1-321-259-1984



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]