Re: Moving from 10.5.3.0 -> 10.12.1.1 SQLNonTransientConnectionException but 10.5.3.0 ->10.7.1.1 is working perfectly exactly same code, 10.5.3.0 -> 10.8.1.2 fails similar

I found the problem and suggested a fix to the code. See comments in https://issues.apache.org/jira/browse/DERBY-6726 On Wed, Sep 28, 2016 at 2:03 PM, bruehlicke wrote: > I have managed to crystallize out the error into a standalone JUnit 4 test > and uploaded a NetBeans

Re: Moving from 10.5.3.0 -> 10.12.1.1 SQLNonTransientConnectionException but 10.5.3.0 ->10.7.1.1 is working perfectly exactly same code, 10.5.3.0 -> 10.8.1.2 fails similar

I have managed to crystallize out the error into a standalone JUnit 4 test and uploaded a NetBeans project with this to JIRA under DERBY-6726. Hope this will allow us to hunt down the issue which really was introduced with 10.8. On Tue, Sep 27, 2016 at 9:18 PM, bruehlicke

Re: Moving from 10.5.3.0 -> 10.12.1.1 SQLNonTransientConnectionException but 10.5.3.0 ->10.7.1.1 is working perfectly exactly same code, 10.5.3.0 -> 10.8.1.2 fails similar

Thanx I will see if I can narrow it down. I do rebuild the entire sets of Tables and triggers and hence I would be able to make this reproducable. I will work on making a small test app and see if I can make it fail. The interesting bit is that the UPDATE works if I paste the SQL statement

Re: Moving from 10.5.3.0 -> 10.12.1.1 SQLNonTransientConnectionException but 10.5.3.0 ->10.7.1.1 is working perfectly exactly same code, 10.5.3.0 -> 10.8.1.2 fails similar

java.lang.NullPointerException at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getTriggerActionString(Unknown Source) at org.apache.derby.iapi.sql.dictionary.TriggerDescriptor.getActionSPS(Unknown Source) This definitely looks like it could be DERBY-6726