Nathan, you should still be able to get to the manager from
http://localhost:8080/manager/html
If you messing around with the ROOT config, its a little tricky because its
precompiled.
The easiest way to change ROOT, is to just make a webapp with the name ROOT
and an empty context path do
Hi Glenn,
Thanks for your tutorial - the virtual folder in IIS was indeed the missing
piece to the jigsaw. IIS and Tomcat are happily up and running now.
Cheers,
Richard.
gbarnas wrote:
404's indicate that the file can't be found. IIS needs to be able to see
the tomcat files/folders in
Hi,
I'm fighting a relatively nasty issue. I've implemented a WMS service (Web
Map Server), which basically
returns a geographic map in response to a request stating which data to use,
which area to display, which style to apply to the map, and so on.
The main trouble is that building the map
Hi
I am seeing this error in my isapi.log, I am running IIS 6.0, tomcat 4.1
and jk 1.2.23
...[5228:6988] [error] jk_isapi_plugin.c (1507): Failed to obtain an
endpoint to service request - your connection_pool_size is probably less
than the threads in your web server!
Does anyone
From: Juha Laiho [mailto:[EMAIL PROTECTED]
Subject: Re: Context.xml error
Looking at that the context data you posted, at least the
first one is missing the path=/... attribute (which is
required to be unique for all context within a given host
-- and I think this requirement makes the
From: Marcello Pucci [mailto:[EMAIL PROTECTED]
Subject: How to compile from source
I've just completed the steps required to build
apache-tomcat-5.5 from source,
For curiosity's sake, why are you doing this?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
Thanks for the feedback, and I'm glad it was useful. I'll be posting it as an
HTML document on my web site shortly - adding a Resources page for this kind
of information. The .DOC file will still be available for downloading.
Glenn
rcgeorge23 wrote:
Hi Glenn,
Thanks for your tutorial -
Hi
I am seeing this error in my stderror.log, I am running IIS 6.0, tomcat
4.1 and jk 1.2.23
Jul 8, 2007 7:38:37 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: connection timeout reached
Does anyone know what this means, and what the cure is?
Thanks,
Rasmus
This is an interesting question, and I'm going to guess...
If you in a JSP page, I dont think the error can be trapped.
If you in a servlet, yes I think a try catch will detect it, but only if you
actually write something.
I think the generic problem is that you cant just leave the browser
Are there any flat files to look at or modify the manager/html settings.
The tricky
part is that I don't have phyisical access to the machine. I can log in
through ssh
and do have sufficient privileges to tweak the server. I've tried wget
on localhost,
so I know the helloWorld webapp is working
That was a really great set of answers, thanks! These follow-ups are somewhat
off-topic to Tomcat, but you really know this stuff well so I hope you don't
mind addressing them:
POST requests always use the request's body encoding, which is specified
in
the HTTP header (and can be overridden
hi everyone,
can i use two tomcat webservers to exchange information between them?
how can i do that?
thank you,
rana.
--
View this message in context:
http://www.nabble.com/about-tomcat-tf4047066.html#a11495638
Sent from the Tomcat - User mailing list archive at Nabble.com.
Yes, it is possible to run two servers as a cluster and exchange
information between them. I have seen an article on the internet recently
on doing exactly this. The easiest way of finding out how to do this is to
use Googles advanced search and to type 'tomcat clustering' into the exact
phrase
thank you for the reply.
what i really need to do is transfer records from one database to
another database.so in the middle there would be two web servers.
is this a good idea?
Stephen.Morris wrote:
Yes, it is possible to run two servers as a cluster and exchange
information
I would have thought this wouldn't be a problem as long as the db queries
returned a concise list of records for transfer. If the queries returned
large volumes of transactions your network could very quickly become
clogged and unusable.
regards,
Steve Morris
IT Security Access Management
No, I dont think so, a web server is not a client, and unless you really
have to work on port 80, it would be much easier to just to use JDBC to
exchange records. ie open 2 database connections, read from one and write to
the other, this way you can also use tranactions and ensure the
16 matches
Mail list logo