Re: Derby 10.15.3.1 - Java 8?

Thanks for the log files, Oskar. It looks like you are running a replicated database. I am not an expert on how Derby replication works, so I am afraid that any theories I propose are likely to be red herrings. Maybe someone with replication experience can help you untangle this. On 5/1/19

Re: Derby 10.15.3.1 - Java 8?

Hi Rick, I have attached derby.log from master and slave to 6981. Let me know what you think. Thank you very much! Kind regards, Oskar > On Apr 29, 2019, at 3:53 PM, Rick Hillegas wrote: > > Oh, right. That would explain why we don't see line numbers. Without line > numbers it's hard to

Re: Derby 10.15.3.1 - Java 8?

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

Re: Derby 10.15.3.1 - Java 8?

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?

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?

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?

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?

Hi Oskar, The fix has not been ported to any earlier branches and no-one has volunteered to manage a new release on those older branches. You are correct that 10.15.1.3 requires Java 9 or higher. The fix does not look complicated--it's only one line, excluding the regression test. You could