RE: Tomcat, IIS and virtual hosts

2001-05-03 Thread Duncan Irvine

I didn't spend too long on this, as we only needed the vhosts as a stop-gap
solution, and only needed three at that, but the only way I found to do it
was to have vhosts defined in both Apache and Tomcat.

Apache's vhosting knows the difference for the static pages, and any
.jsps/servlets for *any* of the servers are handed off to Tomcat without
vhosting.  Tomcat then knows the correct vhost as well, and serves the
relevant jsp.  I forget which (but I believe Apache) complained about the
mod_jk config appearing within a vhost definition.  I've no idea about IIS
unfortunately - I only use real web-servers!

The rest of the information you need is in the docs, and you should be able
to work it out yourself.  

There may be a better way to do it, but I didn't have the time to find it.

Hope this helps,
Duncan.

P.S. I can probably dig the old config files out if you need them, but I
don't have them to hand at the mo.


 -Original Message-
 From: Brian Murray [mailto:[EMAIL PROTECTED]]
 Sent: 03 May 2001 08:42
 To: [EMAIL PROTECTED]
 Subject: Re: Tomcat, IIS and virtual hosts
 
 
  Apache is a much better solution for virtual hosts than IIS
 
 He's using IIS and I'm using Apache.  What we have in common 
 is that we're both after examples of
 setting up Tomcat to work with virtual hosts.  I'm sorry if 
 that was not clear.
 
 __
 Do You Yahoo!?
 Yahoo! Auctions - buy the things you want at great prices
 http://auctions.yahoo.com/
 



This message contains information which may be privileged
and confidential and subject to legal privilege. If you are not
the intended recipient, you may not peruse, use, disseminate,
distribute or copy this message. If you have received this 
message in error, please notify the sender immediately by 
e-mail, facsimile, or telephone and return or destroy the 
original message. Sopheon and its officers are not responsible
for any statements or material in this e-mail and in any attachment
to it which might give rise to any criminal or civil claim.




RE: Why Use apache

2001-05-02 Thread Duncan Irvine

I would suggest that Apache is also more secure - it's been around longer,
and has had more development, thus has had longer to mature.  If you hide
Tomcat behind Apache, then any bugs that may appear in Tomcat's URL parsing
(for example) are less of a worry.

Duncan.


 -Original Message-
 From: David M. Rosner [mailto:[EMAIL PROTECTED]]
 Sent: 02 May 2001 16:06
 To: [EMAIL PROTECTED]
 Subject: RE: Why Use apache
 
 
 If I have all my static html and graphics loading off of 
 other servers, is 
 there any reason to use Apache with Tomcat? Is the 
 combination more stable 
 or is performance better with both running?
 
 thanks
 
 -dave
 
 At 11:00 AM 5/2/2001, Ronan Derby wrote:
 tomcat isn't as good as apache at serving static html files 
 and images.
 also, with apache up and running you can do other stuff like 
 execute cgi
 scripts and so on.
 
 -Original Message-
 From: Skinner, Dallas M [mailto:[EMAIL PROTECTED]]
 Sent: 02 May 2001 15:48
 To: [EMAIL PROTECTED]
 Subject: Why Use apache
 
 
 Excuse me if this question is obvious.  If Tomcat can be run 
 in a standalone
 mode, why should it be used in conjunction with apache?
 
 Thanks
 
 Dallas Skinner
 



This message contains information which may be privileged
and confidential and subject to legal privilege. If you are not
the intended recipient, you may not peruse, use, disseminate,
distribute or copy this message. If you have received this 
message in error, please notify the sender immediately by 
e-mail, facsimile, or telephone and return or destroy the 
original message. Sopheon and its officers are not responsible
for any statements or material in this e-mail and in any attachment
to it which might give rise to any criminal or civil claim.




RE: Cache problem with IE

2001-03-13 Thread Duncan Irvine

I'm sure someone will jump on this from a great height if I'm wrong, but I
seem to recall that the cache settings are for intermediate caches - not the
browser.  The browser can cache pages as it sees fit - provided that it
checks to see if they've been updated, but the cache control settings are
there to stop intermediate caches from falsely reporting a page as not
having changed.

Duncan.


 -Original Message-
 From: Zsolt Koppany [mailto:[EMAIL PROTECTED]]
 Sent: 13 March 2001 16:13
 To: [EMAIL PROTECTED]
 Subject: Cache problem with IE
 
 
 Hi,
 
 with the code below I can get netscape not to cache a jsp page but it
 does not work with Internet-Explorer.
 Does anybody know why?
 
 
 response.setHeader("Cache-Control", "no-cache");
 response.setHeader("Pragma", "no-cache");\
 
 
 
 Zsolt
 
 -- 
 Zsolt Koppany
 Intland GmbH www.intland.com
 Schulze-Delitzsch-Strasse 16
 D-70565 Stuttgart
 Tel: +49-711-7871080 Fax: +49-711-7871017
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]
 



This message contains information which may be privileged
and confidential and subject to legal privilege. If you are not
the intended recipient, you may not peruse, use, disseminate,
distribute or copy this message. If you have received this 
message in error, please notify the sender immediately by 
e-mail, facsimile, or telephone and return or destroy the 
original message. Sopheon and its officers are not responsible
for any statements or material in this e-mail and in any attachment
to it which might give rise to any criminal or civil claim.


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




Jasper losing classpath?!?

2001-02-09 Thread Duncan Irvine

Hi all,
I've been merrily using Tomcat for some time now (v3.2.1) and have
just come accross a rather bizarre one... Jasper seems to 'forget' the
classpath after a while and refuses to compile new JSPs.  All is well after
startup, things run smoothly for an hour or two, and Tomcat will continue to
serve already compiled JSPs.  However, if I haven't used a given JSP after a
couple of hours (not sure of a specific time) it will not compile.  Jasper
throws a 'Class not Found' JasperException and that's it.  If Tomcat is
restarted the same JSP will compile and run quite happily.  Is this a known
problem with Jasper, or am I just doing something really dumb with the
config.

It's not a major problem, as I should think that the production box can be
'pre-hit'  to compile all the JSPs beforehand, and is unlikely to be updated
often enough to warrant dynamic recompilation, but it'd be nice to know.

Cheers,
Duncan.




This message contains information which may be privileged
and confidential and subject to legal privilege. If you are not
the intended recipient, you may not peruse, use, disseminate,
distribute or copy this message. If you have received this 
message in error, please notify the sender immediately by 
e-mail, facsimile, or telephone and return or destroy the 
original message. Sopheon and its officers are not responsible
for any statements or material in this e-mail and in any attachment
to it which might give rise to any criminal or civil claim.


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