Segmentation Violation Error Handling

Has anyone determined if it is possible to catch a Segmentation Violation
and handle it? We have so far been unsuccessful. Looking for
GenericException has not worked. We believe we cannot catch this error, but
perhaps someone else can prove me wrong?
Thank you,
Jason Carpenter
CSC Consulting & Systems Integration
[email protected]
3811 Turtle Creek Blvd.
20th Floor
Dallas, TX 75219
214.520.0555
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Similar Messages

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

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

Segmentation violation error

hi,
We often get the following error on Solaris:
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x160]
stackpointer=D8690650
"HighPriority TimeEventGenerator" (TID:0x5d4bad8, sys_thread_t:0x5d4ba10,
state:CW, thread_t: t@145, threadID:0xd7671dd8, stack_bottom:0xd7672000,
stack_size:0x20000) prio=9
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:276)
[2]
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:131)
[3] java.lang.Thread.run(Thread.java:479)
Our environment is WL5.1 + sp9 + WL JDriver + Oracle815 Client + Oracle815
Server + Solaris 2.6
Any suggestion would be greately appreciated!
Thanks!

Perhaps you are using a JDK that needs inlining turned off -
See the platform support page -
http://www.weblogic.com/docs51/platforms/index.html
This might fix your other problem as well.
Mike
"Louis" <[email protected]> wrote:
hi,
We often get the following error on Solaris:
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x160]
stackpointer=D8690650
"HighPriority TimeEventGenerator" (TID:0x5d4bad8, sys_thread_t:0x5d4ba10,
state:CW, thread_t: t@145, threadID:0xd7671dd8, stack_bottom:0xd7672000,
stack_size:0x20000) prio=9
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:276)
[2]
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:131)
[3] java.lang.Thread.run(Thread.java:479)
Our environment is WL5.1 + sp9 + WL JDriver + Oracle815 Client + Oracle815
Server + Solaris 2.6
Any suggestion would be greately appreciated!
Thanks!

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

3400 Segmentation violation dis4adm.exe Error

Hi All,
One of the customers tries to run adupdeul.sh which ends in the following error.
Calling discoverer import utility for US language ...
dis4adm.exe /connect "sysadmin/sysadminentdv@ENTDV" /EUL "EUL_US" /apps_user /apps_responsibility "System Administrator" /apps_gwyuid "APPLSYSPUB/PUB" /apps_fndnam "APPS" /apps_security_group "Standard" /refresh /identifier /CMDFILE D:/Jagadishk/BUG/99927/ENTDV/discover/discover/cmdfile3680.lst /log D:/Jagadishk/BUG/99927/ENTDV/discover/discover/logfile3680.log
[1] + Done(139) ?
3400 Segmentation violation dis4adm.exe
Done calling discoverer import utility for US language.
Discoverer import exited with status 139.
Log information from the import process dis4adm.exe ...
++++++++++++++++++++++++++++++++
Import for US language
++++++++++++++++++++++++++++++++
8/14/2006 4:41:12 PM
dis4adm.exe /connect sysadmin/sysadminentdv@ENTDV /EUL EUL_US /apps_user /apps_responsibility System Administrator /apps_gwyuid APPLSYSPUB/PUB /apps_fndnam APPS /apps_security_group Standard /refresh /identifier /CMDFILE D:/Jagadishk/BUG/99927/ENTDV/discover/discover/cmdfile3680.lst /log D:/Jagadishk/BUG/99927/ENTDV/discover/discover/logfile3680.log
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamsbsnsslnflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscctblltflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscctshptflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscctstblflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscctstshflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscmpgnscflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscmpgnsflo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscntct01flo.eex:The import process did not import or modify any data
\Jagadishk\BUG\99927\ENTDV\discover\discover\US\amsamscntct02flo.eex:The import process did not import or modify any data
I have searched for the "3400 Segmentation violation" in the knowledge base but couldn't find any references.
Customer was on Discoverer 4.1.48.06 and upgraded to 4.1.48.08.
Following are the patches that customer applied recently.
Patch 3451630 DISCOVERER PATCH VERSION 4.1.48.08.00 ADMIN DESKTOP ONEOFF PATCH.
Patch 3622870 APPS: FIX FOR SECURE CONNECTION BUG 3559523 ON ADMIN/DESKTOP.
May I request for your inputs please.
Regards,
Ramana.

Hi Russ,
Thanks for response.
1. Yes
2.Using MKS Toolkit
3. Yes
4. Following is the command.
sh adupdeul.sh connect=sysadmin/<password>@<SID> resp=”System Administrator”gwyuid=APPLSYSPUB/PUB fndnam=APPS secgroup=”Standard”
topdir=/Jagadishk/BUG/99927/ENTDV/discover/discover language=US eulprefix=EUL eultype=OLTP mode=complete exedir=/oracle/DISCVR4 logfile=import1.log
5. We do have the .eex files in the directory.

SIGSEGV 11 segmentation violation - sp3 upgrade

I get the following error while upgrading WL 6.1 from SP2 to SP3....
I noticed someone else on this newsgroup got the same error while upgrading
to SP2.
Any clues on where/ why this occurs?
thanks
_nik
============================
bash-2.03$ java -cp wls61sp3_upgrade_generic.zip install -i console
Preparing CONSOLE Mode Installation...
============================================================================
===
Choose Locale...
->1- English
CHOOSE LOCALE BY NUMBER: 1
============================================================================
===
WebLogic Server 6.1 Service Pack 3 (created with InstallAnywhere by Zero
G)
============================================================================
===
Introduction
This installer will guide you through the installation of Service Pack 3 of
WebLogic Server 6.1. Use command "next" to proceed to the next screen. If
you
want to change something in a previous screen, use command "previous" or
"back". You may quit the installer at any time by using the command the
"quit".
PRESS <ENTER> TO CONTINUE:
============================================================================
===
Choose BEA Home Directory
1- /opt/pwl61
Existing BEA Home: 1
============================================================================
===
Installing...
[==================|==================|==================|==================
[SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x7a28bd0]
stackpointer=FFBEDC78
Exiting Thread (sys_thread_t:0xff30c2e8) : no stack
"Thread-2" (TID:0x2b55e8, sys_thread_t:0x2b5520, state:CW, thread_t: t@8,
threadID:0xf99c1d70, stack_bottom:0xf99c1d70, stack_size:0x1fd70) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] ZeroGl.run([DashoPro-V1.2-120198])
[4] java.lang.Thread.run(Thread.java:479)
"Finalizer" (TID:0x155610, sys_thread_t:0x155548, state:CW, thread_t: t@6,
threadID:0xfec81d70, stack_bottom:0xfec81d70, stack_size:0x1fd70) prio=8
[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
[3]
java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
24)
"Reference Handler" (TID:0x1512a0, sys_thread_t:0x1511d8, state:CW,
thread_t: t@5, threadID:0xfecc1d70, stack_bottom:0xfecc1d70,
stack_size:0x1fd70) prio=10
[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
"Signal dispatcher" (TID:0x12c1b8, sys_thread_t:0x12c0f0, state:MW,
thread_t: t@4, threadID:0xfed01d70, stack_bottom:0xfed01d70,
stack_size:0x1fd70) prio=10
"main" (TID:0x38650, sys_thread_t:0x38588, state:R, thread_t: t@1,
threadID:0x25118, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
current thread
[1] ZeroGb.m([DashoPro-V1.2-120198])
[2]
com.zerog.ia.installer.actions.InstallUninstaller.a([DashoPro-V1.2-120198])
[3]
com.zerog.ia.installer.actions.InstallUninstaller.b([DashoPro-V1.2-120198])
[4]
com.zerog.ia.installer.actions.InstallUninstaller.installSelf([DashoPro-V1.2
-120198])
[5] com.zerog.ia.installer.Action.install([DashoPro-V1.2-120198])
[6] com.zerog.ia.installer.Action.install([DashoPro-V1.2-120198])
[7] com.zerog.ia.installer.GhostDirectory.install([DashoPro-V1.2-120198])
[8] com.zerog.ia.installer.Installer.install([DashoPro-V1.2-120198])
[9] com.zerog.ia.installer.Main.a([DashoPro-V1.2-120198])
[10] com.zerog.ia.installer.Main.main([DashoPro-V1.2-120198])
[11] install.main([DashoPro-V1.2-120198])
Abort

Nik:
There is a good chance that you do not have your .../jdk131/bin in your PATH.
If that doesn't do it, please file a case and I'll look for it!
Wayne Scott
"Nik" <[email protected]> wrote in message news:<[email protected]>...
I get the following error while upgrading WL 6.1 from SP2 to SP3....
I noticed someone else on this newsgroup got the same error while upgrading
to SP2.
Any clues on where/ why this occurs?
thanks
_nik
============================
bash-2.03$ java -cp wls61sp3_upgrade_generic.zip install -i console
Preparing CONSOLE Mode Installation...
============================================================================
===
Choose Locale...
->1- English
CHOOSE LOCALE BY NUMBER: 1
============================================================================
===
WebLogic Server 6.1 Service Pack 3 (created with InstallAnywhere by Zero
G)
============================================================================
===
Introduction
This installer will guide you through the installation of Service Pack 3 of
WebLogic Server 6.1. Use command "next" to proceed to the next screen. If
you
want to change something in a previous screen, use command "previous" or
"back". You may quit the installer at any time by using the command the
"quit".
PRESS <ENTER> TO CONTINUE:
============================================================================
===
Choose BEA Home Directory
1- /opt/pwl61
Existing BEA Home: 1
============================================================================
===
Installing...
[==================|==================|==================|==================
[SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x7a28bd0]
stackpointer=FFBEDC78
Exiting Thread (sys_thread_t:0xff30c2e8) : no stack
"Thread-2" (TID:0x2b55e8, sys_thread_t:0x2b5520, state:CW, thread_t: t@8,
threadID:0xf99c1d70, stack_bottom:0xf99c1d70, stack_size:0x1fd70) prio=5
[1] java.lang.Object.wait(Native Method)
[2] java.lang.Object.wait(Object.java:424)
[3] ZeroGl.run([DashoPro-V1.2-120198])
[4] java.lang.Thread.run(Thread.java:479)
"Finalizer" (TID:0x155610, sys_thread_t:0x155548, state:CW, thread_t: t@6,
threadID:0xfec81d70, stack_bottom:0xfec81d70, stack_size:0x1fd70) prio=8
[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
[3]
java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
24)
"Reference Handler" (TID:0x1512a0, sys_thread_t:0x1511d8, state:CW,
thread_t: t@5, threadID:0xfecc1d70, stack_bottom:0xfecc1d70,
stack_size:0x1fd70) prio=10
[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
"Signal dispatcher" (TID:0x12c1b8, sys_thread_t:0x12c0f0, state:MW,
thread_t: t@4, threadID:0xfed01d70, stack_bottom:0xfed01d70,
stack_size:0x1fd70) prio=10
"main" (TID:0x38650, sys_thread_t:0x38588, state:R, thread_t: t@1,
threadID:0x25118, stack_bottom:0xffbf0000, stack_size:0x20000) prio=5
current thread
[1] ZeroGb.m([DashoPro-V1.2-120198])
[2]
com.zerog.ia.installer.actions.InstallUninstaller.a([DashoPro-V1.2-120198])
[3]
com.zerog.ia.installer.actions.InstallUninstaller.b([DashoPro-V1.2-120198])
[4]
com.zerog.ia.installer.actions.InstallUninstaller.installSelf([DashoPro-V1.2
-120198])
[5] com.zerog.ia.installer.Action.install([DashoPro-V1.2-120198])
[6] com.zerog.ia.installer.Action.install([DashoPro-V1.2-120198])
[7] com.zerog.ia.installer.GhostDirectory.install([DashoPro-V1.2-120198])
[8] com.zerog.ia.installer.Installer.install([DashoPro-V1.2-120198])
[9] com.zerog.ia.installer.Main.a([DashoPro-V1.2-120198])
[10] com.zerog.ia.installer.Main.main([DashoPro-V1.2-120198])
[11] install.main([DashoPro-V1.2-120198])
Abort

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

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)

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 ?

Error Handling in JDBC Adaptor - Without BPM

Hi friends,
My problem is like this. Scenario is File -> Xi -> JDBC.
here i didn't used BPM at all.
My interface is working fine.
right now i am not doing any error handling for 'Primary key violation, refrential intigrity etc.. '.
if this type errors encountered i going to adapter monitoring and looking out the issue.
Now the client requirment is
whenever this type of errors occured Client should be notified Via email along with error description.
Is there anyway to do this ?

Hi Suresh,
You can setup the Alerting framework of XI to trigger alerts. Alert rules can be set to raise alerts in case of JDBC Adapter Errors.
Check these links....
http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Thanks & Regards,
Renjith
An addition to what i just said...You have to be on SP14 for this...
Message was edited by: Renjith Andrews

Error Handling with JPA

I'm working on a JPA/TopLink Essentials/ADF faces application. It's going well except that I don't have a clue how to get on top of the error handling. JPA doesn't seem to have any. I would assume that there must be a Toplink extension[b] to find out what errors/codes etc are being produced. ADF faces does a ok job of showing them on screen but the handling should be more user friendly for errors like invalid foreign key, unique key violation etc.
Since there is no return and no exceptions declared on JPA functions like persist(), I assume that there must be some sort of listener that I can register to handle the errors myself. If ADF Faces can get the errors then so can I, but how??
Any help would be appreciated
Mark

The "errors" raised by the persistence provider for the types of "errors" you mentioned are all runtime exceptions of the PersistenceException variety. See the javadoc for this class and also look at its subclasses: http://java.sun.com/javaee/5/docs/api/javax/persistence/PersistenceException.html
Since PersistenceException is an unchecked runtime exception, its up to you to catch it at whatever point you decide to handle these types of problems in your application (i.e. in the service layer which would communicate the problem to your view layer to display something user friendly). Make sense?

Problems in Query, error handling and sqlj

I need some clarifications:
1. Can I use where clause in Insert query: for e.g: Insert into table_name (.., ...) values (.., ..) where id not in (Select Id from table_2 where name = '');
2. Can I handle error in my query in sqlj file. For e.g unique constraint violated error, I want to handle it like try-catch block in Java. So that if there would be any such error it will ignore.
3. I want to do this both in the sqlj file. Is it possible?
If anyone can answer it would be a great help for me.

more appropriate forums :
PL/SQL
JDeveloper and ADF
SQL-Syntax and much more :
http://tahiti.oracle.com/
http://download.oracle.com/docs/cd/E11882_01/server.112/e10592/toc.htm
http://download.oracle.com/docs/cd/E11882_01/server.112/e10592/statements_9014.htm#i2163698
http://download.oracle.com/docs/cd/E11882_01/server.112/e10592/statements_9014.htm#i2079995
http://download.oracle.com/docs/cd/E11882_01/server.112/e10592/statements_9014.htm#i2145081

How to ignore a DML operation using error handler.

In our streams replication application (using Oracle 10G), we have error handler to handle the errors at destination apply process. It uses straight apply process no DML handlers except error handlers. The error handler should just log the error and LCR info into the error log table and discard the DML LCR. Error logging is not a problem. But the problem is how to ignore the error DML LCR and move to next LCR in the same transaction without rollback of the transaction or any error.
Another question, do I need to use LCR.EXECUTE() procedure to continue the transaction in case of errors?
Appreciated your help.

Thanks for reference, confirmation of use of execute function.
I read those pages and other related pages in "Oracle® Streams Concepts and Administration" too.
I am able to write an error handler to handle errors with regular apply process. It is logging "no data found" errors but failing in case of foreign key violations. Error handler takes any kind of error and logs a record into errorlog table and ignores the error. I think it is not calling error handler. I checked for handlers in dba_apply_dml_handlers table. There is a handler for Inert, update and delete. I am investigating it further now. If you have any leads, please post.
Thanks for your time and help.
Dharma

Segmentation Violation Error Handling

Similar Messages

Maybe you are looking for