Re: ZipException: Access is denied

2002-07-03 Thread Cynthia Jeness

Liam,

This is not a security issue with OS/2 since there are not different levels of users
and we have verified that the files are accessible.  Further, we can make the
problem go away by just switching to a back level JDK without changing anthing about
Tomcat or our deployed web app.

Cynthia Jeness

Liam Morley wrote:

> Cynthia,
> I was experiencing that exception on the latest JDK from Sun (j2se
> 1.4.0_01) which I just downloaded yesterday. This is in Windows XP Pro;
> the user that's executing Tomcat (at the moment) does not have
> Administrator rights. My path is C:\Apache\jakarta\tomcat4.1.3-beta\ (no
> spaces). Specifically, I saw this exception when tomcat tried expanding
> a WAR file.
>
> Liam Morley
>
> Cynthia Jeness wrote:
>
> >Roger,
> >
> >We see a similar problem with the latest IBM JDK 1.3.1 for OS/2.  We have
> >assumed that it is a JDK problem because a version of the JDK just 1 month older
> >does not produce this problem.   We had been programming on Tomcat  since
> >December, 2001 and the problem first appeared a month ago when we got a "fix"
> >from IBM.
> >
> >We have never seen the problem on Sun's JDK for Linux.  We would like to report
> >the problem to IBM since it only occurs on the IBM JDK; however, this is no
> >longer possible for us under OIS/2.  So, try using a different vendor's JDK to
> >see if that solves your problem.   If it is an IBM JDK problem, then perhaps you
> >can report it as a problem under Windows which I am sure gets more attention
> >than OS/2.
> >
> >Cynthia Jeness
> >
> >Roger Adema wrote:
> >
> >
> >
> >>I've tried putting Tomcat into c:\tomcat-4.0 (changing %CATALINA_HOME% of
> >>course) and there's no change in behavior.  Also, I have no directory names
> >>with ".jar".
> >>
> >>Looking at the exception again, it seems to indicate that a native method
> >>is involved.  Do I need a zip.exe/unzip.exe or any other native zip support
> >>on my system for this to work?
> >>
> >>java.util.zip.ZipException: Access is denied
> >>at java.util.zip.ZipFile.open(Native Method)
> >>at java.util.zip.ZipFile.(ZipFile.java:127)
> >>at java.util.jar.JarFile.(JarFile.java:138)
> >>
> >>
> >>>
> >>>Another good one (which will result in a permission denied message) is
> >>>if you unpack a jar file into a directory with a .jar extension eg...
> >>>
> >>>%TOMCAT_HOME%/lib/xerces.jar/org...
> >>>
> >>>TomCat will choke on it as it can't unpack the directory that it
> >>>believes is a file.
> >>>
> >>>
> >>>
> >>>
> >>Andy Eastham wrote:>
> >>
> >>
> >>>>Roger,
> >>>>
> >>>>Try putting tomcat in a path with no spaces, eg c:\apache_tomcat_4.0
> >>>>
> >>>>As for classpath, any jars under tomcat\webapps\app_name\WEB_INF\lib
> >>>>
> >>>>
> >>(your
> >>
> >>
> >>>>webapps private classesd)or tomcat\common\lib (classes shared between
> >>>>webapps, usually db drivers etc) will be automatically included in the
> >>>>classpath.
> >>>>
> >>>>All the best,
> >>>>
> >>>>Andy
> >>>>
> >>>>
> >>>>
> >>>>
> >>--
> >>To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> >>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> >>
> >>
> >
> >
> >--
> >To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> >
> >
> >
> >
> >
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


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




Re: ZipException: Access is denied

2002-07-03 Thread Cynthia Jeness

Roger,

Sorry for the delay in respose, but I have been out of town with no access to
email.

Yes, I see the problem on the start-up of Tomcat and it is very reproducible.

Cynthia Jeness

Roger Adema wrote:

> Cynthia, just to confirm it's the same problem - are you seeing the
> exception on startup of Tomcat?  If so, I'll pursue reporting the problem
> to the appropriate people at IBM.
>
> Roger
>
> 
>
> Roger,
>
> We see a similar problem with the latest IBM JDK 1.3.1 for OS/2.  We have
> assumed that it is a JDK problem because a version of the JDK just 1 month
> older
> does not produce this problem.   We had been programming on Tomcat  since
> December, 2001 and the problem first appeared a month ago when we got a
> "fix"
> from IBM.
>
> We have never seen the problem on Sun's JDK for Linux.  We would like to
> report
> the problem to IBM since it only occurs on the IBM JDK; however, this is no
> longer possible for us under OIS/2.  So, try using a different vendor's JDK
> to
> see if that solves your problem.   If it is an IBM JDK problem, then
> perhaps you
> can report it as a problem under Windows which I am sure gets more
> attention
> than OS/2.
>
> Cynthia Jeness
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


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




Re: ZipException: Access is denied

2002-06-27 Thread Cynthia Jeness

Roger,

We see a similar problem with the latest IBM JDK 1.3.1 for OS/2.  We have
assumed that it is a JDK problem because a version of the JDK just 1 month older
does not produce this problem.   We had been programming on Tomcat  since
December, 2001 and the problem first appeared a month ago when we got a "fix"
from IBM.

We have never seen the problem on Sun's JDK for Linux.  We would like to report
the problem to IBM since it only occurs on the IBM JDK; however, this is no
longer possible for us under OIS/2.  So, try using a different vendor's JDK to
see if that solves your problem.   If it is an IBM JDK problem, then perhaps you
can report it as a problem under Windows which I am sure gets more attention
than OS/2.

Cynthia Jeness

Roger Adema wrote:

> I've tried putting Tomcat into c:\tomcat-4.0 (changing %CATALINA_HOME% of
> course) and there's no change in behavior.  Also, I have no directory names
> with ".jar".
>
> Looking at the exception again, it seems to indicate that a native method
> is involved.  Do I need a zip.exe/unzip.exe or any other native zip support
> on my system for this to work?
>
> java.util.zip.ZipException: Access is denied
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.(ZipFile.java:127)
> at java.util.jar.JarFile.(JarFile.java:138)
> >
> >
> >
> >Another good one (which will result in a permission denied message) is
> >if you unpack a jar file into a directory with a .jar extension eg...
> >
> >%TOMCAT_HOME%/lib/xerces.jar/org...
> >
> >TomCat will choke on it as it can't unpack the directory that it
> >believes is a file.
> >
> >
> Andy Eastham wrote:>
> >
> >>Roger,
> >>
> >>Try putting tomcat in a path with no spaces, eg c:\apache_tomcat_4.0
> >>
> >>As for classpath, any jars under tomcat\webapps\app_name\WEB_INF\lib
> (your
> >>webapps private classesd)or tomcat\common\lib (classes shared between
> >>webapps, usually db drivers etc) will be automatically included in the
> >>classpath.
> >>
> >>All the best,
> >>
> >>Andy
> >>
> >>
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


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




Shutdown Error - /WEB-INF/lib/commons-digester missing

2002-06-18 Thread Cynthia Jeness

I am using the 4.1 version of Tomcat contained in the JWSDP (Java Web
Services Developers Pack EA2) from Sun along with the versions of
startup.sh and shutdown.sh provided.  My platform is Linux RedHat 7.1.
Tomcat starts and functions correctly; however, when I use the shutdown
script to stop it, I get the error that the "commons-digester" is
missing.  More specifically, the catalina log entry looks like this:

WebappClassLoader:   Resource '/WEB-INF/lib/commons-digester.jar' is
missing.


I have even tried putting the "commons-digester.jar" in the lib
directory of the Root context, but the error persists on shutdown.  The
latest scripts appear virtually identical to those that I used under
Tomcat 4.0.3 where I did not see the problem.

Any suggestions as to the source of the error.

Cynthia Jeness



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




Re: Tomcat 4 install / config

2002-05-29 Thread Cynthia Jeness

Eric,

I am using the 4.0.3 version of Tomcat and installed through RPM.  The name of
the startup file is "tomcat4" and is in /usr/bin.

Cynthia Jeness

Eric Etkin wrote:

> Configuration:
>
> RH Linux 7.3
> Tomcat 4.1
> Apache 2.0
>
> Installations done via RPM for everything
> I have installed Apache, and it works fine (i.e I get the default page) I
> installed Tomcat and all the related prerequisites.
>
> I cannot find the startup.sh file, I have looked everywhere.  Is it missing
> from my RPM somehow?  I tried running: "tomcat4 start" and it looks like it
> does something, but when I try to browse to "127.0.0.1:8080" I get nothing.
>
> Any advice would be much appreciated.
>
> I'm a Linux Newbie, so please be gentle. :)
>
> Thanks!
>
> -Eric Etkin
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


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




Re: DataSource from JNDI always null

2002-04-23 Thread Cynthia Jeness

I have also experienced 1. below.  Does anyone know of there is any resolution?  We 
are temporarily running servlets which use this through Tomcat directly.

Cynthia Jeness

"Clearwater, Pete" wrote:

> Hi Nick.
>
> I had similar problems, and have found out a couple of things:
>
> 1.  I could not get my datasources to be found when using the WARP connector.  Same 
>thing as you - null DataSource.  No idea what the problem was here.
>
> 2.  Initially I could not get it to work at all, but found that if I used the 
>parameter "url" instead of "driverName" then everything was OK (except for 1. above).
>
> cheers.  Isn't debugging this JNDI stuff fun?  The log messages sure give lots of 
>useful information
>
> pete.
>
> -Original Message-
> From: nickJohnson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 19, 2002 8:07 PM
> To: [EMAIL PROTECTED]
> Subject: DataSource from JNDI always null
>
> I thought I had this problem fixed, but it has come up again.
>
> Basically I'm just trying to grab a JDBC resource for a postgresql
> database.  My code looks something like this:
>
> public static Connection getConnection(char mode)
>   throws NamingException, SQLException {
> Context ctx = null;
>
> ctx = new InitialContext();
> Context envCtx = (Context) ctx.lookup("java:comp/env");
> String dbname = "jdbc/" + (mode == 'w'? "dbrw" : "dbro");
> DataSource ds = (DataSource) envCtx.lookup(dbname);
> Connection c = ds.getConnection();
> return c;
> }
>
> This code is called as a static method on a utility class from inside a
> bean used by a JSP document.
>
> Of course what happens is I get a null pointer exception trying to call
> getConnection on ds.  Here's the relevent information from server.xml.
> I'll paste in only the entry for "dbrw".  dbro is identical except it uses
> a different username.  Both have the same problem.  I have verified that I
> can log in both using the command line tool and a quick and dirty jdbc
> test program.
>
>  type="javax.sql.DataSource"/>
>  
> 
>   user
>   www
> 
> 
>   password
>   
> 
> 
>   driverClassName
>   org.postgresql.Driver
> 
> 
>   driverName
>   jdbc:postgresql://localhost:5432/main/value>
> 
>  
>
> And in web.xml (I've decided to use the server's web.xml rather than the
> context's):
>
>   
> 
>Resource reference to a java.sql.Connection factory
> 
> jdbc/dbrw
> javax.sql.DataSource
> Container
>   
>
> postgresql.jar and the jdbc extensions are in common/lib.  As far as I can
> tell from snooping traffic across lo0, no connection attempt is ever made,
> although I do see plenty of traffic from my little jdbc test program.
>
> Any pointers would be greatly appreciated, especially any information on
> debugging problems with JNDI, getting diagnostic information out of it,
> etc.  A working postgresql config would be even better. My instinct about
> this is that I have JNDI set up incorrectly, or the jdbc drivers are not
> getting found or initialized properly, but having exhausted all my ideas,
> I thought I'd ask for a pointer :)
>
> Many thanks,
>
>Nick
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Re: mod_webapp + httpd.conf

2002-04-19 Thread Cynthia Jeness

I believe that this is a known problem and one suggested workaround is
to do the following:

"Uncomment the line "ServerName=localhost" and changed
"localhost" to "www.ajug.org". Unless this line is uncommented, then
Apache will generate an error (Invalid virtual host name) when
restarted. "

Of course, change "localhost" to the correct name of your server.
"www.ajug.org" is my web server.  You can find our Tomcat4 how-to at
this URL:

   http://www.ajug.org/howto/tomcat4.html


Cynthia Jeness
Web Chair, Atlanta Java Users Group


Karoly VEGH wrote:

> Hello,
>
> i try to get apache communicate with tomcat,
>
> i have the following section in my httpd.conf:
>
> >8-
>
> 
>  WebAppConnection conn  warp  localhost:8008
>  WebAppDeploy examplesconn  /examples
> # WebAppInfo /webapp-info
> 
>
> -8<
>
> WebAppDeploy takes three arguments,   
>
> the problem is at apachectl configtest:
>
> Syntax error on line 1039 of /etc/apache/httpd.conf:
> Invalid virtual host name
>
> the 1039th line is WebAppDeploy examplesconn  /examples
>
> what virtual host does he await?
>
> tia,
>
> Charlie
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Which Connector for Tomcat 4.0.3 - mod_webapp or mod_jk

2002-04-19 Thread Cynthia Jeness

I searched the Tomcat and Apache site yesterday for some explanation
and/or recommendations for the choice of connector, but a search on
"connector" or "mod_webapp" did not seem to provide any information
about why I would chooce one over another.  Can someone point me to the
correct place or explain the difference between these connectors.

Thanks,

Cynthia Jeness


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Rolling File Appender Type Log

2002-04-19 Thread Cynthia Jeness

Under Tomcat, there appear to be only three types of loggers available:

1.  FileLogger - which writes to a new file each day.
2.  SystemOutLogger - which logs to system out
3.  SystemErrLogger - which logs to system error

Further in the case of "valves" for web logs, it appears that the only
option is getting a new file each day.


We have clients whose standards dictate a "rolling  file appender"
similar to what you can get from log4j. Therefore, we use log4j for
our own logging; however, this still leaves all of the logging that
Tomcat does directly.  Is there anyway to plug-in a rolling file
appender?  I have tried extending LoggerBase myself, but it appears not
to be public access.

Cynthia Jeness


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Re: TomCat RPM's

2002-01-02 Thread Cynthia Jeness


Donald,

The rpm builds two files in /usr/bin -- tomcat4 and tomcatd.  To start
or
stop Tomcat, just use tomcat4 start or tomcat4 stop.  One other issue
with
the RPM is that it su's to the tomcat4 user, but the var/tomcat4
directory
is owned by root.  The tomcat4 user needs at least write access to the
logs
directory.  Finally, the default port is 8180 and not 8080 with the rpm.

Other than that, the rpm worked fine.

Based on my experience, I put together my own documentation -- some of
this
is specific to our AJUG (Atlanta Java User Group) site.  If you are
interested, check out:

http://www.ajug.org/howto/tomcat4.html

Cindy Jeness


Donald Lee wrote:

> I went to
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/rpms/

> downloaded tomcat4-4.0.1-1.noarch.rpm
> installed using rpm -iv tomcat4-4.0.1-1.noarch.rpm
> everything appeared to be going ok until I came to the part in the doc

> file I found called running.txt
>
> "execute shell command:
> $CATALINA_HOME/bin/startup.sh"
>
> That didn't work.
> It turns out my Tomcat installation went to
> /var/tomcat4
> which is where I set $CATALINA_HOME to.
> I looked in the $CATALINA_HOME/bin directory and to my surprise, there

> was no startup.sh, only a bootstrap.jar.  I searched my whole system
> for a startup.sh and could not find one, so I decided that something
> was dreadfully wrong, and went back to the tomcat site.
> I went into
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/bin/
> this time and downloaded jakarta-tomcat-4.0.1.zip
> I unpacked it and it created it's own directory of
> jakarta-tomcat-4.0.1.  I basically cut and pasted the contents of that

> directory into my /var/tomcat4 directory and over wrote all
> directories and files.  I then ran $CATALINA_HOME/bin/startup.sh and
> tested my installation with http://localhost:8080 and all appears to
> be well.I have a question, when I installed the rpm it created a
> directory etc/tomcat4/conf/tomcat4.conf.  As this was not part of my
> list of installation procedures, can I assume that this directory/file

> is not needed?  I was wondering if I could safely delete this
> directory or is something left out of the running.txt file?
> Can anybody tell me what the purpose of the rpms are if they do not
> properly install tomcat?
>
> Thanks, and God Bless and have a happy new year!
>
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 





--
To unsubscribe:   
For additional commands: 
Troubles with the list: 




Re: mod_webapp -- EAPI error

2001-12-26 Thread Cynthia Jeness

John,

By searching through Google, I discovered this link to a slightly older set of  RPMS 
for
Tomcat including one for mod_webapp:

http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0/rpms/

This is not the link that you get from the Jakarta site.  The Jakarta link ends wiht
"4.0.1/rpms".

When I installed the 4.0/rpm version of mod_webapp, then my "EAPI" error went away and 
I
could load the "HelloWorldExample" servlet.  However, the changes that the RPM made to 
the
httpd.conf file seemed to be incorrect.  So I deleted these and added the lines 
specified
in the README.txt for mod_webapp.

I would still like to understand  how to compile from source and get an appropriate 
module
since it seems like the rpm for mod_webapp is not always provided.  Further, some of 
our
systems run Apache on Solaris where I need to be able to compile the source.

So, can anyone from the Apache team please help with this issue?

Cynthia


John Clayton wrote:

> I have just experienced the very same issue with the binary.  What's
> more, I can't even get configure to run while trying to build it from
> source, as it is reporting a syntax error on line 5.  Hmm 
>
> On Wednesday, December 26, 2001, at 10:45 AM, Cynthia Jeness wrote:
>
> > I got the sources for Apache 1.3.22, compiled and installed.
> >
> > Then I got the sources for mod_webapp.  After unpacking, I did the
> > following as described in the "README.txt" file:
> >
> > ./support/buildconf.sh
> > CFLAGS=-DEAPI \
> > ./configure --with-apxs=/usr/local/bin
> >
> > Then I executed make.  Watching the compiles display on my screen, the
> > "-DEAPI" flag was specified.
> >
> > The sources compiled and "mod_webapp.so" was created.  Then I copied
> > this module to my Apache modules directory,  modified the httpd.conf as
> > directed in the README.txt and started Apache.  Apache did start, but I
> > received the following warning:
> >
> > starting httpd: [Wed Dec 26 09:21:24 2001] [warn] Loaded DSO
> > modules/mod_webapp.so uses plain Apache 1.3 API, this module might crash
> > under EAPI! (please recompile it with -DEAPI)
> >
> > This is exactly the same warning that I get when I attempted to use the
> > binary module from the Jakarta site.  I have double checked that I am
> > using my newly compiled module.  This is easy to do because my freshly
> > compiled module is only 165852 while the binary module was 437664
> > bytes.  So, why are these files so different in size; and, more
> > importantly, how do I get rid of this warning?
> >
> > Below is the "Makedefs" file which was generated as part of my building
> > mod_webapp.so from source:
> >
> > Please help so that I can "Have fun..."
> >
> > Cynthia Jeness
> >
> > 
>-
> >
> >
> >
> > # @author  Pier Fumagalli <mailto:[EMAIL PROTECTED]>
> > # @version $Id: Makedefs.in,v 1.11 2001/09/17 00:42:59 pier Exp $
> >
> > .SUFFIXES: .c .o
> >
> > #
> > -
> >
> > # Programs discovered by "configure" during initialization
> > #
> > -
> >
> > TEST = /usr/bin/test
> > TRUE = /bin/true
> > ECHO = /bin/echo
> > GREP = /bin/grep
> > CAT = /bin/cat
> > SED = /bin/sed
> > LN = /bin/ln
> > RM = /bin/rm
> >
> > #
> > -
> >
> >  Compilation settings and Makefile macros
> > #
> > -
> >
> > # The target module to build
> > MODULE = apache-1.3
> > # The system which built this binary
> > SYSTEM = linux-gnu-i686
> > # Wether to build debug information or not
> > DEBUG = false
> > # The WebApp sources directory
> > SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40
> > # The compilation (this) directory
> > TGTDIR = /home/cj/tomcat/webapp-module-1.0-tc40
> > # The directory of a Tomcat 4.0 binary distribution
> > TC4DIR =
> > # The list of configure-generated files
> > CFGFILES = ./Makefile ./Makedefs ./lib/Makefile ./java/Constants.java
> > ./apache-1.3/Makefile ./config.cache
> > ./config.log ./config.status
> > # The file holding the list of makefile-generated files
> > LSTFILE = $(TGTDIR)/config.list
> > # GNU-Make style ech

mod_webapp -- EAPI error

2001-12-26 Thread Cynthia Jeness

I got the sources for Apache 1.3.22, compiled and installed.

Then I got the sources for mod_webapp.  After unpacking, I did the
following as described in the "README.txt" file:

./support/buildconf.sh
CFLAGS=-DEAPI \
./configure --with-apxs=/usr/local/bin

Then I executed make.  Watching the compiles display on my screen, the
"-DEAPI" flag was specified.

The sources compiled and "mod_webapp.so" was created.  Then I copied
this module to my Apache modules directory,  modified the httpd.conf as
directed in the README.txt and started Apache.  Apache did start, but I
received the following warning:

starting httpd: [Wed Dec 26 09:21:24 2001] [warn] Loaded DSO
modules/mod_webapp.so uses plain Apache 1.3 API, this module might crash
under EAPI! (please recompile it with -DEAPI)

This is exactly the same warning that I get when I attempted to use the
binary module from the Jakarta site.  I have double checked that I am
using my newly compiled module.  This is easy to do because my freshly
compiled module is only 165852 while the binary module was 437664
bytes.  So, why are these files so different in size; and, more
importantly, how do I get rid of this warning?

Below is the "Makedefs" file which was generated as part of my building
mod_webapp.so from source:

Please help so that I can "Have fun..."

Cynthia Jeness

-



# @author  Pier Fumagalli <mailto:[EMAIL PROTECTED]>
# @version $Id: Makedefs.in,v 1.11 2001/09/17 00:42:59 pier Exp $

.SUFFIXES: .c .o

#
-

# Programs discovered by "configure" during initialization
#
-

TEST = /usr/bin/test
TRUE = /bin/true
ECHO = /bin/echo
GREP = /bin/grep
CAT = /bin/cat
SED = /bin/sed
LN = /bin/ln
RM = /bin/rm

#
-

 Compilation settings and Makefile macros
#
-

# The target module to build
MODULE = apache-1.3
# The system which built this binary
SYSTEM = linux-gnu-i686
# Wether to build debug information or not
DEBUG = false
# The WebApp sources directory
SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40
# The compilation (this) directory
TGTDIR = /home/cj/tomcat/webapp-module-1.0-tc40
# The directory of a Tomcat 4.0 binary distribution
TC4DIR =
# The list of configure-generated files
CFGFILES = ./Makefile ./Makedefs ./lib/Makefile ./java/Constants.java
./apache-1.3/Makefile ./config.cache
./config.log ./config.status
# The file holding the list of makefile-generated files
LSTFILE = $(TGTDIR)/config.list
# GNU-Make style echo
MECHO = $(ECHO) "$(MAKE)[$(MAKELEVEL)]:"
#
-

# APR library values
#
-

# The APR source directory (if needed)
APR_SRCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr
# Where libapr.a resides
APR_LIBDIR = /home/cj/tomcat/webapp-module-1.0-tc40/lib
# Where APR include files are located
APR_INCDIR = /home/cj/tomcat/webapp-module-1.0-tc40/apr/include
# Location of APRVARS
APR_VARFIL = /home/cj/tomcat/webapp-module-1.0-tc40/apr/APRVARS
# Extra APR C compilation flags
APR_CFLAGS =
# Extra APR C macro pre-processor flags
APR_CPPFLAGS = -DLINUX=2 -D_REENTRANT
# Extra APR inclusion flags
APR_INCLUDES =
# Extra APR linker flags
APR_LDFLAGS =
# Extra APR libraries required for linking
APR_LIBS = -lm -lcrypt -lnsl -ldl
#
-

# C Compiler settings
#
-

# Library archiver
AR = /usr/bin/ar
# C compiler
CC = /usr/bin/gcc
# C macro pre-processor
CPP = /usr/bin/gcc -E
# Library updater
RANLIB = /usr/bin/ranlib
# C compilation flags
CFLAGS = -DEAPI
# C macro pre-processor flags
CPPFLAGS =

#
-

# Java Compiler settings
#
-

# The JVM home directory
JAVA_HOME =
# Jar archiver
JAR =
# Java compiler
JAVAC =
# JavaDoc documentation tool
JAVADOC =
# Java compilation flags
JAVACFLAGS =
# Java Class Path
CLASSPATH =

#
-

# ScanDoc Documentation tool settings
#
-

# PERL interpreter
PERL =
# ScanDoc documentation tool
SCANDOC =
# Scandoc flags
SCANDOCFLAGS =

#
-

# C-Compilation default setting
#
-

ALL_CFLAGS = $(CFLAGS) $(CP

Re: Problem Installing Tomcat.4.0.1 on Redhat Linux 7.0

2001-12-26 Thread Cynthia Jeness

Stan,

The "webapp-module-1.0..." just contains the WebApp connector.  You also need
to get either the rpm or the tgz for Tomcat itself.  Then you will get the
stuff that you are missing.

In terms of the syntax error, was it something like "Invalid virtual server
name...".  This has bee address at least twice on then Tomcat mailing list, but
since the solutions seemed different (again I am not an Apache expert), I am
not sure which approach is best.  The first solution was to uncomment the
"ServerName" line.

Cynthia

Stan Levine wrote:

> Thank you, Cynthia, for your response.
> 1) Regarding the tomcat libraries, that I can't find,
> (bin,conf,doc,lib,logs,webapps), I did not install tomcat from a RPM. I used
> the binary ( webapp-module-1.0-tc40-linux-glibc2.2.tar.gz.), did the gunzip
> and tar extract. I still can't find these directories.
> 2) After I added th theWebAppConnection and WebAppDeplay lines to
> httpd.conf, I got a syntax error on the WebAppDeploy line when I started
> tomcat.  Maybe it was because there is no /examples directory.  Where should
> this be?
>
> Thanks.
>
> Stan
> - Original Message -
> From: "Cynthia Jeness" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, December 25, 2001 11:34 AM
> Subject: Re: Problem Installing Tomcat.4.0.1 on Redhat Linux 7.0
>
> > Stan Levine wrote:
> >
> > > I am new to Linux, Apache and Tomcat. I am trying to install Tomcat
> 4.0.1. I already have Apache 1.3.12
> > > installed as part of my Redhat Linux 7.0 installation. I  downloaded
> webapp-module-1.0-tc40-linux-glibc2.2.tar.gz.
> > > 1) First I ran gunzip and built the tar file
> > > 2) Then I ran tar -xvf webapp-module-1.0-tc40-linux-glibc2.2.tar to
> extract the files.
> > > 3) Then I followed the instructions in
> > > webapp-module-1.0-tc40/INSTALL.txt
> > >  a) I copied mod_webapp.do to my modules directory
> > > /usr/lib/apache
> > >  b) I added the LoadModule and AddModule lines to
> > >  /etc/httpd/httpd.conf
> > > ---> I can't find the apachect1 script.  My ServerName is /etc/httpd.
> This contains directory conf,
> >
> > Redhat does not provide this with.  Since this is just an edit check on
> your installation, it is not critical to run this.
> >
> >
> > >
> > >  and link logs ---> /var/log/httpd, and link modules --->
> /usr/lib/apache.  There is  no apachect1 script file in any of these
> directories.  Also, where are the apache scripts to start and stop apache?
> >
> > The script is /etc/rc.d/init.d/httpd
> >
> > It uses the standard options of "start", "stop" and "restart".
> >
> >
> > >
> > > ---> Regard the next instructions:  do I add the WEBAPPConnection and
> WebAppDeploy statements to
> > >httpd.conf just they are in the instructions? or do they
> require modification?
> >
> > If you just want to run the examples, then these should work.  However, I
> get an error about "invalid virtual host name".  There are various comments
> in this email archive about how to work arround this.
> > This last comment that I read was to
> > uncomment the "ServerName" directive in "/etc/httpd/conf/httpd.conf.
> >
> > >
> > > ---> I can't find the server.xml file, or any of the
> directories(bin,conf,doc,lib,logs,webapps) that are supposed to be in
> > > the standard Tomcat setup.
> > >
> >
> > If you installed Tomcat4 from the rpm, then go to "/var/tomcat4".  Also,
> there was a "tomcat4" startup script installed in "/usr/bin".
> >
> > >
> > >Thanks for your help.
> > >
> > >   Stan
> >
> > I have successfully gotten Tomcat started under RedHat 7.1, but I cannot
> get mod_webapp to work correctly.  The fundamental problem is that the
> binary version of mod_webapp was not compiled with the
> > options required to run with the Apache installed with RedHat 7.1.  I have
> tried compiling from source, but so far that has not been successful.
> Basically, you need more that the source provided with
> > mod_webapp and even when I downloaded all of the Apache source and tried
> to compile, it complained about something broken in the "apx" directory.
> >
> > I hope that those who build mod_webapp will recognize that many of us
> using Tomcat are basically Java programmers with stock installations o

Re: Problem Installing Tomcat.4.0.1 on Redhat Linux 7.0

2001-12-25 Thread Cynthia Jeness

Stan Levine wrote:

> I am new to Linux, Apache and Tomcat. I am trying to install Tomcat 4.0.1. I already 
>have Apache 1.3.12
> installed as part of my Redhat Linux 7.0 installation. I  downloaded 
>webapp-module-1.0-tc40-linux-glibc2.2.tar.gz.
> 1) First I ran gunzip and built the tar file
> 2) Then I ran tar -xvf webapp-module-1.0-tc40-linux-glibc2.2.tar to extract the 
>files.
> 3) Then I followed the instructions in
> webapp-module-1.0-tc40/INSTALL.txt
>  a) I copied mod_webapp.do to my modules directory
> /usr/lib/apache
>  b) I added the LoadModule and AddModule lines to
>  /etc/httpd/httpd.conf
> ---> I can't find the apachect1 script.  My ServerName is /etc/httpd. This contains 
>directory conf,

Redhat does not provide this with.  Since this is just an edit check on your 
installation, it is not critical to run this.


>
>  and link logs ---> /var/log/httpd, and link modules ---> /usr/lib/apache.  There is 
> no apachect1 script file in any of these directories.  Also, where are the apache 
>scripts to start and stop apache?

The script is /etc/rc.d/init.d/httpd

It uses the standard options of "start", "stop" and "restart".


>
> ---> Regard the next instructions:  do I add the WEBAPPConnection and WebAppDeploy 
>statements to
>httpd.conf just they are in the instructions? or do they require 
>modification?

If you just want to run the examples, then these should work.  However, I get an error 
about "invalid virtual host name".  There are various comments in this email archive 
about how to work arround this.
This last comment that I read was to
uncomment the "ServerName" directive in "/etc/httpd/conf/httpd.conf.

>
> ---> I can't find the server.xml file, or any of the 
>directories(bin,conf,doc,lib,logs,webapps) that are supposed to be in
> the standard Tomcat setup.
>

If you installed Tomcat4 from the rpm, then go to "/var/tomcat4".  Also, there was a 
"tomcat4" startup script installed in "/usr/bin".

>
>Thanks for your help.
>
>   Stan

I have successfully gotten Tomcat started under RedHat 7.1, but I cannot get 
mod_webapp to work correctly.  The fundamental problem is that the binary version of 
mod_webapp was not compiled with the
options required to run with the Apache installed with RedHat 7.1.  I have tried 
compiling from source, but so far that has not been successful.  Basically, you need 
more that the source provided with
mod_webapp and even when I downloaded all of the Apache source and tried to compile, 
it complained about something broken in the "apx" directory.

I hope that those who build mod_webapp will recognize that many of us using Tomcat are 
basically Java programmers with stock installations of Apache.  So we really need a 
"mod_webapp" that works with
these stock distributions.  Also, there seem to be problems with the directions with 
regard to updating httpd.conf.  Perhaps these problems are trivial for Apache experts, 
but again I do not think that
servlet progammers necessary fall into this category.

So if you do manage to get mod_webapp working with out the "DEAPI" warning, then 
please post your success story.

Happy Holidays to all,
Cynthia Jeness





--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Re: Jakarta-Tomcat 4.01 startup problem

2001-12-22 Thread Cynthia Jeness

John,

It appears to me that Tomcat4 listens on port 8180 and not port 8080.  This
is what I see through "lsof" and I can connect to "locahost:8180".

Cynthia Jeness

John Clayton wrote:

> OK -
>
> I figured out service.  I got tomcat to start, at least service says
> it's started.  But ... requesting localhost:8080 gets a connection
> failure.  Anyone come across this?
>
> I am using RedHat 7.2 for this.
>
> Thanks,
>
> John
>
> On Saturday, December 22, 2001, at 06:51 PM, John Clayton wrote:
>
> > Kenneth,
> >
> > forgive my ignorance here, I'm new to using Tomcat on Linux.  you say
> > use service, what is that?  the rpm installed only bootstrap.jar in my
> > tomcat4/bin directory, not the usual .sh files.  Anybody?
> >
> > Thanks,
> >
> > John
> >
> >
> > --
> > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > For additional commands: <mailto:[EMAIL PROTECTED]>
> > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> >
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Re:

2001-12-22 Thread Cynthia Jeness

What shell?

For Bash and Korn shell:

JAVA_HOME=/usr/java/jdk1.3.1 (for example)
export JAVA_HOME

The "C" shell uses "setenv"; e.g.,

setenv JAVA_HOME /usr/java/jdk1.3.1

Windows and OS/2 use "SET".

Cynthia Jeness

Ladjicke Diouf wrote:

> Hi
>
> Unix gurus, I'm trying to install tomcat but I'm having a very simple
> problem. I can seem to be able to set the environment variable JAVA_HOME. I
> used set end setenv but it doesn't do it for me. Am I going crazy?
>
> >From: "rakesh" <[EMAIL PROTECTED]>
> >Reply-To: "Rakesh Narang" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: Tomcat with apache for virtual hosting
> >Date: Sun, 23 Dec 2001 06:00:34 +0530
> >
> >Hi
> >
> >I have recently installed the tomcat 4.0.1 with apache but i am facing the
> >problem while using the virtual hosting with tomcat can any one help me
> >that how can i host multiple sites on tomcat
> >
> >Thanks
> >Rakesh
>
> _
> Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>




Need Binary web-app Module for RedHat 7.1

2001-12-22 Thread Cynthia Jeness

When I tried to install the webapp-module in order to connect tomcat to
Apache, I got the warning that the module might crash and that I needed
to recompile with DEAPI.  So I got the source code for the weapp-module
as a tar.gz file from the Apache site.  The README file indicated that
the source code should be complete.  However, all of my attempts to
recompile folling the instructions in the README fail.

1.  There is no configure as described in the "README".
2.  I managed to build one with the buildconf in support using the
following command:

./support/buildconf.sh CFLAGS=-DEAPI

Is this the correct way to get the "-DEAPI" flag?

3.  The README file says to run:

./configure --with-apxs

Unfortunately, I do not have "apxs" with my RedHat distribution...


Since Apache is servicing a production web site, I really do not feel
comfortable rebuilding Apache just to get the webapps module built
correctly.  Also, because the README file seems to presume that one is
already intimately familiar with how to build appache components, the
chance of success seems relatively low.

I did go through the mailing list archives and there definitely seems to
be problems related to building and installing this webapps module.
Therefore, I was hoping that someone would have an appropriate pre-built
module with "-DEAPI" for RedHat 7.1 on Intel or at least a better source
of documentation.

I have even a more basic question.  I assume that the webapps module is
the replacement for mod_jserv which I used under previous versions of
Tomcat.  Is this correct?  Again, maybe I am looking in the wrong place,
but I just could not find current documentation on how to connect to
Apache.

Thanks in advance,

Cynthia Jeness




--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>