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 ;-)


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

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

Chris Wright
CrossCheck, Inc.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.