RE: JVM Problems using JDBCR4 -- RPG400-L

Thanks for the response, Scott!

The AS400 job produced the following:

Unhandled exception
Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000032
Handler1=F01ACA18 Handler2=F01A7A10
R0=00000000 R1=30058D60 R2=F01AE0BC R3=00000000
R4=FFFFFFFC R5=00000000 R6=00000003 R7=D21AE898
R8=00000001 R9=00000001 R10=30058F50 R11=30058F50
R12=00000000 R13=32594C00 R14=33C39084 R15=F03C5024
R16=00000007 R17=00000002 R18=F01AE968 R19=00000002
R20=00000410 R21=30059010 R22=00000000 R23=00000000
R24=F01AA3A0 R25=D05EEBF0 R26=D21AE898 R27=00000001
R28=00000000 R29=30058EE0 R30=30058F50 R31=00000000
IAR=D05AEAB8 LR=D05AE89C MSR=0000F032 CTR=D004FC80
CR=22401841 FPSCR=82020000 XER=32000010 TID=00000000
MQ=00000000
FPR0 0000000082020000 (f: 2181169152.000000, d: 1.077641e-314)
FPR1 0000000020100000 (f: 537919488.000000, d: 2.657675e-315)
FPR2 41c3028000000000 (f: 0.000000, d: 6.378619e+08)
FPR3 4070000000000000 (f: 0.000000, d: 2.560000e+02)
FPR4 410999999999999a (f: 2576980480.000000, d: 2.097152e+05)
FPR5 3fa999999999999a (f: 2576980480.000000, d: 5.000000e-02)
FPR6 00000000000a74c0 (f: 685248.000000, d: 3.385575e-318)
FPR7 4124e98000000000 (f: 0.000000, d: 6.852480e+05)
FPR8 006f006c0020002d (f: 2097197.000000, d: 1.379619e-306)
FPR9 006f006e00740072 (f: 7602290.000000, d: 1.379620e-306)
FPR10 0072007400200063 (f: 2097251.000000, d: 1.602211e-306)
FPR11 4026000000000000 (f: 0.000000, d: 1.100000e+01)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4020800000000000 (f: 0.000000, d: 8.250000e+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=/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit/jre/bin/libj9vm23.so
Module_base_address=D058A000
Target=2_30_20150323_240985_bHdSMr (OS/400 V6R1M0)
CPU=ppc (4 logical CPUs) (0xc00000000 RAM)
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP032I JVM requested System dump using '/home/CCOWNER/core.20150622.095707.30509.0001.dmp' in response to an event
JVMDUMP010I System dump written to /home/CCOWNER/core.20150622.095707.30509.0001.dmp
JVMDUMP032I JVM requested Snap dump using '/home/CCOWNER/Snap.20150622.095707.30509.0002.trc' in response to an event
Carmen Leon Guerrero - I.S.
JVMDUMP010I Snap dump written to /home/CCOWNER/Snap.20150622.095707.30509.0002.trc
JVMDUMP032I JVM requested Java dump using '/home/CCOWNER/javacore.20150622.095707.30509.0003.txt' in response to an event
JVMDUMP010I Java dump written to /home/CCOWNER/javacore.20150622.095707.30509.0003.txt
JVMDUMP013I Processed dump event "gpf", detail "".

The javacore and snap dumps seem to suggest a memory problem - I can send these also, if that would be helpful - but they are big!

Chris

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, June 23, 2015 9:41 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: JVM Problems using JDBCR4

Hi Chris,

Is there any information printed to stdout? Any job log information with more details we can see? It would help a lot if you posted the actual error messages. Please make sure you start a fresh job before generating the messages to send -- because once the JVM has crashed, you won't get any useful messages until you start a new job again.

JDBC_Properties() does not use the network at all, so I think the network guys are off the hook on that one ;-)

-SK

On 6/23/2015 10:56 AM, Chris Wright wrote:

Hi,

We've been updating files on a remote SQL Server happily using Scott
Klement's JDBCR4 package since August 2011, until this weekend, when
it has suddenly stopped functioning - each call to the
JDBC_Properties() method causes the JVM to end and dump. Examination
of the dumps suggests that it is a general protection fault and hint
at memory issues, but attempts to change the initialization for the
JVM have not produced any results.

Our network guys swear blind that nothing has changed on the network
and we have tried changing which server it is trying to connect to ,
to no avail.

I've confirmed that other Java functions still work on the system, so
it is not a general problem with the JVM.

Any clues? I can provide copies of the dumps if these would be of
assistance.

Chris Wright
CrossCheck, Inc.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.