----------------------------------------------------------------
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 Michael

The simply explanation is that different Linux dists, use  different unix
threads implementations and different JDK's prefer different
implementations.... as I recall it is a thread persistence issue.   I'm a
SuSE linux/SCO linux  man, so I can't give you much on mandrake (I think
that is what you were using).

Certainly under SuSE you just change the line sin rc.config  to.

JAVARUNT_THREADS_TYPE="green"
JAVA_THREADS_TYPE="green"

I'm sure mandrake has a similar setup. Also have a look in your java
documentation for JVM parameters, but is short:

/usr/local/jdk1.2.2/bin/i386/green_threads/java  

Runs java using green threads,  and  :

/usr/local/jdk1.2.2/bin/i386/native_threads/java

Runs with Native threads.... go figure:) 

hth 

Chris



>I did a buncha searching on this during my two days of sweat and tears, and it looked 
>like roughly 1/2 of the advice (mostly in Deja) was "use native threads -- green 
>threads don't work" and 1/2 of the advice was "use green threads -- native threads 
>don't work". I couldn't see a strong correlation between the advice and the JDK 
>version. Mystified, I wished for someone to tell me *why* the problem was occurring, 
>and also wished for some better error messages. Chris, can you shed some light? Also, 
>how do you 'set threads to green (or to native)'? 
>
>At 11:58 PM 6/21/00 +0950, you 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!!!
>>----------------------------------------------------------------
>>
>>This may be off base, but worth a thought.
>>
>>When I was using JServ on SuSE Linux running Blackdown 1.1.8 (as I
>>remember) , JServ segfaulted often.
>>
>>After a lot of sweat and tears.. and when I had nearly no hair left , I
>>tracked it down to a bug that is more noted for using Blackdown 1.2.2 on
>>RedHat. You have to set threads to green.
>>
>>I don't know if this is what is causing you guys the problem, but maybe it
>>is of some use to you.
>>
>>Good luck!
>>
>>Chris
>>
>>On Wed, 21 Jun 2000 16:06:17 +0200, [EMAIL PROTECTED] 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 have:
>> >
>> >        Linux Mandrake 6.0 (kernel 2.2.9)
>> >        Apache-1.3.12
>> >        ApacheJServ-1.1.1
>> >        JSDK-2.0
>> >        JDK-1.1.8
>> >
>> >I find a similar problem while accessing
>> >http://localhost/servlets/IsItworking
>> >
>> >jserv.log says:
>> ><jservException> AJP Protocol Error: java.io.IOException: Stream broken
>> >
>> >error_log says:
>> >child pid nnnn exit signal Segmentation fault (11)
>> >
>> >Meanwhile, mod_jserv.log doesn't hear what is happening:
>> >(INFO) Apache-JServ 1rst  initialization: JVM will be started later 1 1364 1363
>> >(INFO) Apache Module was cleaned-up
>> >(INFO) Apache-JServ 2nd  initialization starting JVM now: 1 1365 1
>> >(INFO) wrapper classpath: 
>> >/usr/lib/apache/ApacheJServ.jar:/home/httpd/classes/servlet-2.0.jar:/usr/lib/cla
>> >sses/jsdk.jar
>> >(INFO) wrapper: Java VM spawned (PID=1378, PPID=1366)
>> >(INFO) Apache Module was cleaned-up
>> >(INFO) Wrapper: Shutting down JServ (PID=1366) (sig 15)
>> >(INFO) wrapper: Terminating JServ (PID=1366, VM PID=1378)
>> >(INFO) ajp12: sending shutdown signal
>> >
>> >What can I try? Where should I read? Do you have any clue?
>> >
>> >Lorenzo
>> >
>> >
>> >
>> >______________________________ Reply Separator _________________________________
>> >Subject: Re: Jserv seg. fault
>> >Author:  dawalt ([EMAIL PROTECTED]) at internet
>> >Date:    21/06/2000 14:35
>> >
>> >
>> >     
>> >Yes I found it, the README in the JSDK 2.0 says that with JDK 1.2 the servlet 
>> >API is bundled with the JDK 1.2. This isn't true is it? Am I messing things 
>> >up by pointing the classpath to another JAR? Couldn't get the IsItWorking to 
>> >compile otherwise...
>> >     
>> >     
>> >----- Original Message -----
>> >From: "Don Awalt" <[EMAIL PROTECTED]>
>> >To: "Java Apache Users" <[EMAIL PROTECTED]> 
>> >Sent: Wednesday, June 21, 2000 8:06 AM
>> >Subject: Re: Jserv seg. fault
>> >     
>> >     
>> >>
>> >> Thanks for the feedback!
>> >>
>> >> I am confused about one thing, maybe someone can answer - does Sun's J2SE 
>> >> JDK 1.2.2 contain the servlet API? It does not appear to (although in the 
>> >> documentation for J2SDK or JServ I believe it says it is included in the 
>> >> JDK!), I have it explicitly pointed to by my wrapper.classpath entry. Is 
>> >> this correct?
>> >>
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Michael Deck" <[EMAIL PROTECTED]>
>> >> To: "Java Apache Users" <[EMAIL PROTECTED]> 
>> >> Sent: Tuesday, June 20, 2000 6:10 PM
>> >> Subject: Re: Jserv seg. fault
>> >>
>> >>
>> >> >
>> >> > Don, I had this problem too, and it drove me nuts for the last two days. 
>> >> Turned out that all my servlets stopped working when I upgraded to 
>> >JDK1.2.2
>> >> but I didn't know it because nobody reported the problem. I backed off to 
>> >> Blackdown 1.1.8 and they started working. Maybe this fact was in the faq 
>> >> somewhere; there was a bunch of material about what compilers are 
>> >supported
>> >> that I struggled through without fully understanding. 
>> >> >
>> >> > The other piece of wisdom which *is* in the faq, is to be sure that 
>> >rt.jar
>> >> is in wrapper.classpath. Without that, you wont get the SIGSEGV but you 
>> >will
>> >> get an EMERGENCY.
>> >> >
>> >> > -Mike
>> >> >
>> >> > At 05:48 PM 6/20/00 -0400, you 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 am at my wits end getting JServer to run right: 
>> >> > >
>> >> > >Config:
>> >> > >==========
>> >> > >
>> >> > >Mandrake 7.1
>> >> > >kernel 2.2.15
>> >> > >Apache 1.3.12
>> >> > >JServ 1.1.1-1
>> >> > >glibc 2.1.3
>> >> > >J2SE jdk 1.2.2 (Sun)
>> >> > >450 MHz dual CPU
>> >> > >
>> >> > >Problem
>> >> > >========
>> >> > >I install JServ after verifying Apache is running fine, and I get a 
>> >> > >segmentation fault trying to run "IsItWorking" servlet.
>> >> > >No other messages or logs identifying a potential problem. 
>> >> > >
>> >> > >
>> >> > >Things I have tried/verified:
>> >> > >===================
>> >> > >1. java is installed properly - I can compile and run programs
>> >> > >2. I can recompile IsItWorking.java without problems (JDSK 2.0 is in 
>> >J2SE
>> >> > >jdk 1.2.2 I believe)
>> >> > >3. I can install JSDK 2.0 explicitly on the machine, and ServletRunner 
>> >> > >listening on port 8080 runs IsItWorking and other servlets fine
>> >> > >4. Tried mucking around with wrapper.classpath to add all the .jar 
>> >files
>> >> > >explicitly (do not install that way by default, I installed JServ 
>> >through
>> >> an
>> >> > >RPM file which appears to configure everything ok)
>> >> > >5. Validated jserv.properties file with FAQs, emails from people, etc. 
>> >> > >6. Checked gary meyer's HOWTO (which shows it to be incredibly straight 
>> >> > >forward to get this working, which leaves me clueless!)
>> >> > >
>> >> > >I have done a lot more that I can't think of now. To me it seems like 
>> >> some
>> >> > >sort of incompatibility (jsdk and jdk? Jserv 1.1.1-1 and Apache or 
>> >> kernel?)
>> >> > >
>> >> > >Any help, or advice how to track down would be GREATLY appreciated! 
>> >> > >
>> >> > >
>> >> > >
>
>
>Michael Deck
>Cleanroom Software Engineering, Inc.   
>
>
>--
>--------------------------------------------------------------
>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]

Reply via email to