----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files.  Don't make us guess your problem!!!
----------------------------------------------------------------


Garrison,

you are absolutely my favorite person in the world today. Your script
worked 1-2-3, just like these things are supposed to. Better yet, I am
having none of the aggravating problems I was having on SCO trying to
refresh the servlet.

I plan to tattoo your instructions to the inside of my eyelids.

Thanks again! and thanks everyone else for help as well.

Jim


At 12:59 PM 4/27/2000 -0400, Garrison Roberts wrote:
>----------------------------------------------------------------
>BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
>WHEN YOU POST, include all relevant version numbers, log files,
>and configuration files.  Don't make us guess your problem!!!
>----------------------------------------------------------------
>
>    Oh, I've never compiled it in statically, since everything I've read
>says, "To ensure greater flexibility in the future use of the Apache server,
>use Dynamic Shared Object support".  It makes sense to me perhaps more than
>to you becuase the configuration excerpts I just gave you were slightly
>abridged versions of the commands I actually use, since I also use mod_ssl
>and various jdbc drivers when I build the server.  In that case, DSO is
>invaluable to me, since I can plug in anything I want at any time, like if I
>feel like adding PHP4 later on or something.  Are you sold on a static build
>for some reason, so that DSO isn't an option?
>    To really answer your question, there's nothing wrong with building a
>statically compiled-in JServ, but I've not done it and I thought I could
>help you since I know how to build it one way very well.  If you change your
>mind on static vs. DSO, the instructions below should do you well.
>
>----- Original Message -----
>From: Jim Miani <[EMAIL PROTECTED]>
>To: Java Apache Users <[EMAIL PROTECTED]>
>Sent: Thursday, April 27, 2000 12:40 PM
>Subject: RE: Apache won't recognize JServ
>
>
>----------------------------------------------------------------
>BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
>WHEN YOU POST, include all relevant version numbers, log files,
>and configuration files.  Don't make us guess your problem!!!
>----------------------------------------------------------------
>
>
>I did not do a shared object build - I have the source distribution for
>both Apache and JServ - thus the LoadModule directive is
>commented out in jserv.conf - is this wrong for some reason?
>
>At 12:30 PM 4/27/2000 -0400, Kirk Benson wrote:
>>----------------------------------------------------------------
>>BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
>>WHEN YOU POST, include all relevant version numbers, log files,
>>and configuration files.  Don't make us guess your problem!!!
>>----------------------------------------------------------------
>>
>>I suspect that the JServ module is not being loaded at startup.  Check the
>>pathname of the loadmodule directive in jserv.conf.
>>
>>> -----Original Message-----
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Miani
>>> Sent: Thursday, April 27, 2000 11:11 AM
>>> To: Java Apache Users
>>> Subject: Apache won't recognize JServ
>>>
>>>
>>> ----------------------------------------------------------------
>>> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
>>> WHEN YOU POST, include all relevant version numbers, log files,
>>> and configuration files.  Don't make us guess your problem!!!
>>> ----------------------------------------------------------------
>>>
>>>
>>> Hi, I hate to be a barnacle-like newbie, but I'm _still_ having
>>> trouble installing JServ. I've given up on SCO Open Server because of the
>>> servlet returning an empty document problem I was talking about on this
>>> list about a week ago.
>>>
>>> I've now moved over to Linux - Red Hat 6.1 Pro - and I'm having a
>>> completely different problem. Apache 1.3.12 and JServ 1.1
>>>
>>> I cannot get Apache to recognize the fact that JServ is out there
>>> and should
>>> have servlet requests passed to it. Apache starts and runs fine, but
>JServ
>>> does
>>> not get launched - there is nothing in the log file to indicate an error.
>>>
>>> If I compare the log files from my SCO server where JServ is working
>>> intermittently,
>>> there is a difference. On SCO, when I restart Apache, I get
>>> [Wed Apr 26 18:40:03 2000] [notice] Apache/1.3.12 (Unix)
>>> ApacheJServ/1.1.1b1 ...
>>> but on Linux,
>>> [Thu Apr 27 10:47:26 2000] [notice] Apache/1.3.12 (Unix) configured -- re
>>>
>>> so it doesn't look like Apache is attempting to start JServ at
>>> all. Also, if I
>>> try to access a servlet from the browser, I get a 404 and a look
>>> at the log
>>> file shows that it is trying to find a document called
>>> /servlets/Hello, rather
>>> than passing the request off to JServ. It's as if Apache has no idea that
>>> JServ
>>> exists!
>>>
>>> If I start JServ up manually, it _seems_ to run fine - it logs a
>>> startup message to the jserv.log, ps -eaf | grep java shows the threads
>>> running, no problems I can see.
>>>
>>> A few points:
>>> 1. I DID reconfigure, make and install Apache AFTER I configured, made
>and
>>> installed
>>>    JServ. I did it twice to be absolutely sure.
>>> 2. I did put Include /usr/local/jserv/etc/jserv.conf into Apache's
>>> httpd.conf file.
>>>
>>> My questions:
>>>
>>> 1. Anybody have any idea what I'm doing wrong?
>>> 2. Is there a way I can test JServ in manual mode - i.e. pass an
>>> HTTP request
>>>    to it - I tried using ab but get a message "broken pipe"
>>>
>>> Thanks ...
>>>
>>> Jim
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>==========================================================================
>>> Jim Miani
>>> ICANON Associates, Inc.
>>> Phone: 610-313-1850 x 121
>>> Fax: 610-313-1848
>>>
>>> NEWZwareT is a product of ICANON Inc. - Visit our web site at
>>> http://www.icanon.com/ for more information on ICANON, the
>>> company, and its
>>> suite of products and services.
>>>
>>>
>>> --
>>> --------------------------------------------------------------
>>> Please read the FAQ! <http://java.apache.org/faq/>
>>> To subscribe:        [EMAIL PROTECTED]
>>> To unsubscribe:      [EMAIL PROTECTED]
>>> Archives and Other:  <http://java.apache.org/main/mail.html>
>>> Problems?:           [EMAIL PROTECTED]
>>>
>>
>>
>>
>>--
>>--------------------------------------------------------------
>>Please read the FAQ! <http://java.apache.org/faq/>
>>To subscribe:        [EMAIL PROTECTED]
>>To unsubscribe:      [EMAIL PROTECTED]
>>Archives and Other:  <http://java.apache.org/main/mail.html>
>>Problems?:           [EMAIL PROTECTED]
>>
>>
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe:        [EMAIL PROTECTED]
>To unsubscribe:      [EMAIL PROTECTED]
>Archives and Other:  <http://java.apache.org/main/mail.html>
>Problems?:           [EMAIL PROTECTED]
>
>
>
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe:        [EMAIL PROTECTED]
>To unsubscribe:      [EMAIL PROTECTED]
>Archives and Other:  <http://java.apache.org/main/mail.html>
>Problems?:           [EMAIL PROTECTED]
>
>

==========================================================================
Jim Miani
ICANON Associates, Inc.
Phone: 610-313-1850 x 121
Fax: 610-313-1848

NEWZware� is a product of ICANON Inc. - Visit our web site at
http://www.icanon.com/ for more information on ICANON, the company, and its
suite of products and services.


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to