----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Matthew
Maybe the reason noone has responded is since there has been quite a bit
of discussion on the seg violation issue on this and many other lists.
The general view is that these are generally hardware related and as such
are not a software issue.
My first move is usually to change the RAM on the machine behaving this
way. The other major cause I found was on PC's running Linux on
overclocked CPU's or overheating CPU's.
Have you tried this servlet on another machine? Does it behave the same?
What JVM are you running?
Chris
On Fri, 03 Nov 2000 13:00:39 -0600, Matthew Mello 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!!!
>----------------------------------------------------------------
>
>Okay, I'll try this again. You guys are my only hope.
>
>It appears that the class loader or JVM is crashing on me with a
>segmentation violation. This sounds like a MAJOR bug in the JVM.
>However, I have found no references to anything like it anywhere in the
>newsgroups. Does anyone have any information on a bug that would
>produce the error listed below?
>
>Thanks!
>
>
>Matthew Mello 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 using Apache JServ 1.1 on Apache 1.3.9 for Spark Solaris 2.6, with
>> my jar in the <javainstall>/jre/lib/ext directory (which seems to work
>> fine, or did until today).
>>
>> I'm not sure which list I should post this question on. Please tell me
>> if you know.
>>
>> We are moving our product closer to the production environment, and
>> since we will have lots of traffic, I opened up the system to multiple
>> threads (quit using SingleThreadModel for servlets).
>>
>> Anyway, now that I have a couple of daemon threads going, I'm getting
>> this segmentation fault when the system is supposed to be loading a
>> class [Class.forName("whatever")]. Any idea where this would come from
>> or how to debug it?
>>
>> Thanks for any help anyone can offer or for redirection!
>>
>> - Matt
>>
>> SIGSEGV 11* segmentation violation
>> si_signo [11]: SIGSEGV 11* segmentation violation
>> si_errno [0]: Error 0
>> si_code [1]: SEGV_MAPERR [addr: 0x4c8b308]
>>
>> stackpointer=EB27EE90
>> "Thread-30" (TID:0x7e9aa4, sys_thread_t:0x7e99e8, state:R, thread_t:
>> t@38, threadID:0xeb280dd8, stack_bottom:0xeb281000, stack_size:0x20000)
>> prio=5 *current thread*
>>
>> [1] java.lang.Class.forName0(Native Method)
>> [2] java.lang.Class.forName(Class.java:125)
>> [3]
>> net.paymate.connection.ActionRequest.fromProperties(ActionRequest.java:91)
>> [4]
>> net.paymate.connection.ConnectionServer.ReplyTo(ConnectionServer.java:324)
>> [5] net.paymate.web.UserSession.ReplyTo(UserSession.java:158)
>> [6] net.paymate.servlet.TxnServlet.doPost(TxnServlet.java:68)
>> [7] javax.servlet.http.HttpServlet.service(HttpServlet.java:521)
>> [8]
>> net.paymate.servlet.SessionedServlet.service(SessionedServlet.java:104)
>> [9] javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
>> [10]
>> org.apache.jserv.JServConnection.processRequest(JServConnection.java:314)
>> [11] org.apache.jserv.JServConnection.run(JServConnection.java:170)
>> [12] java.lang.Thread.run(Thread.java:484)
>> -------------------
>>
>> Exiting Thread (sys_thread_t:0xef761df0) : no stack
>> "Session Cleaner" (TID:0x41b944, sys_thread_t:0x41b888, state:CW,
>> thread_t: t@10, threadID:0xeb0b0dd8, stack_bottom:0xeb0b1000,
>> stack_size:0x20000) prio=5
>>
>> [1] java.lang.Thread.sleep(Native Method)
>> [2] net.paymate.servlet.CleanerThread.run(SessionCleaner.java:105)
>> -------------------
>> "Thread-2" (TID:0x33d9c4, sys_thread_t:0x33d908, state:CW, thread_t:
>> t@8, threadID:0xeb2b0dd8, stack_bottom:0xeb2b1000, stack_size:0x20000)
>> prio=5
>>
>> [1] java.lang.Thread.sleep(Native Method)
>> [2]
>> org.apache.jserv.JServServletManager.run(JServServletManager.java:998)
>> [3] java.lang.Thread.run(Thread.java:485)
>> -------------------
>> "Thread-1" (TID:0x339d3c, sys_thread_t:0x339c80, state:CW, thread_t:
>> t@7, threadID:0xee6b0dd8, stack_bottom:0xee6b1000, stack_size:0x20000)
>> prio=1
>>
>> [1] java.lang.Object.wait(Object.java:424)
>> [2] org.apache.java.util.SimpleQueue.waitObject(SimpleQueue.java:116)
>> [3] org.apache.java.io.LogWriter$Agent.run(LogWriter.java:427)
>> -------------------
>> "Finalizer" (TID:0x149e04, sys_thread_t:0x149d48, state:CW, thread_t:
>> t@6, threadID:0xee820dd8, stack_bottom:0xee821000, stack_size:0x20000)
>> prio=8
>>
>> [1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:106)
>> [2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:128)
>> [3] java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:175)
>> -------------------
>> "Reference Handler" (TID:0x14668c, sys_thread_t:0x1465d0, state:CW,
>> thread_t: t@5, threadID:0xee850dd8, stack_bottom:0xee851000,
>> stack_size:0x20000) prio=10
>>
>> [1] java.lang.Object.wait(Object.java:424)
>> [2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:107)
>> -------------------
>> "Signal dispatcher" (TID:0x126dac, sys_thread_t:0x126cf0, state:MW,
>> thread_t: t@4, threadID:0xee890dd8, stack_bottom:0xee891000,
>> stack_size:0x20000) prio=10
>>
>> -------------------
>> "main" (TID:0x38564, sys_thread_t:0x384a8, state:R, thread_t: t@1,
>> threadID:0x25130, stack_bottom:0xf0000000, stack_size:0x20000) prio=5
>>
>> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
>> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
>> [3] java.net.ServerSocket.implAccept(ServerSocket.java:237)
>> [4] java.net.ServerSocket.accept(ServerSocket.java:223)
>> [5]
>>
>org.apache.java.net.AuthenticatedServerSocket.accept(AuthenticatedServerSocket.java:160)
>> [6] org.apache.jserv.JServ.main(JServ.java:127)
>> -------------------
>> [Mon Oct 30 18:04:00 2000] [error] [client 24.167.70.105] Premature end
>> of script headers: /servlets/txn
>>
>> --
>> --------------------------------------------------------------
>> Please read the FAQ! <http://java.apache.org/faq/>
>> To subscribe: [EMAIL PROTECTED]
>> To unsubscribe: [EMAIL PROTECTED]
>> Search Archives:
>> <http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
>> Problems?: [EMAIL PROTECTED]
>
>--
>Matt Mello
>Home: 512-266-7081
>Cell: 512-350-6900
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Search Archives:
><http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
>Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]