Jump to content
We've recently updated our Privacy Statement, available here ×

Has anyone seen this issue (Segmentation error)

wooderi

By wooderi
in Products

 Share

Recommended Posts

wooderi Rookie

wooderi

Posted
Posted

Has anyone seen this issue (Unhandled exception Type=Segmentation error vmState=0x0005ff0c)?

We are running jasper reports 3.7.1 on AIX 5.3 with Java6 and iText-2.1.0. The report uses XML datasource and from time to time we are getting intermittent core dumps with error...

Unhandled exception Type=Segmentation error vmState=0x0005ff0c

Method_being_compiled=com/lowagie/text/pdf/PdfDocument.writeLineToContent(Lcom/l
owagie/text/pdf/PdfLine;Lcom/lowagie/text/pdf/PdfContentByte;Lcom/lowagie/text/p
df/PdfContentByte;[Ljava/lang/Object;F)V

I can reprocess the same report / XML file 100+ times after getting this error without it happening again. Then after awhile it does it again. Any ideas what might be causing this, or is it possible to catch the exception to avoid the JVM crashing?

Thanks in advance!

Code:
                JRDataSource xmlcon = xmlConnection(datafile, selectstatement);                jPrint = JasperFillManager.fillReport(jasperReport,                        jasperParameter, xmlcon);                JasperExportManager.exportReportToPdfFile(jPrint,                        outputfile + ".pdf");    public JRDataSource xmlConnection(String datafile,            String selectstatement) {        JRDataSource connection = null;        try {            JRDataSource ds = new JRXmlDataSource(datafile, selectstatement);            connection = ds;
Link to comment
Share on other sites
  • 4 weeks later...
  • Replies 13
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

dcabasson Newbie

dcabasson

Posted
Posted

Hi,

We are having a similar issue, with AIX 6.1. We are running Websphere Application Server 7.0.0.9 (so I guess an IBM Java 6 JRE), with iText 2.1.4 / Jasperreport 3.7.0.

We encountered for the second time this exception :

Unhandled exception
Type=Segmentation error vmState=0x0005ff0c
...

Method_being_compiled=com/lowagie/text/pdf/PdfDocument.writeLineToContent(Lcom/lowagie/text/pdf/PdfLine;Lcom/lowagie/text/pdf/PdfContentByte;Lcom/lowagie/text/pdf/PdfContentByte;[Ljava/lang/Object;F)V

I have opened a PMR with IBM to see if they have any insight on that. It is the second time we had that error at this place. I am not sure whether it is because of some memory shortage or something else, but that is taking the server down pretty hard.

Link to comment
Share on other sites
frab Rookie

frab

Posted
Posted

 We also have the exact same issue :

 

 

2XHOSLEVEL     OS Level         : AIX 5.3

2XHCPUS        Processors -

3XHCPUARCH       Architecture   : ppc

3XHNUMCPUS       How Many       : 1

3XHNUMASUP       NUMA is either not supported or has been disabled by user

NULL           

1XHEXCPCODE    J9Generic_Signal_Number: 00000004

1XHEXCPCODE    Signal_Number: 0000000B

1XHEXCPCODE    Error_Value: 00000000

1XHEXCPCODE    Signal_Code: 00000033

1XHEXCPCODE    Handler1: F0D90C80

1XHEXCPCODE    Handler2: F0D8AAC4

NULL           

1XHEXCPMODULE  Module: /opt/java6/jre/lib/ppc/libj9jit24.so

1XHEXCPMODULE  Module_base_address: D1C48000

NULL           

1XHREGISTERS   Registers:

...

1XHEXCPMODULE  Compiling method: com/lowagie/text/pdf/PdfDocument.writeLineToContent.(Lcom/lowagie/text/pdf/PdfLine;Lcom/lowagie/text/pdf/PdfContentByte;Lcom/lowagie/text/pdf/PdfContentByte;[Ljava/lang/Object;F)V

NULL           

1XHFLAGS       VM flags:0005FF0C

NULL           

NULL           ------------------------------------------------------------------------

0SECTION       ENVINFO subcomponent dump routine

NULL           =================================

1CIJAVAVERSION JRE 1.6.0 IBM J9 2.4 AIX ppc-32 build jvmap3260sr8-20100401_55940

1CIVMVERSION   VM build 20100401_055940

1CIJITVERSION  JIT enabled, AOT enabled - r9_20100401_15339

1CIGCVERSION   GC - 20100308_AA

1CIRUNNINGAS   Running as a standalone JVM

1CICMDLINE     /usr/java6/bin/java -Xms64M -Xmx128M -Xverify:none ......

1CIJAVAHOMEDIR Java Home Dir:   /opt/java6/jre

1CIJAVADLLDIR  Java DLL Dir:    /opt/java6/jre/bin

 

 

Link to comment
Share on other sites
wooderi Rookie

wooderi

Posted
  • Author
Posted

I found a workaround for this by turning off the JIT compiler.

export JAVA_COMPILER=NONE or -Djava.compiler=NONE but processing time on large reports are much much slower. Please let us know if you find anything out from IBM.

 

Link to comment
Share on other sites
frab Rookie

frab

Posted
Posted

We are currently testing the same kind of workaround : disabling the JIT compiler by using the -Xint option on the command line.

For now, it sounds to work but the work load of our system is not high enough to really say whether it is a real workaround or if we were just "lucky" until now... 

 



Post Edited by frab42 at 06/03/2010 14:27
Link to comment
Share on other sites
dcabasson Newbie

dcabasson

Posted
Posted

We have a PMR open with IBM on the matter. IBM already has a previous PMR opened on the matter. Their advice is to turn off JIT on this class. They are working on reproducing the issue in their lab and will let me know when a solution becomes available. 

Link to comment
Share on other sites
frab Rookie

frab

Posted
Posted

 We just received an answer from the IBM support.

In our case, the problem may be caused by a heap corruption due to a bug in the AIX  C runtime libs.

We are currently installing a patch provided by the IBM support and we will see what happen.

 



Post Edited by frab42 at 06/09/2010 15:43
Link to comment
Share on other sites
frab Rookie

frab

Posted
Posted

 Here is the reference of what we are asked to install "IZ68763: GETGRENT_R CAUSES SIGSEGV WHEN INVOKED BY MULTIPLE THREADS. APPLIES TO AIX 5300-10".  Our Unix administrator wants to ask more questions before applying this since it impacts a lot of things in the system, I will post more when I have more details.

 



Post Edited by frab42 at 06/09/2010 15:48



Post Edited by frab42 at 06/09/2010 15:49
Link to comment
Share on other sites
  • 8 months later...
sriniv Newbie

sriniv

Posted
Posted

We ended up getting a core due to the same error today.

1XHEXCPMODULE  Compiling method: com/lowagie/text/pdf/PdfDocument.writeLineToContent.(Lcom/lowagie/text/pdf/PdfLine;Lcom/lowagie/text/pdf/PdfContentByte;Lcom/lowagie/text/pdf/PdfContentByte;[Ljava/lang/Object;F)VWe are on Jasperserver 3.7.0 on IBM JDK 1.6 64 bit running on AIX 5.3. We run Jasper under Tomcat 6.0.20. Opened a support case with jasper.

 

Link to comment
Share on other sites
wooderi Rookie

wooderi

Posted
  • Author
Posted

From what we were told by IBM, it should be fixed in OS version AIX 5.3 TL12, Service Pack 2 released in December. But we haven't had a chance to upgrade yet. I'm still using the work around JAVA_COMPILER=NONE (Slow!!)
 

Link to comment
Share on other sites
jared1451 Newbie

jared1451

Posted
Posted

Still getting the same error even though the latest IBM AIX 6.1 patches have been applied

 bash-3.2# oslevel -s
6100-06-01-1043
bash-3.2# lslpp -l |grep bos.rte.libc
  bos.rte.libc               6.1.6.1  COMMITTED  libc Library
  bos.rte.libcfg             6.1.6.0  COMMITTED  libcfg Library
  bos.rte.libcur             6.1.6.0  COMMITTED  libcurses Library
  bos.rte.libc               6.1.6.1  COMMITTED  libc Library
  bos.rte.libcfg             6.1.6.0  COMMITTED  libcfg Library
  bos.rte.libcur             6.1.6.0  COMMITTED  libcurses Library

dsuat2cbcppfins01
bash-3.2# oslevel -s
6100-06-01-1043
bash-3.2# lslpp -l |grep bos.rte.libc
  bos.rte.libc               6.1.6.1  COMMITTED  libc Library
  bos.rte.libcfg             6.1.6.0  COMMITTED  libcfg Library
  bos.rte.libcur             6.1.6.0  COMMITTED  libcurses Library
  bos.rte.libc               6.1.6.1  COMMITTED  libc Library
  bos.rte.libcfg             6.1.6.0  COMMITTED  libcfg Library
  bos.rte.libcur             6.1.6.0  COMMITTED  libcurses Library

Unhandled exception
Type=Segmentation error vmState=0x0005ff0c
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=F1396C80 Handler2=F138DB7C
R0=0000B190 R1=3279EDE0 R2=F13EB078 R3=35B906DC
R4=0000001C R5=35B90640 R6=35E173B0 R7=00000003
R8=357F3404 R9=F13C5EC8 R10=00000001 R11=00000000
R12=D4825ECC R13=5265706F R14=72742F6C R15=69622F70
R16=6F692D33 R17=31DBB190 R18=31DB5C18 R19=414C2D32
R20=00000000 R21=35E1738C R22=357F3404 R23=000031DC
R24=00000064 R25=00000060 R26=0000B190 R27=00000018
R28=00000038 R29=35812BF8 R30=35812C3C R31=35812BC8
IAR=D4825E70 LR=D4825ECC MSR=0000D032 CTR=D4825944
CR=8840244B FPSCR=A6164100 XER=00000004 TID=00000000
MQ=73716C2D
FPR0 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR1 3ff0000000000000 (f: 0.000000, d: 1.000000e+00)
FPR2 4034000000000000 (f: 0.000000, d: 2.000000e+01)
FPR3 4330000080000377 (f: 2147484416.000000, d: 4.503602e+15)
FPR4 4330080000000000 (f: 0.000000, d: 4.512396e+15)
FPR5 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR6 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/java6/jre/lib/ppc/libj9jit24.so
Module_base_address=D453C000

Method_being_compiled=com/lowagie/text/pdf/PdfDocument.writeLineToContent(Lcom/lowagie/text/pdf/PdfLine;Lcom/lowagie/text/pdf/PdfContentByte;Lcom/lowagie/text/pdf/PdfContentByte;[Ljava/lang/Object;F)V
Target=2_40_20100609_059383 (AIX 6.1)
CPU=ppc (16 logical CPUs) (0x740000000 RAM)
----------- Stack Backtrace -----------
(0xD46D5558 [libj9jit24.so+0x199558])
(0xD4576D00 [libj9jit24.so+0x3ad00])
(0xD4576570 [libj9jit24.so+0x3a570])
(0xD455C5FC [libj9jit24.so+0x205fc])
(0xD455BBF4 [libj9jit24.so+0x1fbf4])
(0xD4544A4C [libj9jit24.so+0x8a4c])
(0xD45438B4 [libj9jit24.so+0x78b4])
(0xD4478A98 [libj9prt24.so+0x3a98])
(0xD45417F0 [libj9jit24.so+0x57f0])
(0xD45407B4 [libj9jit24.so+0x47b4])
(0xD4478A98 [libj9prt24.so+0x3a98])
(0xD453F2CC [libj9jit24.so+0x32cc])
(0xD44687CC [libj9thr24.so+0x27cc])
_pthread_body+0xec (0xD04ECC50 [libpthreads.a+0x3c50])
---------------------------------------
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP032I JVM requested System dump using

Still getting the same issue any one having any idea bout why so ?
Has the IBM patch helped any one resolve the issue previously ?

Link to comment
Share on other sites
jared1451 Newbie

jared1451

Posted
Posted

Hi all

In my case the appearing even after the latest patch being deployed. The reason was that part from the bug in the IBM AIX c libraries there was a bug in the IBM j9 JIT too. The bug hs been resolved in the sr9 of j9 1.6

Here is the IBM portal link regarding the same

http://www-01.ibm.com/support/docview.wss?uid=swg1IZ77436

Since i dint have the luxury to update the JVM i disabled the JIT for that specific method. Instead of disabling the JIT in general , which will make it very very very slow this option suggested by IBM is great and no preformance lag was reported. Hope this helps:)

Cheers ,

Jared

Link to comment
Share on other sites
  • 11 months later...
sivab Newbie

sivab

Posted
Posted

I am facing this exception In RFT(Rational functional testing) while playback the script, if any body know please letme know.

(bschandrasekhar4@gmail.com)      (this si my personal mail-id)

 

 

 

Unhandled exception

Type=Segmentation error vmState=0x6a2f727c

J9Generic_Signal_Number=00000004 ExceptionCode=c0000005 ExceptionAddress=6AF7F12C ContextFlags=0001003f

Handler1=7FEFA110 Handler2=7FECC060 InaccessibleAddress=00000000

EDI=000000E7 ESI=780CCC40 EAX=00000000 EBX=00000000

ECX=0087F444 EDX=6AFC02BC

EIP=6AF7F12C ESP=0087F414 EBP=0087F450 EFLAGS=00210202

GS=0000 FS=003B ES=0023 DS=0023

Module=C:Program FilesIBMSDPFunctionalTesterbinrtxivsys.dll

Module_base_address=6AF40000 Offset_in_DLL=0003f12c

Target=2_40_20110624_085526 (Windows XP 5.1 build 2600 Service Pack 3)

CPU=x86 (2 logical CPUs) (0xcdb7f000 RAM)

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

© 2024 Cloud Software Group,
Inc. All rights reserved.

Products

Explore