Service Temporarily Unavailable
inform...@lrsl.lu
When I want to start my iManager I always get the message:
Service Temporarily Unavailable.
But this temporarily message comes all the time.
What can that be? I have restarted Apache and TomCat, no change.
Thanks for your help
Hubert
Marcel Cox
to access iManager? If there an error code shown in the web browser (like
500 or 503)?
--
Marcel Cox
http://support.novell.com/forums
inform...@lrsl.lu
I use as OS OES (Netware), Apache 2.0.54. As error code I get 503.
The URL which doesn't work is
https://<server IP adress>:2200 and then I click on iManager.
But even if I use
http://<server Ip adress>/nps/servlet/configure
I get the same error message an using
http://<server Ip adress>.iManager.html
I get : Page not found.
The Ip adress is an intranet number.
Hubert
Marcel Cox
before) is expired certificates. If your certificates have expired, then
Tomcat will not start correctly and so iManager will not work.
I suggest you run PKIDIAG.NLM on your server and see if it can find/fix
any certificate errors.
inform...@lrsl.lu
We deleted both certificates and created new ones with PKIDIAG.NLM.
We even ran TCKEYGEN.NCF.
Same result, nothing changed.
Hubert
Marcel Cox
startup. For this, first make sure that tomcat is stopped by using the
console command:
tc4stop
Now wait half a minute and then execute the command:
tomcat4
Now switch to the logger screen and look if there are any error messages.
Report all error messages you see.
Also, could you give some more background information on your problem
please:
- what support pack is installed on the server? What version of iManger?
- did iManager ever work on this server?
- if iManager worked before, what event cause it to stop working?
inform...@lrsl.lu
Copyright (C) 2000-01, 2004-05 Novell, Inc. All Rights
Reserved.
Loading module PERL.NLM status
OK
Perl 5.8.4 - Command Line
Interface
Version 5.00.05 13 September
2005
Copyright (C) 2000-01, 2004-05 Novell, Inc. All Rights
Reserved.
Auto-Loading Module
LIBPERL.NLM
Auto-loading module
LIBPERL.NLM
Perl 5.8.4 - Script Interpreter and
Librarym.
Version 5.00.05 13 September 2005andard locale
("C").
Copyright (C) 2000-01, 2004-05 Novell, Inc. All Rights
Reserved.
Module LIBPERL.NLM load status
OKt/4
Module PERL.NLM load status
OKmcat/4/temp
perl: warning: Setting locale
failed.
perl: warning: Please check that your locale
settings:
java: ClLC_ALL = (unset),plication.tomcat.util.tccheck.LDAPVerifier
exited succe
ssfully LANG =
(unset)
are supported and installed on your system.ster.Digester
fatalError
perl: warning: Falling back to the standard locale ("C").ing instruction
target
Using CATALINA_BASE:
sys:/tomcat/4ed.
Using CATALINA_HOME: sys:/tomcat/4rocessing instruction target
matching "[xX][
Using CATALINA_TMPDIR:
sys:/tomcat/4/temp
Using JAVA_HOME:
SYS:\javal.ErrorHandlerWrapper.createSAXParseException(Un
Doing a
stop)
Jul 6, 2006 2:23:34 PM org.apache.commons.digester.Digester fatalErrorwn
Source)
SEVERE: Parse Fatal Error at line 2 column 6: The processing instruction
target
matching "[xX][mM][lL]" is not
allowed.
org.xml.sax.SAXParseException: The processing instruction target
matching "[xX][
mM][lL]" is not
allowed.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un
known
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
Source)
at org.apache.xerces.impl.XMLScanner.scanPIData(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanPIData(Unkn
own
Source)
at org.apache.xerces.impl.XMLScanner.scanPI(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispat
ch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown
Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse
(Digester.java:1548)
at org.apache.catalina.startup.Catalina.stop
(Catalina.java:522)
at org.apache.catalina.startup.Catalina.execute
(Catalina.java:352)
at org.apache.catalina.startup.Catalina.process
(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main
(Bootstrap.java:156)
Catalina.stop: org.xml.sax.SAXParseException: The processing instruction
target
matching "[xX][mM][lL]" is not
allowed.
org.xml.sax.SAXParseException: The processing instruction target
matching "[xX][
mM][lL]" is not
allowed.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse
(Digester.java:1548)
at org.apache.catalina.startup.Catalina.stop
(Catalina.java:522)
at org.apache.catalina.startup.Catalina.execute
(Catalina.java:352)
at org.apache.catalina.startup.Catalina.process
(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main
(Bootstrap.java:156)
java: Class org.apache.catalina.startup.Bootstrap exited with status
1
org.jdom.JDOMException: Error on line 2: XML declaration may only begin
entities
.
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:367)
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:740)
at
com.novell.application.tomcat.util.tccheck.LDAPVerifier.parseServerXM
L
(LDAPVerifier.java:74)
at
com.novell.application.tomcat.util.tccheck.LDAPVerifier.parseServerXM
L
(LDAPVerifier.java:58)
at com.novell.application.tomcat.util.tccheck.LDAPVerifier.main
(LDAPVeri
fier.java:289)
Caused by: org.xml.sax.SAXParseException: XML declaration may only begin
entitie
s.
at org.apache.crimson.parser.Parser2.fatal
(Parser2.java:3376)
at org.apache.crimson.parser.Parser2.fatal
(Parser2.java:3364)
at org.apache.crimson.parser.Parser2.maybePI
(Parser2.java:1140)
at org.apache.crimson.parser.Parser2.maybeMisc
(Parser2.java:1266)
at org.apache.crimson.parser.Parser2.parseInternal
(Parser2.java:654)
at org.apache.crimson.parser.Parser2.parse
(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse
(XMLReaderImpl.java:448)
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:354)
... 4
more
Caused by: org.xml.sax.SAXParseException: XML declaration may only begin
entitie
s.
at org.apache.crimson.parser.Parser2.fatal
(Parser2.java:3376)
at org.apache.crimson.parser.Parser2.fatal
(Parser2.java:3364)
at org.apache.crimson.parser.Parser2.maybePI
(Parser2.java:1140)
at org.apache.crimson.parser.Parser2.maybeMisc
(Parser2.java:1266)
at org.apache.crimson.parser.Parser2.parseInternal
(Parser2.java:654)
at org.apache.crimson.parser.Parser2.parse
(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse
(XMLReaderImpl.java:448)
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:354)
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:740)
at
com.novell.application.tomcat.util.tccheck.LDAPVerifier.parseServerXM
L
(LDAPVerifier.java:74)
at
com.novell.application.tomcat.util.tccheck.LDAPVerifier.parseServerXM
L
(LDAPVerifier.java:58)
at com.novell.application.tomcat.util.tccheck.LDAPVerifier.main
(LDAPVeri
fier.java:289)
Caused by: org.xml.sax.SAXParseException: XML declaration may only begin
entitie
s.
at org.apache.crimson.parser.Parser2.fatal
(Parser2.java:3376)
at org.apache.crimson.parser.Parser2.fatal
(Parser2.java:3364)
at org.apache.crimson.parser.Parser2.maybePI
(Parser2.java:1140)
at org.apache.crimson.parser.Parser2.maybeMisc
(Parser2.java:1266)
at org.apache.crimson.parser.Parser2.parseInternal
(Parser2.java:654)
at org.apache.crimson.parser.Parser2.parse
(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse
(XMLReaderImpl.java:448)
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:354)
at org.jdom.input.SAXBuilder.build
(SAXBuilder.java:740)
at
com.novell.application.tomcat.util.tccheck.LDAPVerifier.parseServerXM
L
(LDAPVerifier.java:74)
at
com.novell.application.tomcat.util.tccheck.LDAPVerifier.parseServerXM
L
(LDAPVerifier.java:58)
at com.novell.application.tomcat.util.tccheck.LDAPVerifier.main
(LDAPVeri
fier.java:289)
Loading module
PERL.NLM
Perl 5.8.4 - Command Line
Interface
Version 5.00.05 13 September
2005
Copyright (C) 2000-01, 2004-05 Novell, Inc. All Rights
Reserved.
Auto-Loading Module
LIBPERL.NLM
Auto-loading module
LIBPERL.NLM
Perl 5.8.4 - Script Interpreter and
Library
Version 5.00.05 13 September
2005
Copyright (C) 2000-01, 2004-05 Novell, Inc. All Rights
Reserved.
Module LIBPERL.NLM load status
OK
Module PERL.NLM load status
OK
perl: warning: Setting locale
failed.
perl: warning: Please check that your locale
settings:
LC_ALL =
(unset),
LANG =
(unset)
are supported and installed on your
system.
perl: warning: Falling back to the standard locale
("C").
Using CATALINA_BASE:
sys:/tomcat/4
Using CATALINA_HOME:
sys:/tomcat/4
Using CATALINA_TMPDIR:
sys:/tomcat/4/temp
Using JAVA_HOME:
SYS:\java
Doing a
start
java: Class com.novell.application.tomcat.util.tccheck.LDAPVerifier
exited succe
ssfully
Jul 6, 2006 2:24:21 PM org.apache.commons.digester.Digester
fatalError
SEVERE: Parse Fatal Error at line 2 column 6: The processing instruction
target
matching "[xX][mM][lL]" is not
allowed.
org.xml.sax.SAXParseException: The processing instruction target
matching "[xX][
mM][lL]" is not
allowed.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un
known
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
Source)
at org.apache.xerces.impl.XMLScanner.scanPIData(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanPIData(Unkn
own
Source)
at org.apache.xerces.impl.XMLScanner.scanPI(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispat
ch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown
Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse
(Digester.java:1548)
at org.apache.catalina.startup.Catalina.start
(Catalina.java:420)
at org.apache.catalina.startup.Catalina.process
(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main
(Bootstrap.java:156)
Catalina.start using sys:\tomcat\4\conf\server.xml:
org.xml.sax.SAXParseExceptio
n: The processing instruction target matching "[xX][mM][lL]" is not
allowed.
org.xml.sax.SAXParseException: The processing instruction target
matching "[xX][
mM][lL]" is not
allowed.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse
(Digester.java:1548)
at org.apache.catalina.startup.Catalina.start
(Catalina.java:420)
at org.apache.catalina.startup.Catalina.execute
(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process
(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main
(Bootstrap.java:156)
java: Class org.apache.catalina.startup.Bootstrap exited with status
1
Hubert
Marcel Cox
>SYS:\javal.ErrorHandlerWrapper.createSAXParseException(Un
>Doing a
>stop)
>Jul 6, 2006 2:23:34 PM org.apache.commons.digester.Digester fatalErrorwn
>Source)
>SEVERE: Parse Fatal Error at line 2 column 6: The processing instruction
>target
>matching "[xX][mM][lL]" is not
>allowed.
>org.xml.sax.SAXParseException: The processing instruction target
>matching "[xX][
>mM][lL]" is not
>allowed.
This is an XML parsing problem similar to the one documented in the
following TID:
http://support.novell.com/docs/Tids/Solutions/10092883.html
Your server.xml file or some other xml file is corrupted, and the
corruption can be found in line 2 column 6 of the file. Alas, the file
name itself is not mentioned.
I would start with the server.xml file. Please post it here and I can take
a look to see what's wrong with it.
Marcel Cox
>- <!-- Example Server Configuration File
As this just an effect of your newsreader, or is there really a "-"
character in front of this and many other lines?
The "-" att he beginning of the line is certainly wrong and would cause
the XML parser to fail. Cehck if you have a server.bak file in the same
directory and see if it is identical or different.
inform...@lrsl.lu
CD. iManager did work before, but we can't tell you exactly since when it
stopped working.
Here is a copy of our server.xml:
<?xml version="1.0" encoding="Cp437" ?>
- <!-- 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>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/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="20000"
useURIValidationHack="false" disableUploadTimeout="true" />
-->
- <!--
Note : To disable connection timeouts, set connectionTimeout value
to -1
-->
- <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443
-->
- <!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" scheme="https" secure="true"
useURIValidationHack="false" disableUploadTimeout="true">
<Factory
className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
clientAuth="false" protocol="TLS" />
</Connector>
-->
- <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009
-->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="9010" minProcessors="5" maxProcessors="250" enableLookups="true"
acceptCount="10" debug="0" connectionTimeout="0"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" />
- <!-- Define an AJP 1.3 Connector on port 8009
-->
- <!--
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
-->
- <!-- Define a Proxied HTTP/1.1 Connector on port 8082
-->
- <!-- See proxy documentation for more information about using this.
-->
- <!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" useURIValidationHack="false"
disableUploadTimeout="true" />
-->
- <!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083
-->
- <!--
<Connector
className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
- <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084
-->
- <!--
<Connector
className="org.apache.catalina.connector.http10.HttpConnector"
port="8084" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
- <!--
An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes
them
on to the appropriate Host (virtual host).
-->
- <!--
You should set jvmRoute to support load-balancing via JK/JK2 ie :
<Engine name="Standalone" defaultHost="localhost" debug="0"
jmvRoute="jvm1">
-->
- <!-- Define the top level container in our container hierarchy
-->
- <Engine name="Standalone" defaultHost="localhost" debug="0">
- <!--
The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the
response
headers and cookies that were sent, for all requests received
by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry
instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the
following
element to enable it.
-->
- <!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
- <!-- Global logger unless overridden at lower levels
-->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt" timestamp="true" />
- <!-- Because this Realm is here, an instance will be shared globally
-->
- <!--
This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm.
-->
- <!--
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
-->
- <!--
This Realm uses the an LDAP directory for security. To add
a role, create a group in
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm.
-->
<Realm className="org.apache.catalina.realm.JNDIRealm"
connectionURL="ldap://localhost:636" debug="0" userPattern="cn=
{0},OU=administration,O=education" protocol="ssl" authentication="simple"
roleBase="ou=Tomcat-Roles,O=education" roleName="cn" roleSearch="member=
{0}" />
- <!--
Comment out the old realm but leave here for now in case we
need to go back quickly
-->
- <!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
- <!--
Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC
-->
- <!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name"
userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
- <!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name"
userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
- <!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name"
userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
- <!-- Define the default virtual host
-->
- <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true"
autoDeploy="true">
- <!--
Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would
like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have
that
user identity maintained across *all* web applications
contained
in this virtual host.
-->
- <!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
debug="0"/>
-->
- <!--
Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory
relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a
relative
(to $CATALINA_HOME) or absolute path to the desired
directory.
-->
- <!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log."
suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
- <!--
Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in
the "logs"
directory relative to $CATALINA_HOME. If you wish, you can
specify
a different directory with the "directory" attribute.
Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.
-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true" />
- <!--
Define properties for each web application. This is only needed
if you want to set non-default properties, or have web
application
document roots in places other than the virtual host's
appBase
directory.
-->
- <!-- Tomcat Root Context
-->
- <!--
<Context path="" docBase="ROOT" debug="0"/>
-->
- <!-- Tomcat Examples Context
-->
- <Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt" timestamp="true" />
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord" />
- <!--
If you wanted the examples app to be able to edit the
user database, you would uncomment the following entry.
Of course, you would want to enable security on the
application as well, so this is not done by default!
The database object could be accessed like this:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
UserDatabase database =
(UserDatabase) envCtx.lookup("userDatabase");
-->
- <!--
<ResourceLink name="userDatabase" global="UserDatabase"
type="org.apache.catalina.UserDatabase"/>
-->
- <!--
PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out.
minIdleSwap
limits this. -1 or 0 means unlimited sessions are
allowed.
If it is not possible to swap sessions new sessions will
be rejected.
This avoids thrashing when the site is highly active.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
activity.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked
periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the
Store,
but left in active memory) if idle for this long (in
seconds),
and all sessions found in the Store will be loaded on
startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions,
maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then
restart
Catalina.
-->
- <!--
<Manager
className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15" />
<Parameter name="context.param.name" value="context.param.value"
override="false" />
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource" />
- <ResourceParams name="jdbc/EmployeeAppDb">
- <parameter>
<name>username</name>
<value>sa</value>
</parameter>
- <parameter>
<name>password</name>
<value />
</parameter>
- <parameter>
<name>driverClassName</name>
<value>org.hsql.jdbcDriver</value>
</parameter>
- <parameter>
<name>url</name>
<value>jdbc:HypersonicSQL:database</value>
</parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session" />
- <ResourceParams name="mail/Session">
- <parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource" global="simpleValue"
type="java.lang.Integer" />
</Context>
</Host>
</Engine>
</Service>
- <!--
The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming
with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS
repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if
needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through
Apache.
-->
- <!-- Define an Apache-Connector Service
-->
- <!--
<Service name="Tomcat-Apache">
<Connector
className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true" appBase="webapps"
acceptCount="10" debug="0"/>
<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>
<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
-->
</Server>
-----------------
Thanks for helping us!
inform...@lrsl.lu
"-->" characters.
Marcel Cox
copying the text into the message.
BAsed on other information I got on this error, there must be a whitespace
problem in yoru server.xml file. E.g. some line contains a space character
or another character too much near the beginning of the file .
You might also try to remove the first line from your server.xml file, e.g.:
<?xml version="1.0" encoding="Cp437" ?>
On all servers I verified here, that line does not exist.
inform...@lrsl.lu
copying its content here?
Perhaps we should mention that we reinstalled iManager yesterday, so that
Server.xml and Server.bak are exactly the same.
inform...@lrsl.lu
fact the size is slightly different and there is no blank line at the
beginning. Now I copied the Server.xml from the working server to the
problem server.
It seems to be working now. But we have to test it with an administrator
login that I don't have.
Thank you very much for your help until now.
Bob Turping
CTE
Marcel Cox
>What do you mean by posting the Server.xml as an actual file, without
>copying its content here?
Oh, I see that you seem to be using the web interface to access the
forums. If you would use a newsreader to access the forums, you would be
able to post files as attachments instead of copying and pasting them into
the message.
--
Marcel Cox (using XanaNews 1.18.1.3)