Installation Problem

2004-07-21 Thread Phillip Blancher
Good day,
I am using IBServer on a Windows 2000 Box. Installed is apache 1.3.26, PHP 
4.2 and I am trying to get Tomcat to work.

Tomcat runs as a Windows Service with no errors.
Apache runs fine with the jk_mod installed.
My httpd.conf is listening for ports 80, 8080 and 8009 for processing JSP.
The problem is I can never get JSP files on localhost or IP assigned for the 
server to run on outside the network. I keep getting prompted to save the 
JSP source in IE.

I have set up 5 VirtualHosts for webspace off the server plus the main space 
and I am using just IP addresses.

My goal is to have all 6 IP's able to server JSP or PHP.
Listed below is the httpd.conf (with approprate IP's removed and such)
ALso listed is the mod_jk.conf file.
Thank you in advance for the help.
Phil
--- httpd.conf 
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://www.apache.org/docs/> for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#
# After this file is processed, the server will look for and process
# D:/IBserver/Apache/conf/srm.conf and then 
D:/IBserver/Apache/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as 
a
# whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' 
server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# ServerType is either inetd, or standalone.  Inetd mode is only supported 
on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
ServerRoot "D:/IBserver/Apache"
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile logs/httpd.pid
#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this.  But if yours does (you'll know 
because
# this file will be  created when you run Apache) then you *must* ensure 
that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile logs/apache_runtime_status

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order.  The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults.  You can have 
the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait fo

Installation problem

2003-04-01 Thread dutta_kaushik

Hi All,

I installed tomcat 4.1 on Solaris OS.
While running i get an error which is given
below:


java.util.zip.ZipException: invalid END header (bad central directory offset)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:112)
at java.util.jar.JarFile.(JarFile.java:117)
at java.util.jar.JarFile.(JarFile.java:55)
at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(
StandardClassLoader.java:1082)
at org.apache.catalina.loader.StandardClassLoader.(StandardClassLo
ader.java:200)
at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(Clas
sLoaderFactory.java:202)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:140)
Bootstrap: Class loader creation threw exception
java.lang.IllegalArgumentException: addRepositoryInternal: java.util.zip.ZipExce
ption: invalid END header (bad central directory offset)
at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(
StandardClassLoader.java:1110)
at org.apache.catalina.loader.StandardClassLoader.(StandardClassLo
ader.java:200)
at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(Clas
sLoaderFactory.java:202)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:140)



can anyone tell me that what could be the cause of this error and
how can it be rectified.



Thanks,

Kaushik



* * * The information contained in this message is legally privileged and confidential
information intended only for the use of the addressed individual or entity indicated 
in
this message (or responsible for delivery of the message to such person). It must not 
be
read, copied, disclosed, distributed or used by any person other than the addressee.
Unauthorised use, disclosure or copying is strictly prohibited and may be unlawful.
 Opinions, conclusions and other information on this message that do not relate to the
official business of any of the constituent companies of the TATA CONSULTANCY SERVICES
shall be understood as neither given nor endorsed by the Group. If you have received 
this
message in error, you should destroy this message and kindly notify the sender by 
e-mail.
Thank you. * * *

This eMail has been scanned by Interscan Viruswall

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

DO NOT REPLY [Bug 6310] - Tomcat 4.0.1 installation problem with Solaris 7

2002-02-07 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6310>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6310

Tomcat 4.0.1 installation problem with Solaris 7

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WORKSFORME



--- Additional Comments From [EMAIL PROTECTED]  2002-02-07 16:00 ---
It works for me fine on normal JDK versions. It's probably an installation 
error of some sort, but the information given in the report is extremely 
unconclusive. It would be a good idea to post on tomcat-user to investigate.

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




DO NOT REPLY [Bug 6310] New: - Tomcat 4.0.1 installation problem with Solaris 7

2002-02-07 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6310>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6310

Tomcat 4.0.1 installation problem with Solaris 7

   Summary: Tomcat 4.0.1 installation problem with Solaris 7
   Product: Tomcat 4
   Version: 4.0.1 Final
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Blocker
  Priority: Other
 Component: HTTP/1.1 Connector
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I am running Solaris 7 (SPARC) with java 1.1.7, when I tried to start the binary
distribution of tomcat 4.0.1 I got some nasty java errors. I pulled down java
1.3.1_02 and installed it in a local directory and updated the JAVA_HOME variable.

When I start up tomcat with the newer java, I do not get any startup errors in
cataling.out but I don't get a normal standard web page when I connect to port
8080 (get a Not Found message from browser) and the access logs are not being
updated in the logs directory. It looks like the server is running but not
working properly.

Any ideas if this is a java version problem?  Port 8080 does allow connections
but it does not seem to be working properly.

The startup messages are:

Starting service Tomcat-Standalone
Apache Tomcat/4.0.1

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