Re: JDBCR4 JVM Creation fails

Thanks Scott,

Yes I agree it is not an error in JDBCR4 it is the JVM start up that is
crashing.

I have opened a PMR and hopefully IBM will be able to at least point me on
the right path.

It currently seems like XMLSERVICE calling the service program that
subsequently starts a JVM is the issue - I'm just not that cleaver to be
able to work out why.

If I can't resolve it I might just just create a new program with a pair
of data queues and send the request on one queue and get the response from
the other.

Appreciate your response.

Thanks

Don Brown





From: "Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 18/04/2018 11:50 PM
Subject: Re: JDBCR4 JVM Creation fails
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Don,

This appears to be some sort of internal Java error. It's not really an
issue inside JDBCR4 itself -- all JDBCR4 is doing (as you pointed out)
is asking Java to create a string. You'd have the same problem using
any other process that uses Java within an RPG program.

What I'd suggest is to create a very simple RPG program that simply
creates a string and then frees it up and does nothing else. Run that
from within XMLSERVICE, and it should cause the exact same error.

Then, file a PMR with IBM asking for information about why it fails.
Provide the simple program and a job log and let them try it and see the
problem for themselves. At that point, they'll either give you a
solution, or will determine there's an internal problem and fix it.

-SK



On 4/18/2018 4:10 AM, Don Brown wrote:

IBMi Version V7R3 and current on PTF's
JDBCR4 version - not sure but I have downloaded again from Scott's web
site.

I have a service program that connects to a MS SQL server and retrieves

a

list of records, converts the results into json using yajl and returns

the

string.

If I run this from the command line it works perfectly.

If I call externally using XMLSERVICE it fails.

I have run the process in debug and in JDBCR4 the procedure start_jvm()
used to start the JVM , it simply calls the java method java.lang.String
with wwStr = s('Temp String'); which should start a JVM if there is not
already one running.

I have pasted the joblog below.

I have tried submitting the same process to batch using the same job
description (library list) and running under the same user profile and

it

completes normally.

I have looked at the dump files created but none of the content is
meaningful to me or for that matter indicates a reason for the failure.

Any suggestions most welcomed - I have been going in circles with this

for

quite a while!!

Java Virtual Machine is IBM Technology for Java. PID(15710)
Object domain or storage protection error for offset X'000000002B25B800'
in object XTOOLKIT PHPUSER 065558.
JVMDUMP039I Processing dump event "gpf", detail "" at 2018/04/18

07:50:46

- please wait.■
IBM Java[15710]: JVMDUMP039I Processing dump event "gpf", detail "" at
2018/04/18 07:50:46 - please wait.■
JVMDUMP032I JVM requested System dump using
'//core.20180418.075046.15710.0001.dmp' in response to an event■
IBM Java[15710]: JVMDUMP032I JVM requested System dump using
'//core.20180418.075046.15710.0001.dmp' in response to an event■
JVMDUMP010I System dump written to

//core.20180418.075046.15710.0001.dmp■

JVMDUMP032I JVM requested Java dump using
'//javacore.20180418.075046.15710.0002.txt' in response to an event■
IBM Java[15710]: JVMDUMP032I JVM requested Java dump using
'//javacore.20180418.075046.15710.0002.txt' in response to an event■
JVMDUMP010I Java dump written to
//javacore.20180418.075046.15710.0002.txt■
JVMDUMP032I JVM requested Snap dump using
'//Snap.20180418.075046.15710.0003.trc' in response to an event■
IBM Java[15710]: JVMDUMP032I JVM requested Snap dump using
'//Snap.20180418.075046.15710.0003.trc' in response to an event■
JVMDUMP010I Snap dump written to

//Snap.20180418.075046.15710.0003.trc■

JVMDUMP007I JVM Requesting JIT dump using
'//jitdump.20180418.075046.15710.0004.dmp'■
JVMDUMP010I JIT dump written to

//jitdump.20180418.075046.15710.0004.dmp■

JVMDUMP013I Processed dump event "gpf", detail "".■



Don Brown