tomcat standalone virtual hosting

2004-05-17 Thread Rudolf Feyerkleist
I have a localhost host and test host. Both contain two webapps: /pkservermanager 
and /pkserver. The test host has a seperate connector listening to the port 3030. 
The server.xml content of tomcat is given below. The problem is when I open the 
browser and type http://localhost:3030/pkservermanager/index.htm the 
/pkservermanager/index.html page of localhost (in its docbase) is loaded and not the 
one of test. Does anybody has an idea why this is occurs, and if possible howto fix 
it? I tried to change everything in the server.xml of tomcat but nothing seems to work.
 
Rudolf Feyerkleist
 
 
Directory structure of my tomcat installation under tomcat directory:
/server/webapps/pkserver/
/webapps/pkservermanager/ /** the index.html under this directory isalways loaded **/
/webapps_test/pkserver/
/webapps_test/pkservermangager/  /** the index.html under this directory is never 
loaded **/
 
Content of server.xml
 

?xml version=1.0 encoding=UTF-8?

!-- Example Server Configuration File --

!-- Note that component elements are nested corresponding to their

parent-child relationships with each other --

!-- A Server is a singleton element that represents the entire JVM,

which may contain one or more Service instances. The Server

listens for a shutdown command on the indicated port.

Note: A Server is not itself a Container, so you may not

define subcomponents such as Valves or Loggers at this level.

--

Server port=8005 shutdown=SHUTDOWN debug=0

!-- Comment these entries out to disable JMX MBeans support --

!-- You may also configure custom components (e.g. Valves/Realms) by

including your own mbean-descriptor file(s), and setting the

descriptors attribute to point to a ';' seperated list of paths

(in the ClassLoader sense) of files to add to the default list.

e.g. descriptors=/com/myfirm/mypackage/mbean-descriptor.xml

--

Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/

Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener 
debug=0/

!-- Global JNDI resources --

GlobalNamingResources

!-- Test entry for demonstration purposes --

Environment name=simpleValue type=java.lang.Integer value=30/

!-- Editable user database that can also be used by

UserDatabaseRealm to authenticate users --

Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase 
description=User database that can be updated and saved

/Resource

ResourceParams name=UserDatabase

parameter

namefactory/name

valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value

/parameter

parameter

namepathname/name

valueconf/tomcat-users.xml/value

/parameter

/ResourceParams

/GlobalNamingResources

!-- A Service is a collection of one or more Connectors that share

a single Container (and therefore the web applications visible

within that Container). Normally, that Container is an Engine,

but this is not required.

Note: A Service is not itself a Container, so you may not

define subcomponents such as Valves or Loggers at this level.

--

!-- Define the Tomcat Stand-Alone Service --

Service name=Tomcat-Standalone

!-- A Connector represents an endpoint by which requests are received

and responses are returned. Each Connector passes requests on to the

associated Container (normally an Engine) for processing.

By default, a non-SSL HTTP/1.1 Connector is established on port 8080.

You can also enable an SSL HTTP/1.1 Connector on port 8443 by

following the instructions below and uncommenting the second Connector

entry. SSL support requires the following steps (see the SSL Config

HOWTO in the Tomcat 4.0 documentation bundle for more detailed

instructions):

* Download and install JSSE 1.0.2 or later, and put the JAR files

into $JAVA_HOME/jre/lib/ext.

* Execute:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)

$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)

with a password value of changeit for both the certificate and

the keystore itself.

By default, DNS lookups are enabled when a web application calls

request.getRemoteHost(). This can have an adverse impact on

performance, so you can disable it by setting the

enableLookups attribute to false. When DNS lookups are disabled,

request.getRemoteHost() will return the String version of the

IP address of the remote client.

--

!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --

Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 
minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 
acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false 
disableUploadTimeout=true/

Connector className=org.apache.coyote.tomcat4.CoyoteConnector address=test 
port=3030 minProcessors=5 maxProcessors=75 enableLookups=true 
redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 
useURIValidationHack=false disableUploadTimeout=true/

!-- Note : To disable connection timeouts, set connectionTimeout value

Tomcat reboot runtime

2004-05-13 Thread Rudolf Feyerkleist
Is there a way to restart tomcat from a webapplication running on tomcat? Or is there 
a way for canges to the server.xml of tomcat to become effective at runtime?

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

RE: Tomcat reboot runtime

2004-05-13 Thread Rudolf Feyerkleist
1. The original question was if there is some highly tomcat-specific code that enables 
a reboot at runtime. Spending very little time going through the source code of 
catalina, it seems to me that even highly tomcat-specific code does not support a 
reboot a runtime.
2. One solution could be to call a shell script from within the webapplication running 
on Tomcat, reboot Tomcat, accepting in this way that the application and tomcat will 
be unavailable during some reboot time. On the other hand, this could not be regarded 
as a good coding practice, in my opinion.
3. Another solution could be to have the application create a new process in the JVM 
responsible for stopping and starting the tomcat service. But then again this process 
could only do so by calling a script as in the solution proposed in 2, with it same 
consequences (seems to me I might as well be wrong).
 
I would be very pleased with any comments on the above
 
Rudolf Feyerkleist
 
NB As a relative novice to Tomcat it astonishs me that the Tomcat Manager does not 
provide the functionnality to reboot the server at runtime (taking in account that it 
services become unavailable during reboot time).

Shapira, Yoav [EMAIL PROTECTED] wrote:

Hi,
What's running your program (in order to wait and issue a startup
command) after you've done a shutdown? ;)

(Unless you're talking about highly tomcat-specific code that shuts down
tomcat and leaves the JVM itself running)

Yoav Shapira
Millennium Research Informatics




-
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2' 

URGENT: Axis Tomcat webservices at runtime

2004-05-05 Thread Rudolf Feyerkleist

System: 

Windows XP Pro 

Tomcat 4.1.27 

J2RE 1.4.2_01 

Axis 1.1 

I am using Axis to deploy webservices during Tomcat runtime. I use AdminClient.main to 
deploy the webservices, JAVA2WSDL.main to generate the WSDL at runtime in my 
webapplication. When I restart Tomcat after deployement and wsdl generation, 
everything works fine. When I try to access the new webservice wsdl during runtime 
without restarting Tomcat, I get a LifeCycle Error, CL stopped. Does anybody know if 
it is possible to access the new webservice (deployed with its wsdl) at runtime 
without restarting tomcat? 

Rudolf Feyerkleist



-
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs