What is Segmentation Violation?

Hi,
Recently, i've encouter Segmentation Violation. What is Segmentation Violation? What is the cause for it? Which area i should look into to solve this problem, because when is error happens, my program will crash.
Could anyone pls help me?
jhteo

Was this on linux? I was getting segmentation faults from jdk1.3, nothing to do with my java code (even java -version wouldn't work). I eventually changed the default vm to server, and the threads to something else (can't remember), and now it works.
m

Similar Messages

What is "segmentation violation" error?

My a servlet can run in my local(win2000+wl5.1),but run on
          server(unix+wl5.1),It will shutdown the wl.
          and report the error,message:
          SIGSEGV 11* segmentation violation
          si_signo [11]: SIGSEGV 11* segmentation violation
          si_errno [0]: Error 0
          si_code [1]: SEGV_MAPERR [addr:0x65ed408]
          stackpointer=F7EB0720
          what means???
          Thank you!


          see the platform page - you will need to set the JVMARS environmnet
          variable to turn of agressive JIT inlining.
          "sharetop" <[email protected]> wrote:
          >JVM version: Solaris_JDK_1.2.1_04
          >Unix platform: SunOS 5.7
          >
          >How can I deal it? Thank you.
          >
          >"Robert Patrick" <[email protected]> wrote
          >in message
          >news:[email protected]..
          >> This means that the program (in this case, the JVM)
          >crashed. What
          >> version of the JVM are you using (Unix command: java
          >-fullversion) and
          >> on what Unix platform (Unix command: uname -a)?
          >>
          >> sharetop wrote:
          >>
          >> > My a servlet can run in my local(win2000+wl5.1),but
          >run on
          >> > server(unix+wl5.1),It will shutdown the wl.
          >> > and report the error,message:
          >> >
          >> > SIGSEGV 11* segmentation violation
          >> >
          >> > si_signo [11]: SIGSEGV 11* segmentation violation
          >> > si_errno [0]: Error 0
          >> > si_code [1]: SEGV_MAPERR [addr:0x65ed408]
          >> > stackpointer=F7EB0720
          >> >
          >> > .....
          >> >
          >> > what means???
          >> >
          >> > Thank you!
          >>
          >
          >

Installing Oracle 8.1.7 on RHEL 3 (SIGSEGV 11* segmentation violation)

Hi
I have instaled a Oracle 8.1.7 on a Red Hat 3. and apply the 8.1.7 Mandatory OUI/JRE/GLIC Patch. All is fine until this point.
But when i must re-run the install and run the netasst& i get an segmentation violation.
I have checked all again, i have have uninstall all, and made a clean install, but i stil get the same error.
This is the full error. Can any one help please?
./netasst&
[1] 1726
[oracle@lisoms1 bin]$ SIGSEGV 11* segmentation violation
stackbase=0x41836000, stackpointer=0x41835a6c
Full thread dump:
"Image Fetcher 0" (TID:0x405ca908, sys_thread_t:0x3ffbde0c, state:R) prio=5
"TaskScheduler timer" (TID:0x405ca668, sys_thread_t:0x3ffdee0c, state:R) prio=5
"Thread-4" (TID:0x405c9200, sys_thread_t:0x3ffffe0c, state:R) prio=1
"AWT-Motif" (TID:0x405b2860, sys_thread_t:0x41890e0c, state:R) prio=5
java.lang.Thread.run(Thread.java)
"AWT-Input" (TID:0x405b2880, sys_thread_t:0x4186fe0c, state:CW) prio=5
"AWT-EventQueue-0" (TID:0x405b25e0, sys_thread_t:0x41835e0c, state:R) prio=5 current thread
java.lang.Object.wait(Object.java)
java.awt.EventQueue.getNextEvent(EventQueue.java:126)
java.awt.EventDispatchThread.run(EventDispatchThread.java:70)
"Finalizer thread" (TID:0x405ab210, sys_thread_t:0x412fde0c, state:CW) prio=1
"Async Garbage Collector" (TID:0x405ab258, sys_thread_t:0x412dce0c, state:CW) prio=1
"Idle thread" (TID:0x405ab2a0, sys_thread_t:0x412bbe0c, state:R) prio=0
"Clock" (TID:0x405ab088, sys_thread_t:0x4129ae0c, state:CW) prio=12
"main" (TID:0x405ab0b0, sys_thread_t:0x80eb190, state:CW) prio=5
java.lang.Object.wait(Object.java)
oracle.ewt.graphics.ImageLoader.waitFor(Unknown Source)
oracle.ewt.graphics.ImageUtils.loadImage(Unknown Source)
oracle.ewt.graphics.ImageUtils._getImageResource(Unknown Source)
oracle.ewt.graphics.ImageUtils.getImageResource(Unknown Source)
oracle.ewt.laf.oracle.OracleUIUtils.getImage(Unknown Source)
oracle.ewt.laf.oracle.OracleUIUtils.getColorizedImage(Unknown Source)
oracle.ewt.laf.oracle.OracleUIUtils.cImageInst(Unknown Source)
oracle.ewt.laf.basic.StringInstantiator.createValue(Unknown Source)
oracle.ewt.HashTableDefaults.getValue(Unknown Source)
oracle.ewt.MultiUIDefaults.getValue(Unknown Source)
oracle.ewt.UIDefaults.get(Unknown Source)
oracle.ewt.UIDefaults.get(Unknown Source)
oracle.ewt.UIDefaults.getImage(Unknown Source)
oracle.ewt.laf.oracle.OracleChoiceUI._createButtonPainter(Unknown Source)
oracle.ewt.laf.oracle.OracleChoiceUI.getButtonPainter(Unknown Source) oracle.ewt.lwAWT.LWDataSourceChoice$ChoiceButton.getPainter(Unknown Source)
oracle.ewt.lwAWT.AbstractPainterComponent.getInvalidateFlags(Unknown Source)
oracle.ewt.lwAWT.LWComponent.invalidateAndRepaintIfNecessary(Unknown Source)
oracle.ewt.lwAWT.LWComponent.enable(Unknown Source)
Monitor Cache Dump:
oracle.ewt.graphics.ImageLoader@1079814480/1080606192: <unowned>
Waiting to be notified:
"main" (0x80eb190)
<unknown key> (0x0x412dce0c): <unowned>
Waiting to be notified:
"Async Garbage Collector" (0x412dce0c)
oracle.ewt.lwAWT.LWChoice@1079812040/1080591384: owner "main" (0x80eb190, 2 entries)
sun.awt.motif.MToolkit@1079715432/1080130112: owner "AWT-Motif" (0x41890e0c, 0 entries)
Waiting to be notified:
"AWT-Input" (0x4186fe0c)
java.awt.EventQueue@1079715376/1080130376: owner "AWT-EventQueue-0" (0x41835e0c, 1 entry)
oracle.ewt.MultiUIDefaults@1079748416/1080283560: owner "main" (0x80eb190, 1 entry)
oracle.ewt.HashTableDefaults@1079745008/1080268568: owner "main" (0x80eb190, 1 entry)
Registered Monitor Dump:
Thread queue lock: <unowned>
Name and type hash table lock: <unowned>
String intern lock: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class loading lock: <unowned>
Java stack lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Has finalization queue lock: <unowned>
Finalize me queue lock: <unowned>
Waiting to be notified:
"Finalizer thread" (0x412fde0c)
Dynamic loading lock: <unowned>
Monitor IO lock: <unowned>
Child death monitor: <unowned>
Event monitor: <unowned>
I/O monitor: <unowned>
Alarm monitor: <unowned>
Waiting to be notified:
"Clock" (0x4129ae0c)
Monitor registry: owner "AWT-EventQueue-0" (0x41835e0c, 1 entry)
Thread Alarm Q:
sys_thread_t 0x412dce0c [Timeout in 831 ms]
./netasst: line 110: 1728 Killed $JRE -classpath $CLASSPATH oracle.net.asst.container.NetApplication oracle.net.asst.container.NetApplication
[1]+ Exit 137 ./netasst
Thank You
JailBreak

A have installed Oracle 8.1.5 on HP_UX 11.00 - 32 bit environment
I want to install/upgrade to Oracle 8.1.7 (64-bit)
1. Is there any problem with this aspect ? (Oracle 8.1.7. 64-bit on HP_UX 32 bit)
2. I need an advice regarding <new install> vs. <upgrading> ! I'm not sure if all operating system requirements are met (patch releases)
3. What are the risk of upgrading ?

Access/Segmentation Violation errors

Here's another one of those "Has anyone seen this" questions.
We are currently stress testing one of our applications and get the following
'Access/Segmentation Violation' error on a server partition:
Begin Stack Backtrace ==========================================================
Trace caused by a segmentation or access violation in the Forte executable:
Application: PCS_cl0
Platform: PC / NT
Partition: PCS_cl0_Part6
Generated: 02-Jul-2000 18:12:53
By: ftexec Version 3.0.G.2
Fault at 05-Jul-2000 06:46:24, pid '1810', node 'GRFD60':
User Name: FORTE_ACC
Machine Name: GRFD60 with 2 CPU(s)
OS version 4.0
Loading symbols for ...
d:\forte\install\bin\QQSH.dll
d:\forte\userapp\pcs\cl0\pcs_cl6.exe
d:\forte\install\bin\QQKN.dll
d:\forte\install\bin\QQDB.dll
d:\forte\install\bin\QQSM.dll
d:\forte\install\bin\QQDO.dll
d:\forte\install\bin\QQCM.dll
d:\forte\install\bin\QQFO.dll
d:\forte\install\bin\qqtlnt.dll
d:\forte\install\bin\w3tpwss.dll
d:\forte\install\bin\QQDS.dll
C:\WINNT\System32\mspdb50.dll
C:\WINNT\System32\comctl32.ocx
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\system32\OLEAUT32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\LZ32.dll
C:\WINNT\system32\VERSION.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
QQSH qqnl_MsgCatalog::LocatePointers (016785d8,021f54e0,013029b8,00000328)
QQKN ::qqos_InitializeMM (016785d8,01726b28,00004df0,0911f980)
QQKN ::qqos_InitializeMM (016785d8,017266b8,0921fe98,017266b8)
QQKN ::qqos_tmgrProcessStacks (016785d8,007fb6a5,007fc514,016785d8)
QQKN ::qqos_InitializeMM (016785d8,00000001,021f6a28,00000080)
QQKN ::qqos_InitializeMM (016785d8,00000001,00000020,021f6a28)
QQKN ::qqos_InitializeMM (016785d8,00000018,01db97e8,008600d0)
QQKN qqLO_ForteScope_Allocate (016785d8,00000029,0911fabc,005e78b8)
QQSH qqsh_Task::MakeEventInstance (016785d8,016785d8,80000002,00000039)
pcs_cl6 00432013 (016785d8,00000007,00000080,021f6a28)
pcs_cl6 00431e99 (016785d8,01db9780,0911fb58,0072be72)
pcs_cl6 004339b0 (016785d8,006eced8,01db9780,00000024)
QQKN qqlo_ClassType::InstanceAlloc (016785d8,0911fb88,01db8d98,00000000)
QQDO qqdo_DomParamDeSerializeDriver::ProcessHdr
(016785d8,0911fc30,01d748cc,0911fc24)
QQDO qqdo_DomParamDeSerializeDriver::AddObject
(016785d8,01d748cc,0911fc30,00000000)
QQDO qqdo_DomParamDeSerializeObject::XlateObject
(016785d8,01d748cc,00000000,00000000)
QQKN ::qqlo_Xlate (016785d8,01d74838,020e99c8,0060d0d8)
QQKN ::qqlo_Xlate (016785d8,01d74838,020e99c8,0060d0d8)
pcs_cl6 0048d2eb (016785d8,020e99c8,01d74838,0911fd38)
pcs_cl6 004920d9 (016785d8,020e99c8,00e46100,021542a8)
QQDO qqdo_DomParamDeSerializeDriver::ProcessObjGraph
(016785d8,0911fdf0,00000000,00e46100)
QQDO qqdo_DomParamDeSerializeDriver::Run (016785d8,0911fdf0,02154260,0074bf38)
QQDO qqdo_DOMDeSerializeObject::XlateEncapsulatedObject
(016785d8,0911fdf0,00000000,0194e408)
QQDO qqdo_Message::Xlate (016785d8,02154260,00e46100,01f151f8)
QQCM qqcm_DeSerializeDriver::Step (016785d8,01c98290,0911fe60,77f04f85)
QQCM qqcm_ForteNetStream::DeserializeStream
(016785d8,00000000,00e46100,00e46100)
QQCM qqcm_HoseRecvServiceTask::Run (016785d8,00000000,00e46100,00e46100)
QQSH qqsh_TaskManager::RunThread (016785d8,019844f0,00000000,016785d8)
QQKN ::qqos_threadIdle (017266b8,0137c1d8,f7598df0,0911ffb8)
QQKN ::qqos_threadStart (017266b8,00000000,00000000,00e46100)
MSVCRT 7800bee4 (00e46100,00000000,00000000,00e46100)
KERNEL32 77f04f2c (00000000,00000000,00000000,00000000)
QQSH 00000000 (00000000,00000000,00000000,00000000)
End of Stack Backtrace =========================================================
Does anybody have experience with problems like this?
Thank you very much for your help in advance.
Mark J Edwards
Senior Technical Specialist
Willis
The information in this email and in any attachments is confidential and may be
privileged. If you are not the intended recipient, please destroy this message,
delete any copies held on your systems and notify the sender immediately. You
should not retain, copy or use this email for any purpose, nor disclose all or
any part of its content to any other person.

To Keith :
Yep, they're a common occurrence at different stages of
Forte application development. To start the ball rolling,
what hardware platform and versions of Forte are you using
for Client and Server ?
Stab in the dark questions :
Are you invoking the client or server with -fm memory flags ?
eg. Ftexec -fm(n:8000,x:32000) -fi MyApp.idx
Are you using interpreted partitions(standard) or compiled
partitions ?
Does your application contain external C library routines ?
Justin
Justin Levis
Hydro Electric Corporation
Hobart Tas

Full thread dump/segmentation violation encountered in NAS4.0

hi,
the application is running on NAS4.0 and BillerXpert4. while accessing the database via a billerXpert api, we encounter a segmentation violation ==> full thread dump. this happens sporadically. below is an extract from the NAS log showing the error:-
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x20302000]
stackbase=DC841D64, stackpointer=DC83F42C
Full thread dump:
"Thread-3357" (TID:0xe17215c8, sys_thread_t:0x12040a0, state:R, thread_t: t@
3767, sp:0xdc580db8 threadID:0xdc581dd0, stack_base:0xdc581d64, stack_size:0x200
00) prio=5
java.net.SocketInputStream.read(Compiled Code)
java.io.BufferedInputStream.fill(Compiled Code)
java.io.BufferedInputStream.read(Compiled Code)
netscape.ldap.ber.stream.BERElement.getElement(Compiled Code)
netscape.ldap.LDAPConnThread.run(Compiled Code)
any pointers/advice as to what cld have caused this to happen?
many thanks in advance!!

Ah well if you're back on 1.2 then that's about as much error information as you will get.
JDK 1.2 is way past end-of-life. There is nothing you can do here to fix this problem.
Note: just because your application code was written for 1.2 doesn't mean it won't run on a later version of the VM. Try 1.3.1 if you don't want to jump up to 1.5 or 1.6 (but 1.3.1 will soon hit end-of-life too).
Sorry.

SIGSEGV   11* segmentation violation

I'm on a Sco Unixware 7.1.3 platform using
WLS 7SP1 with SCO JDK1.3.1_06.
This configuration is running at most of our stores, and has
been running at this one store for 2 months with no problem until 4 days ago.
When starting WLS, it keeps aborting and core dumping and restarting the WLS
server after each core dump. Just finally got in my stdout log file (see below
peice of log), but now crashes the unixware box.
Has anyone else seen this problem or know what causes it?
Thanks in advance.
Starting WebLogic Server...
<Jul 16, 2003 4:58:17 PM EDT> <Notice> <Management> <140005> <Loading configuration
/appserver/user_domains/wls700/storedomain/./config.xml>
<Jul 16, 2003 4:59:37 PM EDT> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<Jul 16, 2003 4:59:51 PM EDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
Admin Server "MainServer" for domain "storedomain">
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0xA3DF2478]
     stackpointer=80454b4
Full thread dump Classic VM (SCO-UNIX-J2SE-1.3.1_06:*FCS*:20021212, native threads):
"CoreHealthMonitor" (TID:0xb4fa0638, sys_thread_t:0x9783670, state:CW, native
ID:0x3d) prio=5
     at java.lang.Thread.sleep(Native Method)
     at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java,
Compiled Code)
"ExecuteThread: '14' for queue: 'JmsDispatcher'" (TID:0xb4f06258, sys_thread_t:0x951faf8,
state:CW, native ID:0x3c) prio=5
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java, Compiled Code)

hi,
i have a similar problem on my linux-server: i am runninig a java-program that parses a large xml-file (>20MB) and updates a database in background with the data of this xml-file. the programm starts without any problems, but after processing about the half file and allocating a lot of memory (about 400 to 500 MB) there occures the following error:
SIGSEGV 11 (*) segmentation violation
si_signo [11]: SIGSEGV: (*) segmentation violation
si_errno [0]: Success
si_code [1]: SEGV_MAPERR [addr: 0x1]
stackpointer=0xbffc7af8
Full thread dump Classic VM (J2RE 1.2.2 IBM build cx122-20010504, native threads):
"Finalizer" (TID:0x402ca728, sys_thread_t:0x80f4540, state:S, native ID:0xc04) prio=8
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java(Compiled Code))
at java.lang.ref.Finalizer.access$1(Finalizer.java(Compiled Code))
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java(Compiled Code))
"Reference Handler" (TID:0x402ca768, sys_thread_t:0x80ea7f8, state:S, native ID:0x803) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:426)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java(Compiled Code))
"Signal dispatcher" (TID:0x402ca7a8, sys_thread_t:0x80ea638, state:S, native ID:0x402) prio=5
the strange thing is that the program seemed to work correctly with smaller xml-files in former times. now the xml-files have permanetly grown and it seems to me that the programm has not enough handles or something to process the whole file.
could it be a database-problem? i am using a db2 and before this problem appeared, i reduced the amount of the following database-parameters: DBHEAP, APP_CTL_HEAP_SZ, STMTHEAP, APPLHEAPSZ, MAXFILOP in order to reduce the "memory-waste". i also have tried to call the garbage collector more often so that memory is freed.
can anybody help me please??
rde

RE: OLE and Access Segmentation Violations

Hi all,
I did not work with OLE automation for external components, but while developing the external components, C++, in one of our projects I've experienced the same error "Access Segmentation Violations". I've found out that this is because of memory access beyond the component's allocated space AND/OR freeing up the unallocated memory space for the components.
Hope this clue may help u.
Regards
Sivaram S Ghorakavi mailto:[email protected]
International Business Corporation http://www.ibcweb.com/
From: [email protected]
Sent: Tuesday, November 25, 1997 6:25 PM
To: [email protected]
Subject: OLE and Access Segmentation Violations
Has anybody used Forte to communicate with external components using OLE
Automation? We are creating segmentation violations through some of our
use of this interface, and need to know if there are some 'golden rules'
that can guide developers as they use the feature.
Thank you!

Hi!
I am not sure that I can give you any "golden rules" for interfacing
with OLE, but I can give you some thoughts on where to look for problems
that can result in Segmentation Violations.
I have often seen segmentation violations arise as a result of a NIL
object. You might want to try turning on the trc:lo:25 trace flag to
see if there is a NIL object exception being raise right before the seg
v. You have to be careful with the trc:lo:25 flag, though, since it
will show you every exception, no matter what, that is raised within
Forte (even if it's been handled internally). This is of greater
significance to OLE projects, since Forte tries several different ways
of starting an OLE server and uses internally handled exceptions to
notify itself if a certain method failed.
Another thing to try is just-in-time debugging. You will need Microsoft
Visual C++ installed on the machine where the OLE code is running, and
you will need to set the FORTE_NOHANDLER environment variable to TRUE.
In the MSVC development environment, go to the Tools --> Options
properties sheet, and choose the Debug tab. On that tab, make sure that
Just-In-Time Debugging is selected. Then, run the application. When
you encounter the seg v, you should get a dialog box asking if you want
to debug the application. Choosing yes (actually, I think that pressing
Cancel does this - the dialog box tells you) will bring you into the
MSVC development environment, where you can try some intense debugging.
I hope this helps!
-Katie
[email protected] wrote:
>
Has anybody used Forte to communicate with external components using
OLE
Automation? We are creating segmentation violations through some of
our
use of this interface, and need to know if there are some 'golden
rules'
that can guide developers as they use the feature.
Thank you!--
Katie Carty
Forte Consulting
4801 Woodway Drive
Suite 300E
Houston, Texas 77056
vmail: 510-986-3802
email: [email protected]
-----------------------------------------------

OLE and Access Segmentation Violations

Has anybody used Forte to communicate with external components using OLE
Automation? We are creating segmentation violations through some of our
use of this interface, and need to know if there are some 'golden rules'
that can guide developers as they use the feature.
Thank you!

Hi!
I am not sure that I can give you any "golden rules" for interfacing
with OLE, but I can give you some thoughts on where to look for problems
that can result in Segmentation Violations.
I have often seen segmentation violations arise as a result of a NIL
object. You might want to try turning on the trc:lo:25 trace flag to
see if there is a NIL object exception being raise right before the seg
v. You have to be careful with the trc:lo:25 flag, though, since it
will show you every exception, no matter what, that is raised within
Forte (even if it's been handled internally). This is of greater
significance to OLE projects, since Forte tries several different ways
of starting an OLE server and uses internally handled exceptions to
notify itself if a certain method failed.
Another thing to try is just-in-time debugging. You will need Microsoft
Visual C++ installed on the machine where the OLE code is running, and
you will need to set the FORTE_NOHANDLER environment variable to TRUE.
In the MSVC development environment, go to the Tools --> Options
properties sheet, and choose the Debug tab. On that tab, make sure that
Just-In-Time Debugging is selected. Then, run the application. When
you encounter the seg v, you should get a dialog box asking if you want
to debug the application. Choosing yes (actually, I think that pressing
Cancel does this - the dialog box tells you) will bring you into the
MSVC development environment, where you can try some intense debugging.
I hope this helps!
-Katie
[email protected] wrote:
>
Has anybody used Forte to communicate with external components using
OLE
Automation? We are creating segmentation violations through some of
our
use of this interface, and need to know if there are some 'golden
rules'
that can guide developers as they use the feature.
Thank you!--
Katie Carty
Forte Consulting
4801 Woodway Drive
Suite 300E
Houston, Texas 77056
vmail: 510-986-3802
email: [email protected]
-----------------------------------------------

Jdbc 8.1.5 and segmentation violation

I am using the Oracle 8i client libs on a Unix box to connect to a Oracle 7.3.4 database on NT using the JDBC oci driver.
The application server we are running manages a pool of db connections that is used by clients . When the app server starts, it connects to the Oracle database, reads some config tables, and is fine. To grab a connection from the pool the client calls a reserve method of the app server. This reserve method first tries to execute a simple query to check that the connection is good. However, it takes a "segmentation violation" trying to create a jdbc statement object, which is weird since the app server actually uses the same reserve method to call the database during initialization (and it works just fine).
It could be something flakey with the Oracle 8i JDBC or client
libraries, as we never saw this happen with the 8.0.5 client libs. The same app server code runs just fine.
Any ideas on what could be causing this?

I am also using JDK 1.3.1_02 but am using the classes12 library. Is there a classes13 library?
New at this...thanks

*** Break *** segmentation violation

Hi,
i have a problem with my software. I'm developing a little graphic interface for my thesis. I use JNI for native methods.
When i start my program the result is:
*** Break *** segmentation violation
Generating stack trace...
/usr/bin/addr2line: 'java': No such file
0x436c89a4 in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c6157 in <unknown function>
0x401798ec in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x40268378 in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x4017971f in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x4019b3d3 in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x40185e3a in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x4e38cd7c in Java_sun_font_FontManager_getFont2D + 0x38 from /sw/jdk/jdk1.5.0/jre/lib/i386/libfontmanager.so
0x436ce43b in <unknown function>
0x436c89a4 in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c8caa in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c89a4 in <unknown function>
0x436c8d81 in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c8a7b in <unknown function>
0x436c6157 in <unknown function>
0x401798ec in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x40268378 in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x4017971f in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x4019b122 in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x40190008 in <unknown> from /sw/jdk/jdk1.5.0/jre/lib/i386/client/libjvm.so
0x080497fe in <unknown> from java
0x007c3770 in __libc_start_main + 0xf0 from /lib/tls/libc.so.6
0x08049291 in strcpy + 0x35 from java
Aborted
What do i do?
What is the problem??
Thanks!!

The message "*** Break *** segmentation violation" is not characteristic of Java. It seems to be characteristic of ROOT. For those who do not not, see
http://root.cern.ch/root/
It may be that you have a "little graphic interface" but ROOT and the other software packages you are using (based on your other posts, Antares?) are big.
My best guess: you are calling from Java to you JNI library, you then call the ROOT-based software, it is setting up its own exception handlers. While still in ROOT, you get a SEGV and see the output of the ROOT exception handling.
There are nice, full tracebacks in some contexts, such as at this page:
http://root.cern.ch/root/roottalk/roottalk03/0244.html
Perhaps there is some initialization that ROOT normally does that is not happening because of the way your are calling it?

Getting segmentation violation while running holos macro

We are unable to build block in HOLOS 7.0 as we are getting the below error while trying to build HOLOS macros.
Error Logging request failed (status = %x0000004F)
Segmentation violation (code %xD3B70030)
Holos block builds until it reaches size 2146435072 bytes and it then stops piling up the logs with the above error message.
Please find below details regarding HOLOS version
Server Holos : V7.0B (built on 01-DEC-1998)
Please someone assist on what is causing the above issue and also how this can be resolved.

Unfortunately, I don't think there is anyone here that has seen Holos, never mind working with it. 12 years is a long time... Let's see if anyone in the community can help. But you may also want to search for other Holos forums or Holos users that may be able to help you out.
Ludek

Access/segmentation violation

I'm receiving 'Access/Segmentation Violation' errors
in an all-Forte application. Does anybody have experience
with problems like this?
Thank You,
Keith

To Keith :
Yep, they're a common occurrence at different stages of
Forte application development. To start the ball rolling,
what hardware platform and versions of Forte are you using
for Client and Server ?
Stab in the dark questions :
Are you invoking the client or server with -fm memory flags ?
eg. Ftexec -fm(n:8000,x:32000) -fi MyApp.idx
Are you using interpreted partitions(standard) or compiled
partitions ?
Does your application contain external C library routines ?
Justin
Justin Levis
Hydro Electric Corporation
Hobart Tas

Oracle 9i installation problem with RedHat 7.2 (segmentation violation)

I have try to installation 9i with RedHat 7.2 by x windows.
when i use xwin to run the "./runInstaller, i got the error
(segmentation) as below:
i have already try to follow the installation procedure in
http://staff.in2.hr/denis/oracle/901install_rh72_en.html#1 but
still got this error.
Can anyone help me??
Regards
Chris Sung
=================================================================
===============
oracle install
Connecting 192.168.1.3 via TELNET
Thursday, December 13, 2001 1:04:06
Red Hat Linux release 7.2 (Enigma)
Kernel 2.4.7-10 on an i686
login: oracle
Password:
Last login: Thu Dec 13 00:46:39 from apple
[oracle@orange oracle]$ (/home/oracle/Disk1/runInstaller -
display 192.168.1.2:0
-name "oracle install" &)
[oracle@orange oracle]$ Initializing Java Virtual Machine
from /tmp/OraInstall/jre/bin/jre. Please wait...
SIGSEGV 11* segmentation violation
     stackbase=0xbffff298, stackpointer=0xbffff160
Full thread dump:
"Finalizer thread" (TID:0x4276d210, sys_thread_t:0x4d0bfe0c,
state:R) prio=1
"Async Garbage Collector" (TID:0x4276d258,
sys_thread_t:0x4d09ee0c, state:R) prio=1
"Idle thread" (TID:0x4276d2a0, sys_thread_t:0x4d07de0c,
state:R) prio=0
"Clock" (TID:0x4276d088, sys_thread_t:0x4d05ce0c, state:CW)
prio=12
"main" (TID:0x4276d0b0, sys_thread_t:0x80d6fe8, state:R)
prio=5 *current thread*
     java.lang.System.initializeSystemClass(System.java)
Monitor Cache Dump:
Registered Monitor Dump:
Thread queue lock: <unowned>
Name and type hash table lock: <unowned>
String intern lock: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class loading lock: <unowned>
Java stack lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Has finalization queue lock: <unowned>
Finalize me queue lock: <unowned>
Dynamic loading lock: <unowned>
Monitor IO lock: <unowned>
Child death monitor: <unowned>
Event monitor: <unowned>
I/O monitor: <unowned>
Alarm monitor: <unowned>
     Waiting to be notified:
     "Clock" (0x4d05ce0c)
Monitor registry: owner "main" (0x80d6fe8, 1 entry)
Thread Alarm Q:

Strange, but yesterday I nter in Oracle9i install, open
gnome-terminal window as oracle user and simply type
/tmp/Disk1/runInstaler
the DISPLAY enviroment variable was set,
using RedHat 7.2 , kernel 2.4.16-0.9, glibc-2.2.4-19
Segmentation violation 11 may mean RAM problem, sometimes
incorrect program pointer.So I think it must work (runIstaler)

Segment violation in instant client library

Hi,
I have the following problem:
A Jboss/Java application accesses a database over JDBC. We use the OCI driver and Instant Client 10.2.0.1 connected to a two node Oracle RAC.
After several days continuous operation this application crashes with a segment violation, either in libclntsh.so.10.1 or in libocijdbc10.so.
In the mean time the RSS of the process has grown from about 1 GB to 2.5 to 2.7 GB but all Java heap space (and other allocations) are clearly within their set boundaries.
Does anybody now if there is a memory leak in the native code in instant client or elsewhere?
Operating system is Red Hat ES 3, Instant Client is version 10.2.0.1 and Java's version is 1.5.0_06.
regards
Börje Jonsson

Hi,
There is something log or trace erros files that was
generated ?
CheersI have trace files from two appservers, the first one here:
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0x650327ec, pid=2793, tid=1714793392
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C [libclntsh.so.10.1+0x4db7ec] nlolgserv+0x1a0
--------------- T H R E A D ---------------
Current thread (0x675321a8): JavaThread "http-0.0.0.0-8080-36" daemon [_thread_in_native, id=3243]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000000
Registers:
EAX=0x00000000, EBX=0x658e06c4, ECX=0xffffffff, EDX=0x4ca53ac0
ESP=0x66352668, EBP=0x663527a8, ESI=0xbee1e408, EDI=0x00000000
EIP=0x650327ec, CR2=0x00000000, EFLAGS=0x00210246
Top of Stack: (sp=0x66352668)
0x66352668: 6172736d 00000063 00000001 658e06c4
0x66352678: 6635274c 65590000 08400000 6635005a
0x66352688: 00000000 00000000 658e06c4 00000000
0x66352698: 6580a16c 09289560 00000000 0000005a
0x663526a8: bbec9fc0 bd687b54 66352f64 be0e5ca8
0x663526b8: 658e06c4 66352708 b75d7baa 00000081
0x663526c8: 69979527 66352b9c 658e06c4 69978ccd
0x663526d8: be047c96 bbeeedd1 00000001 650dec84
Instructions: (pc=0x650327ec)
0x650327dc: 4d d8 89 45 c4 8b 11 8b f8 b9 ff ff ff ff 33 c0
0x650327ec: f2 ae 83 c7 ff 8a 02 83 c2 01 88 07 83 c7 01 84
Stack: [0x6633a000,0x6635b000), sp=0x66352668, free space=97k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libclntsh.so.10.1+0x4db7ec] nlolgserv+0x1a0
C [libclntsh.so.10.1+0x4dbf2c] nlolgobj+0x552
C [libclntsh.so.10.1+0x3d3cf0] nnfun2a+0x17c
C [libclntsh.so.10.1+0x3d38e4] nnfsn2a+0x66
C [libclntsh.so.10.1+0x413b39] niqname+0x16f
C [libclntsh.so.10.1+0x340340] kwfnran+0x554
C [libclntsh.so.10.1+0x3090a4] kwfcinit+0xfe
C [libclntsh.so.10.1+0x16d0ee] kpuatch+0x7e0
C [libclntsh.so.10.1+0x286d09] OCIServerAttach+0x81
C [libocijdbc10.so+0x5a30]
C [libocijdbc10.so+0x7270] Java_oracle_jdbc_driver_T2CConnection_t2cLogon+0x17c
C [libocijdbc10.so+0x70c1] Java_oracle_jdbc_driver_T2CConnection_t2cCreateState+0x13f
j oracle.jdbc.driver.T2CConnection.t2cCreateState([BI[BI[BI[BISI[S[B[B)I+0
... a lot more rows ...
And the second one:
# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0x683a5e57, pid=23266, tid=1699470256
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C [libocijdbc10.so+0x11e57]
--------------- T H R E A D ---------------
Current thread (0x5c2eddf0): JavaThread "http-0.0.0.0-8080-68" daemon [_thread_in_native, id=7837]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000000
Registers:
EAX=0x00000000, EBX=0x683ae67c, ECX=0x0000000c, EDX=0x0000000c
ESP=0x654bb158, EBP=0x654bb200, ESI=0x683ad210, EDI=0x0000166c
EIP=0x683a5e57, CR2=0x00000000, EFLAGS=0x00210206
Top of Stack: (sp=0x654bb158)
0x654bb158: 00000000 683ae67c 683a5d47 00000000
0x654bb168: 00000000 0000000c 683a3060 00000000
0x654bb178: 00000000 0000000c 654bb190 5e739f5c
0x654bb188: 5e739f60 5e739f60 b704f488 5e739f5c
0x654bb198: 683ae67c 247fd514 0000000a 0076f4c4
0x654bb1a8: 0098b380 00000003 5655d348 00000014
0x654bb1b8: 00000028 b6d24772 0000166c 0000000c
0x654bb1c8: 654bb258 b6d1d088 0000000a ffffffff
Instructions: (pc=0x683a5e57)
0x683a5e47: dc 89 42 e0 89 42 e4 89 42 e8 89 42 ec 89 42 f0
0x683a5e57: 89 42 f4 89 42 f8 89 42 fc 8b 44 24 0c 5e 5b c3
Stack: [0x6549d000,0x654be000), sp=0x654bb158, free space=120k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libocijdbc10.so+0x11e57]
C [libocijdbc10.so+0xe29a] Java_oracle_jdbc_driver_T2CStatement_t2cDefineFetch+0x90
j oracle.jdbc.driver.T2CStatement.t2cDefineFetch(JI[S[BII[Loracle/jdbc/driver/Accessor;[BI[CI[SI[J)I+0
... a lot more rows ...

KJS crashes with Segmentation violation

We use IAS 6.0 SP2 under Solaris 2.8.
The KJS server crashes intermittently with Segmentation fault while running JavaMail APIs.
The error stack from the log is given below.
Will appreciate any help on this.
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0xc0000000]
stackpointer=D387D178
"SeedGenerator Thread" (TID:0x129c5d0, sys_thread_t:0x129c508, state:CW, thread_t: t@62, thre
adID:0xd2980000, stack_bottom:0xd2980000, stack_size:0x200000) prio=1
[1] java.lang.Object.wait(Object.java:424)
[2] sun.security.provider.SeedGenerator.run(SeedGenerator.java:107)
[3] java.lang.Thread.run(Thread.java:478)
"Thread-44" (TID:0xed2a10, sys_thread_t:0xed2948, state:CW, thread_t: t@61, threadID:0xd31000
00, stack_bottom:0xd3100000, stack_size:0x200000) prio=6
[1] java.lang.Thread.sleep(Native Method)
[2] com.kivasoft.applogic.AppLogicCleaner.run(Unknown Source)
"Thread-43" (TID:0xe9cf80, sys_thread_t:0xe9ceb8, state:R, thread_t: t@49, threadID:0xd338000
0, stack_bottom:0xd3380000, stack_size:0x200000) prio=5
[1] com.kivasoft.thread.ThreadBasic.run(Native Method)
[2] java.lang.Thread.run(Thread.java:478)
"Thread-42" (TID:0xe9bda8, sys_thread_t:0xe9bce0, state:CW, thread_t: t@48, threadID:0xd36000
00, stack_bottom:0xd3600000, stack_size:0x200000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] com.kivasoft.thread.ThreadBasic.realSuspend(Unknown Source)
[3] com.kivasoft.thread.ThreadBasic.suspend(Unknown Source)
[4] com.kivasoft.thread.ThreadBasic.run(Native Method)
[5] java.lang.Thread.run(Thread.java:478)
"Thread-42" (TID:0xe9bda8, sys_thread_t:0xe9bce0, state:CW, thread_t: t@48, threadID:0xd36000
00, stack_bottom:0xd3600000, stack_size:0x200000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] com.kivasoft.thread.ThreadBasic.realSuspend(Unknown Source)
[3] com.kivasoft.thread.ThreadBasic.suspend(Unknown Source)
[4] com.kivasoft.thread.ThreadBasic.run(Native Method)
[5] java.lang.Thread.run(Thread.java:478)
"Thread-41" (TID:0xe560c8, sys_thread_t:0xe56000, state:R, thread_t: t@47, threadID:0xd388000
0, stack_bottom:0xd3880000, stack_size:0x200000) prio=5 current thread
[1] java.net.PlainSocketImpl.initProto(Native Method)
[2] java.net.PlainSocketImpl.<clinit>(PlainSocketImpl.java:61)
[3] java.net.Socket.<init>(Socket.java:56)
[4] java.net.Socket.<init>(Socket.java:246)
[5] java.net.Socket.<init>(Socket.java:98)
[6] com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:61)
[7] com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:478)
[8] com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:91)
[9] javax.mail.Service.connect(Service.java:221)
[10] javax.mail.Service.connect(Service.java:127)
[11] javax.mail.Service.connect(Service.java:83)
[12] javax.mail.Transport.send0(Transport.java:95)
[13] javax.mail.Transport.send(Transport.java:73)
[14] sunir.share.util.mail.SimpleEmailSend.sendEmail(SimpleEmailSend.java:126)
[15] infomgr.util.IMMail.send(IMMail.java:187)
[16] infomgr.util.IMMail.sendEmail(IMMail.java:163)

Increase the min/max heap size and stack size for JAVA_ARGS in iasenv.ksh
eg:
JAVA_ARGS="-Xss2048k -Xms128m -Xmx256m"
-Sharmin.

What is Segmentation Violation?

Similar Messages

Maybe you are looking for