Re: Derby 10.15.3.1 - Java 8?

2019-04-29 Thread Rick Hillegas
I don't see derbyshared.jar on the classpath. That new jar is required for all 10.15 configurations. On 4/29/19 11:29 AM, Oskar Z wrote: Hi Rick, I’m running a back ported  fix from 10.15 in 10.14: DERBY-6981 "SQLSTATE: XJ001, SQLERRMC:

Re: Derby 10.15.3.1 - Java 8?

2019-04-29 Thread Oskar Z
Hi Rick, I’m running a back ported fix from 10.15 in 10.14: >> DERBY-6981 >> "SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerException XJ001.U" Classptah includes all the jars, derby.jar, derbynet.jar,

Re: Derby 10.15.3.1 - Java 8?

2019-04-29 Thread Rick Hillegas
That looks odd. I thought that line numbers would be included in 10.15 stack traces. It's dying while trying to open a connection. What does your classpath look like? On 4/29/19 9:05 AM, Oskar Z wrote: Hi Rick, As follow-up so we started running the ported fix for the NullPointerException….

Re: Derby 10.15.3.1 - Java 8?

2019-04-29 Thread Oskar Z
Hi Rick, I’m not running 10.15 actually. I’m running 10.14 with only 1 line code change from defect: DERBY-6981 "SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerException XJ001.U" Thanks, Oskar > On Apr 29,

Re: Derby 10.15.3.1 - Java 8?

2019-04-29 Thread Rick Hillegas
Oh, right. That would explain why we don't see line numbers. Without line numbers it's hard to speculate about what's gone wrong. I don't have any theory about why a one line change to the engine jar file would raise an NPE on the client-side. Can you attach derby.log to DERBY-6981? Maybe