Segmentation Violation Exceptions

All,
We have been encountering some strange behaviour with some of our
applications running on Win NT 4.0 under Forte 3.0.E.0.
The application will stop at a particular point with a Segmentation Fault
detected, and will then shut down Forte. Re-starting Forte, and
re-starting the machine didn't help. Even re-compiling the code doesn't
help. The only way around the problem that we have found is to RENAME the
variable in use at the line of code that causes the crash, then Recompile
and run the code again. Then we simply rename the variable back to what it
was. This happens intermittently, but does cause quite a problem with
losing work occasionally.
Has anyone else encountered this type of problem ?
Regards,
Greg Bastian.

This question really belongs in the Solaris Studio C/C++/Fortran Compilers forum:
https://community.oracle.com/community/server_%26_storage_systems/systems-development-and-management-tools/application_d…
You don't show how you are building your program, and you don't say which version of Studio you are using, or the platform you are using. All of this data is important to understand your issue.
You are mixing binary code created by the Studio C++ compiler with code built with g++. That will work only under these conditions:
- You must use the -compat=g option with Studio C++ on every CC command, compiling and linking. (If you are using Studio 12.4, you can use -std=c++03 or -std=c++11 instead.)
- The g++ compiler must be compatible with the version expected by the Studio C++ compiler, which depends on the Studio version.
- Only shared libraries (.so files) created by g++ can be linked, not .o or .a files.
- The compiler (CC or g++) that builds the main program must be used to link the final program.
If you meet all these conditions and the code still fails, please show
- the Studio version (run the command "CC -V"),
- the g++ version (run "g++ -v"),
- the platform (operating system and version, and whether it is Sparc or x86), and
- show how you build the program.

Similar Messages

Segmentation violation while logging to jdbc type 4

hi,
I'm getting segmentation violation everytime when I try to log to jdbc type 4 after I've sent emails (via a thread). The code was working fine for type 2 jdbc. Following is my stack trace:
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x0]
stackpointer=E107EB98
"Thread-49" (TID:0x135b978, sys_thread_t:0x135b8b0, state:CW, thread_t: t@87, threadID:0xe73a4000, stack_bottom:0xe0e00000, stack_size:0x200000) prio=6
[1] java.lang.Thread.sleep(Native Method)
[2] com.kivasoft.applogic.AppLogicCleaner.run(Unknown Source)
"Thread-48" (TID:0x1328960, sys_thread_t:0x1328898, state:R, thread_t: t@86, threadID:0xe73a3e00, stack_bottom:0xe1080000, stack_size:0x200000) prio=5 current thread
[1] com.kivasoft.rlop.ObjectPoolManager.getObjectPoolnative(Native Method)
[2] com.kivasoft.rlop.ObjectPoolManager.getObjectPool(Unknown Source)
[3] com.netscape.server.jdbc.ConnectionPool.getPool(Unknown Source)
[4] com.netscape.server.jdbc.ConnectionPool.getFromPool(Unknown Source)
[5] com.netscape.server.jdbc.ConnectionPool.getConnection(Unknown Source)
[6] com.netscape.server.jdbc.DataSourceImpl.getConnection(Unknown Source)
[7] TestDatabase.getConnection(TestDatabase.java:89)
Is there any threading issue for logging to jdbc? I'm using Iplanet 6 SP2, running on UNIX system. Thanks in advance for any help.

You say you've managed to get the JDBC driver working
in an application but not in a JSP. You also say that
the error you get is
"com.microsoft.jdbc.sqlserver.SQLServerDriver".
I'd be willing to bet that the exception that you have
got is a ClassNotFoundException. I.E. your application
server hasn't found the JDBC driver classes. The
application server probably doesn't use your current
CLASSPATH to look for classes. It will be setup within
the application server in some way and you'll need to
check your app server documentation to see how it is
done.
Try replacing
e.printStackTrace();with
e.printStackTrace(out);to get a full stack trace of your error.
ColTried it. Got this error when I tried to run the JSP.
Incompatible type for method. Can't convert javax.servlet.jsp.JspWriter to java.io.PrintWriter.
e.printStackTrace(out);
I'm currently using Apache Tomcat 4.0.3 as my JSP/Servlet Container.
I'm also using Type 4 MS SQL Server 2000 JDBC driver version 2.0 on my NT4.0 Server.
Do I need to set my JDBC driver in my container? if so, how do I do that?

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

*** 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?

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 ?

Primary key violation exception in auto increment column

Hi All,
I am facing one issue in Multi threaded environment.
I am getting Primary key violation exception in auto increment column. I have a table and the primary key is the auto increment column, and I have a trigger which is populating this column.
5 threads are running and inserting the data in the table and throwing Primary key violation exception randomly.
create table example (
id number not null,
name varchar2(30)
alter table example
add constraint PK1example primary key (id);
create sequence example_id_seq start with 1 increment by 1;
create or replace trigger example_insert
before insert on example
for each row
begin
select example_id_seq.nextval into :new.id from dual;
end;
Any idea how to handle auto increment column(trigger) in Multi threaded environment??
Thanks,

user13566109 wrote:
Thanks All,
Problem was in approach; removed the trigger and placed a seq.nextval in insert query. It has resolved the issue.I very much suspect that that was not the issue.
The trigger would execute for each insertion and the nextval would have been unique for each insertion (that's how sequences work in oracle), so that wouldn't have been causing duplicates.
I suspect, more likely, that you had some other code somewhere that was using another sequence or some other method of generating the keys that was also inserting into the same table, so there was a conflict in the sources of the sequences being generated.
The way you showed you had coded above, was a perfectly normal way to assign primary keys from a sequence, and is not a problem in a multi user/threaded environment.

"Access Violation" exception while accessing PDEImage in outside of the class as a parameter

Hi,
In our project, we are retrieving PDEImage content from PDF Page by using below line of code in our Plugin project:
But we are getting "Access Violation" exception while accessing retrieved PDEImage in outside of the class as a parameter.
This issue is happening only in Windows 8.1 and Acrobat 11 combination.
If we remove the above highlighted lines from the method then no exception and working fine.
But we don't know why these lines are added, because we are not updating any of the PDF content here.
We are planning to remove these highlighted lines from the method.
We want to know whether the removing of these lines will impact the application.
Kindly help us to resolve the issue.

And will removing the lines impact the application? Certainly. If you do not call PDPageReleasePDEContent you will have a memory leak at best, or may prevent other activity from completing (such as saving or closing the file). The first two lines, however, are redundant since you do not seem to be actually changing the page.
You must call PDPageReleasePDEContent when you have finished with the content, in every case.

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.

Segmentation violation in BDB code in macro SH_TAILQ_REMOVE

Hello OTN Forum readers
I wrote an application using BDB-5.1.19 using replication manager distributed into 2 sites
Sometimes after network partition(no link) between the two nodes
nsites=2
priority=100
ack=quorum
I get a segmentation violation in the BDB code
[New process 3489]
#0 0x00002af382d07885 in __env_alloc_free (infop=0x1418fda0,
ptr=0x2aaaad55b920) at ../src/env/env_alloc.c:421
421 SH_TAILQ_REMOVE(&head->addrq, elp, addrq, __alloc_element);
(gdb) bt
#0 0x00002af382d07885 in __env_alloc_free (infop=0x1418fda0,
ptr=0x2aaaad55b920) at ../src/env/env_alloc.c:421
#1 0x00002af382c58b04 in __rep_grow_sites (env=0x1418f620, nsites=2)
at ../src/rep/rep_elect.c:1336
#2 0x00002af382c5854e in __rep_elect_init (env=0x1418f620, nsites=2,
nvotes=1, beginp=0x606d1ed4, otally=0x606d1ed0)
at ../src/rep/rep_elect.c:1152
#3 0x00002af382c56112 in __rep_elect_int (env=0x1418f620, given_nsites=2,
nvotes=1, flags=0) at ../src/rep/rep_elect.c:251
#4 0x00002af382c77581 in __repmgr_elect (env=0x1418f620, nsites=2, nvotes=1,
failtimep=0x606d2050) at ../src/repmgr/repmgr_elect.c:455
#5 0x00002af382c76d33 in __repmgr_elect_main (env=0x1418f620,
th=0x2aaab0008e20) at ../src/repmgr/repmgr_elect.c:168
#6 0x00002af382c76b9e in __repmgr_elect_thread (argsp=0x2aaab0008e20)
at ../src/repmgr/repmgr_elect.c:102
#7 0x0000003753a064a7 in start_thread () from /lib64/libpthread.so.0
#8 0x00000037532d3c2d in clone () from /lib64/libc.so.6
Current language: auto; currently c
(gdb) info locals
elp = (ALLOC_ELEMENT *) 0x2aaaad55b8f0
elp_tmp = (ALLOC_ELEMENT *) 0x2aaaad55b8b8
head = (ALLOC_LAYOUT *) 0x2aaaad55b080
env = (ENV *) 0x1418f620
q = (SIZEQ_HEAD *) 0x1418f620
len = 64
i = 0 '\0'
p = (u_int8_t *) 0x2aaaad55b920 <Address 0x2aaaad55b920 out of bounds>
(gdb) info registers
rax 0x80000000ffffff9e -9223372032559808610
rbx 0x2aaaad55b8b8 46912540883128
rcx 0xffffffffffffffc8 -56
rdx 0x80000000ffffffd6 -9223372032559808554
rsi 0x2aaaad55b8f0 46912540883184
rdi 0x80002aa9ad55b91a -9223325128608859878
rbp 0x606d1d80 0x606d1d80
rsp 0x606d1d10 0x606d1d10
r8 0x606d1ed0 1617764048
r9 0xffffffff 4294967295
r10 0x7469736e206e6f69 8388362697781964649
r11 0x202 514
r12 0x0 0
r13 0x5f2d1000 1596788736
r14 0x0 0
r15 0x1000 4096
rip 0x2af382d07885 0x2af382d07885 <__env_alloc_free+407>
eflags 0x10a93 [ CF AF SF IF OF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x63 99
(gdb) x/20i $rip
*0x2af382d07885 <__env_alloc_free+407>: mov %rax,0x8(%rdi)*
0x2af382d07889 <__env_alloc_free+411>: mov -0x48(%rbp),%rdx
0x2af382d0788d <__env_alloc_free+415>: mov -0x48(%rbp),%rax
0x2af382d07891 <__env_alloc_free+419>: mov 0x8(%rax),%rax
0x2af382d07895 <__env_alloc_free+423>: lea (%rdx,%rax,1),%rcx
0x2af382d07899 <__env_alloc_free+427>: mov -0x48(%rbp),%rdx
0x2af382d0789d <__env_alloc_free+431>: mov -0x48(%rbp),%rax
0x2af382d078a1 <__env_alloc_free+435>: mov 0x8(%rax),%rax
0x2af382d078a5 <__env_alloc_free+439>: lea (%rdx,%rax,1),%rax
0x2af382d078a9 <__env_alloc_free+443>: mov (%rax),%rdx
0x2af382d078ac <__env_alloc_free+446>: mov -0x48(%rbp),%rax
0x2af382d078b0 <__env_alloc_free+450>: mov (%rax),%rax
0x2af382d078b3 <__env_alloc_free+453>: lea (%rdx,%rax,1),%rax
0x2af382d078b7 <__env_alloc_free+457>: mov %rax,(%rcx)
0x2af382d078ba <__env_alloc_free+460>:
jmp 0x2af382d078f8 <__env_alloc_free+522>
0x2af382d078bc <__env_alloc_free+462>: mov -0x48(%rbp),%rax
0x2af382d078c0 <__env_alloc_free+466>: mov 0x8(%rax),%rcx
0x2af382d078c4 <__env_alloc_free+470>: mov -0x48(%rbp),%rdx
0x2af382d078c8 <__env_alloc_free+474>: mov -0x38(%rbp),%rax
0x2af382d078cc <__env_alloc_free+478>: mov %rdx,%rbx
(gdb)
(gdb) p *env
$3 = {
dbenv = 0x1418eeb0,
mtx_env = 4,
db_home = 0x12b45890 "/usr/local/bdb/replica_data",
open_flags = 3987,
db_mode = 436,
pid_cache = 3489,
lockfhp = 0x0,
env_lref = 0x0,
recover_dtab = {
int_dispatch = 0x14187830,
int_size = 182,
ext_dispatch = 0x0,
ext_size = 0
dir_mode = 0,
data_len = 100,
thr_nbucket = 0,
thr_hashtab = 0x0,
mutex_iq = 0x0,
mutex_iq_next = 1,
mutex_iq_max = 50,
mtx_dblist = 31,
---Type <return> to continue, or q <return> to quit---
db_ref = 2,
dblist = {
tqh_first = 0x2aaab4164dd0,
tqh_last = 0x2aaab4182c80
fdlist = {
tqh_first = 0x14186970,
tqh_last = 0x2aaab41655a0
mtx_mt = 32,
mti = 0,
mt = 0x0,
crypto_handle = 0x0,
lk_handle = 0x14190570,
lg_handle = 0x14186b00,
mp_handle = 0x14186a00,
mutex_handle = 0x12abbf70,
rep_handle = 0x1418f740,
tx_handle = 0x1418fed0,
dbt_usercopy = 0,
log_verify_wrap = 0x2af382c91a3f <__log_verify_wrap>,
reginfo = 0x1418fda0,
test_abort = 0,
---Type <return> to continue, or q <return> to quit---
test_check = 0,
test_copy = 0,
flags = 1316
This is a multithread application and the thread stack relatives to BDB API where
(gdb) thread 13
[Switching to thread 13 (process 3599)]#0 0x00000037532cced2 in select ()
from /lib64/libc.so.6
(gdb) bt
#0 0x00000037532cced2 in select () from /lib64/libc.so.6
#1 0x00002af382d52aca in __os_sleep (env=0x1418f620, secs=1, usecs=0)
at ../src/os/os_yield.c:90
#2 0x00002af382d52a79 in __os_yield (env=0x1418f620, secs=1, usecs=0)
at ../src/os/os_yield.c:48
#3 0x00002af382c714ae in __env_rep_enter (env=0x1418f620, checklock=0)
at ../src/rep/rep_util.c:1022
#4 0x00002af382d24d9d in __log_archive_pp (dbenv=0x1418eeb0,
listp=0x610d2710, flags=8) at ../src/log/log_archive.c:60
#5 0x000000000120836c in clean_unused_log (env=0xfffffffffffffdfe)
at bdb_operations.cpp:664
#6 0x0000000001206fda in BDBCheckpointThread::Run (this=0x2aaab0008fc0,
arg=<value optimized out>) at bdb_environment_handle.cpp:48
#7 0x0000000000bf868d in osiThread::MyRun (Args=0x0)
at /vobs/fw/include/osiThread.h:60
#8 0x0000000000f72dee in threadMain (arg=<value optimized out>)
at osiThreadLauncherLinux.cpp:50
#9 0x0000003753a064a7 in start_thread () from /lib64/libpthread.so.0
#10 0x00000037532d3c2d in clone () from /lib64/libc.so.6
(gdb)
(gdb) thread 14
[Switching to thread 14 (process 3596)]#0 0x0000003753a0ab99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb) bt
#0 0x0000003753a0ab99 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib64/libpthread.so.0
#1 0x00002af382c7e143 in __repmgr_queue_get (env=0x1418f620, msgp=0x5fcd10b0,
th=0x2aaab0008cb0) at ../src/repmgr/repmgr_queue.c:90
#2 0x00002af382c79d9d in message_loop (env=0x1418f620, th=0x2aaab0008cb0)
at ../src/repmgr/repmgr_msg.c:49
#3 0x00002af382c79cd4 in __repmgr_msg_thread (argsp=0x2aaab0008cb0)
at ../src/repmgr/repmgr_msg.c:34
#4 0x0000003753a064a7 in start_thread () from /lib64/libpthread.so.0
#5 0x00000037532d3c2d in clone () from /lib64/libc.so.6
(gdb) thread 15
[Switching to thread 15 (process 3594)]#0 0x0000003753a0ab99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb) bt
#0 0x0000003753a0ab99 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib64/libpthread.so.0
#1 0x00002af382c7e143 in __repmgr_queue_get (env=0x1418f620, msgp=0x5f2d00b0,
th=0x2aaab0008b40) at ../src/repmgr/repmgr_queue.c:90
#2 0x00002af382c79d9d in message_loop (env=0x1418f620, th=0x2aaab0008b40)
at ../src/repmgr/repmgr_msg.c:49
#3 0x00002af382c79cd4 in __repmgr_msg_thread (argsp=0x2aaab0008b40)
at ../src/repmgr/repmgr_msg.c:34
#4 0x0000003753a064a7 in start_thread () from /lib64/libpthread.so.0
#5 0x00000037532d3c2d in clone () from /lib64/libc.so.6
The bug is not always appears , so if its difficults to wrote a little program to reproduce the case
But do you know something about this issue ??

Just to followup a little. The initial election completes and succeeds and one site becomes the master, correct? Then when you cause the partition, the site that is not the master holds its own election and then that gets the SEGV.
Unfortunately we really need to see the contents of the rep structure, because the segv is occurring when trying to free a pointer to space in that structure. That pointer should either be 0 or a valid address.
My suspicion is that the 2nd site that remains a client never participated in the initial election. Maybe your attempts at reproducing this end up having the 2nd site participate too. Perhaps you can increase your chance of reproducing it if you briefly delay bringing that 2nd site online so that the 1st site elects itself master. Then when you disconnect them, the 2nd site will hold its own election for the first time. If you do reproduce it, please save the executable and core file in case there are other things to investigate.
Sue LoVerso
Oracle

Segmentation violation

I'm getting the following errors when attempting to test Net Service Name:
SIGSEGV 11* segmentation violation
stackbase=0x419cb000, stackpointer=0x419cabf0
Full thread dump:
"CursorIdler" (TID:0x406feb00, sys_thread_t:0x41a4ee0c, state:CW) prio=5
oracle.ewt.timer.Timer.accurateSleep(Timer.java:343)
oracle.ewt.timer.Timer.run(Timer.java:302)
java.lang.Thread.run(Thread.java)
"AWT-Modal" (TID:0x407014b0, sys_thread_t:0x414ace0c, state:CW) prio=5
sun.awt.motif.ModalThread.run(MDialogPeer.java:148)
"AWT-Dispatch-Proxy" (TID:0x40701440, sys_thread_t:0x41960e0c, state:CW) prio=5
java.lang.Object.wait(Object.java)
java.awt.EventQueue.getNextEvent(EventQueue.java:141)
java.awt.EventDispatchThread.run(EventDispatchThread.java:73)
"Thread-5" (TID:0x40708440, sys_thread_t:0x419cae0c, state:R) prio=3 current thread
oracle.net.common.TestConnection.callTestConnect(TestConnection.java:55)
oracle.net.asst.servicewizard.TestConnDialog._doConnect(TestConnDialog.java:335)
oracle.net.asst.servicewizard.TestConnDialog$1.run(TestConnDialog.java:203)
"Image Fetcher 0" (TID:0x406fd7a8, sys_thread_t:0x419ebe0c, state:CW) prio=8
sun.awt.image.ImageFetcher.nextImage(ImageFetcher.java:109)
sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:146)
sun.awt.image.ImageFetcher.run(ImageFetcher.java:127)
"TaskScheduler timer" (TID:0x406f9940, sys_thread_t:0x41a2de0c, state:CW) prio=5
java.lang.Object.wait(Object.java)
oracle.ewt.timer.Timer._waitTilScheduled(Timer.java:433)
oracle.ewt.timer.Timer.run(Timer.java:295)
java.lang.Thread.run(Thread.java)
"Screen Updater" (TID:0x406e6bd8, sys_thread_t:0x41a0ce0c, state:CW) prio=4
java.lang.Object.wait(Object.java)
sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:78)
sun.awt.ScreenUpdater.run(ScreenUpdater.java:98)
"AWT-Finalizer" (TID:0x406f1b28, sys_thread_t:0x419a2e0c, state:CW) prio=9
java.lang.Object.wait(Object.java)
sun.awt.AWTFinalizer.run(AWTFinalizer.java:48)
"Image Fetcher 1" (TID:0x406ef488, sys_thread_t:0x41981e0c, state:CW) prio=8
sun.awt.image.ImageFetcher.nextImage(ImageFetcher.java:109)
sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:146)
sun.awt.image.ImageFetcher.run(ImageFetcher.java:127)
"AWT-Motif" (TID:0x406d3978, sys_thread_t:0x4148be0c, state:CW) prio=5
java.lang.Thread.run(Thread.java)
"AWT-Input" (TID:0x406d3998, sys_thread_t:0x4146ae0c, state:CW) prio=5
"AWT-EventQueue-0" (TID:0x406d36f8, sys_thread_t:0x41449e0c, state:CW) prio=5
java.lang.Object.wait(Object.java)
sun.awt.motif.MDialogPeer.show(MDialogPeer.java:104)
java.awt.Dialog.show(Dialog.java:218)
oracle.net.asst.servicename.ServiceName.executeComponentMenu(ServiceName.java:461)
oracle.net.asst.container.NetContainer.commandIssued(NetContainer.java:870)
oracle.sysman.emSDK.client.guiComponent.commandAdapter.CommandAdapter.deliverEvent(CommandAdapter.java:409)
oracle.sysman.emSDK.client.guiComponent.commandAdapter.CommandAdapter.commandIssued(CommandAdapter.java:422)
oracle.sysman.emSDK.client.guiComponent.commandAdapter.CommandAdapter.actionPerformed(CommandAdapter.java:386)
oracle.ewt.lwAWT.lwMenu.LWMenuItem.processActionEvent(LWMenuItem.java:658)
oracle.ewt.lwAWT.lwMenu.LWMenuItem.processEventImpl(LWMenuItem.java:615)
oracle.ewt.lwAWT.LWComponent.redispatchEvent(LWComponent.java:2863)
oracle.ewt.lwAWT.LWComponent.processEvent(LWComponent.java:3107)
oracle.ewt.lwAWT.lwMenu.LWMenuItem.activate(LWMenuItem.java:79)
oracle.ewt.lwAWT.lwMenu.laf.VertMenuItemController.mouseReleased(VertMenuItemController.java:98)
java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:236)
java.awt.Component.processMouseEvent(Component.java:2404)
oracle.ewt.lwAWT.LWComponent.processMouseEvent(LWComponent.java:3155)
java.awt.Component.processEvent(Component.java:2249)
java.awt.Container.processEvent(Container.java:878)
oracle.ewt.lwAWT.LWComponent.processEventImpl(LWComponent.java:3128)
"Finalizer thread" (TID:0x406cd208, sys_thread_t:0x4141fe0c, state:R) prio=1
"Async Garbage Collector" (TID:0x406cd250, sys_thread_t:0x413fee0c, state:R) prio=1
"Idle thread" (TID:0x406cd298, sys_thread_t:0x413dde0c, state:R) prio=0
"Clock" (TID:0x406cd088, sys_thread_t:0x413bce0c, state:CW) prio=12
"main" (TID:0x406cd0b0, sys_thread_t:0x81a2750, state:CW) prio=5
Monitor Cache Dump:
<unknown key> (0x0x413fee0c): owner "Async Garbage Collector" (0x413fee0c, 1 entry)
oracle.net.asst.servicewizard.TestConnDialog@1081116976/1082626288: owner "Thread-5" (0x419cae0c, 1 entry)
sun.awt.ScreenUpdater@1080978392/1082109680: <unowned>
Waiting to be notified:
"Screen Updater" (0x41a0ce0c)
oracle.ewt.timer.Timer@1081055480/1082065880: <unowned>
Waiting to be notified:
"TaskScheduler timer" (0x41a2de0c)
java.util.Vector@1081002552/1081642952: <unowned>
Waiting to be notified:
"Image Fetcher 1" (0x41981e0c)
"Image Fetcher 0" (0x419ebe0c)
<unknown key> (0x0x41a4ee0c): <unowned>
Waiting to be notified:
"CursorIdler" (0x41a4ee0c)
sun.awt.motif.ModalThread@1081087152/1082363448: owner "AWT-Modal" (0x414ace0c, 1 entry)
Waiting to be notified:
"AWT-EventQueue-0" (0x41449e0c)
java.awt.EventQueue@1080899400/1081276096: <unowned>
Waiting to be notified:
"AWT-Dispatch-Proxy" (0x41960e0c)
sun.awt.motif.MToolkit@1080899448/1081275848: <unowned>
Waiting to be notified:
"AWT-Modal" (0x414ace0c)
"AWT-Motif" (0x4148be0c)
sun.awt.AWTFinalizer@1081023272/1081142608: <unowned>
Waiting to be notified:
"AWT-Finalizer" (0x419a2e0c)
Registered Monitor Dump:
Thread queue lock: <unowned>
Waiting to be notified:
"main" (0x81a2750)
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>
Monitor IO lock: <unowned>
Child death monitor: <unowned>
Event monitor: <unowned>
I/O monitor: <unowned>
Waiting to be notified:
"AWT-Input" (0x4146ae0c)
Alarm monitor: <unowned>
Waiting to be notified:
"Clock" (0x413bce0c)
Monitor registry: owner "Thread-5" (0x419cae0c, 1 entry)
Thread Alarm Q:
sys_thread_t 0x414ace0c [Timeout in 67 ms]
sys_thread_t 0x4146ae0c [Timeout in 215 ms]
sys_thread_t 0x41a4ee0c [Timeout in 495 ms]
sys_thread_t 0x41981e0c [Timeout in 2505 ms]
sys_thread_t 0x419ebe0c [Timeout in 4989 ms]
Please advise

I am covering this topic in my homepage:
http://homepages.tig.com.au/~jmsalvo/linux/oracle8i-5.html
Granted that this page is not complete yet, revisit the page within 4 to 8 hours and it should be completed by then.
In any case, my short answer: you do not have to use netassst. There are command line utilities to the same thing.
You can use two tools to test a listener:
* lsnrctl. The only problem with this is that it will use the IPC protocol and not the TCP protocol. Regardless of that, the IPC protocol requires a listner to work properly. Type help at the lsnrctl command prompt for things you can do. If you get positive reponses, then you can be sure that the IPC protocol works with the listener.
* tnsping. This seems to use the TCP protocol. So you can run this on the same machine where 8i is installed or on another machine where 8i client software is installed (granted you have setup sqlnet.ora and tnsnames.ora).
Hope this helps.
null

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

Hurry: SIGSEGV 11 segmentation violation

Environment: IAS 6.0 SP4, Sun Solaris 2.8.
The KJS server crashes every day with Segmentation fault The error message from the KJS log is given below.
We set iasenv.ksh env. (JAVA_ARGS="-Xss2048k -Xms128m -Xmx256m")
but, continue.... The mesage is given below.
help us.
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x0]
stackpointer=E1F7F4B0
"Thread-45" (TID:0x41569b0, sys_thread_t:0x41568e8, state:CW, thread_t: t@55, threadID:0xea862a00, stack_bottom:0xe1d00000, stack_size:0x200000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] org.apache.tomcat.util.Queue.pull(Unknown Source)
[3] org.apache.tomcat.logging.LogDaemon$1.run(Unknown Source)
[4] org.apache.tomcat.logging.LogDaemon.run(Unknown Source)
"Finalizer" (TID:0x3d08e98, sys_thread_t:0x3d08dd0, state:R, thread_t: t@54, threadID:0xea862800, stack_bottom:0xe1f80000, stack_size:0x200000) prio=8 current thread
[1] com.kivasoft.data2.JDBCConnection.closenative(Native Method)
[2] com.kivasoft.data2.JDBCConnection.close(Unknown Source)
[3] com.netscape.server.jdbc.Connection.close(Unknown Source)
[4] com.netscape.server.jdbc.Connection.finalize(Unknown Source)
[5] java.lang.ref.Finalizer$FinalizerWorker.finalizeOne(Finalizer.java:86)
[6] java.lang.ref.Finalizer$FinalizerWorker.access$3(Finalizer.java:82)
[7] java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:124)
"Thread-44" (TID:0xb95470, sys_thread_t:0xb953a8, state:R, thread_t: t@53, threadID:0xea862600, stack_bottom:0xe2a80000, stack_size:0x200000) prio=5
[1] com.kivasoft.thread.ThreadBasic.run(Native Method)
[2] java.lang.Thread.run(Thread.java:478)
"Thread-43" (TID:0xbaf5c0, sys_thread_t:0xbaf4f8, state:CW, thread_t: t@52, threadID:0xea862400, stack_bottom:0xe2d00000, 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:0xb554c8, sys_thread_t:0xb55400, state:CW, thread_t: t@51, threadID:0xea862200, stack_bottom:0xe2f80000, stack_size:0x200000) prio=5
[1] com.kivasoft.thread.ThreadBasic.sleep(Unknown Source)
[2] com.kivasoft.thread.ThreadBasic.run(Native Method)
[3] java.lang.Thread.run(Thread.java:478)
"Thread-41" (TID:0xb59508, sys_thread_t:0xb59440, state:R, thread_t: t@50, threadID:0xea862000, stack_bottom:0xe3200000, stack_size:0x200000) prio=5
/home/iplanet/ias60/ias/bin/kjs[75]: 3794 �� (Segmentation Fault)(�� )
Starting Java Engine
Engine running on Solaris VM 1.2.2 JVM supplied by Sun Microsystems Inc.
Connected to LDAP server on sdi03p.samsung.co.kr port 389
iPlanet Application Server is running in international mode
Initializing LDAP cache from server sdi03p.samsung.co.kr port 389
LDAP cache initialization completed successfully.

You could try increasing the max heap size we saw alot of SIGBUS 10 crashes with sp4 until we increased this value to 1024 which happens to be the default in 6.5. Turn on garbage collection statistics with -verbose:gc if you suspect this could be the problem. The stack size should be set to about 10% the size of the (entire) registry.
Usually however these errors tend to be code related...
Does the crash happen at the same time everyday.

Segmentation Violation Exceptions

Similar Messages

Maybe you are looking for