Sakai-10 binary install

[Gregory Guthrie]

Still trying to work through a new binary install on Debian -
since I had some mySql issues, I went into mySql and deleted all of the mySql database, assuming that sakai with autoddl would re-create it on startup, and also did: "mysqld - initialize" to basically start over.

Now instead of a login failure, I just get an error page for /portal - not sure what sort of rabbit-hole I have fallen down, or how to get out.
Any hints welcome.

Now I get this:
Theta:8080 gives a standard Tomcat welcome page. Looks good.

Theta:8080/portal, now gives:
Error
An unexpected error has occurred.
Send a bug report
To send a bug report, describe what you were doing when the problem occurred, in the space below, and press the submit button.

Recovery
To recover from this error without sending in a bug report, please do the following:
* Press the Logout button above to logout.
* Close your browser to assure a clean start.
* Re-open your browser and start again.

And in the log files: https://www.filesanywhere.com/fs/v.aspx?v=8b7065865e6572a76c6a

2015-12-30 20:56:39,733 WARN http-bio-8080-exec-6 org.sakaiproject.portal.util.ErrorReporter - Bug Report bug-id: 6e846a98-052b-4724-9c71-52a2a55cc679 user: null usage-session: null time: Dec 30, 2015 20:56:39 user comment: null stack trace
org.sakaiproject.portal.api.PortalHandlerException: java.lang.IllegalStateException: The CacheManager has been shut down. It can no longer be used.
...
Request:
: AuthType:null
: CharEncoding:UTF-8
: ContentLength:-1
: ContentType:null
: ContextPath:/portal
: LocalAddress:192.168.10.51
: LocalName:192.168.10.51
: LocalPort:8080
: Method:GET
: PathInfo:null
: Protocol:HTTP/1.1
: QueryString:null
: RemoteAddress:192.168.10.50
: RemoteHost:192.168.10.50
: RemotePort:24776
: Requested URL:http://theta:8080/portal
: Scheme:http
: ServerName:theta
: Headers:
: Header:host:theta:8080
: Header:accept-language:en-us,en;q=0.5
: Header:accept-encoding:gzip, deflate
: Header:accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
: Header:user-agent:Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20150101 Firefox/20.0 (Chrome)
: Header:accept-charset:ISO-8859-1,utf-8;q=0.7,*;q=0.7
: Header:connection:close
: Header:cookie:---censored---
: Parameters:
: Attributes:
: Attribute:sakai.character.encoding.done:sakai.character.encoding.done
: Attribute:sakai.filtered:sakai.filtered
: Attribute:sakai.session:MyS_null{b1569137-9263-4b5e-b6cd-61ed69563836, userId='null', at=2, ts=0, cs=1, Wed Dec 30 20:56:39 CST 2015}
Session:
: Created:1451530599704
: LastAccess:1451530599728
: CreationDateAndTime:Wednesday, December 30, 2015
: LastAccessDateAndTime:Wednesday, December 30, 2015
: MaxInactive:1800
: Attributes:

2015-12-30 20:56:39,734 WARN http-bio-8080-exec-6 org.sakaiproject.email.impl.BasicEmailService - send: javax.mail.internet.AddressException: Illegal address in string ``''

-------------------------------------------
Dr. Gregory Guthrie

Computer Science Department
Dean, and Professor of Computer Science
School of Computer Science & Mathematics
Maharishi University of Management
-------------------------------------------

[Brian Baillargeon]

You've got some 'fatal' logs about the database not being set up for UTF-8:
"2015-12-30 22:04:11,652 FATAL localhost-startStop-1
org.sakaiproject.content.impl.DbContentService - WARNING The
connection from this instance of Sakai to the database has been tested
and found to corrupt UTF-8 Data. In order for Sakai to operate
correctly you must ensure that your database setup is correct for
UTF-8 data. This includes both the JDBC connection to the database and
the underlying storage in the database. The test that was performed
on your database create a table wrote some data to that table and read
it back again. On reading that data back it found some form of
corruption, reported above."

In your sakai.properties, does your u...@javax.sql.BaseDataSource conform
to this format?:
u...@javax.sql.BaseDataSource=jdbc:mysql://127.0.0.1:3306/sakai?useUnicode=true&characterEncoding=UTF-8

[Gregory Guthrie]

Thanks - I had missed that error message.

But, I do have the described addition to server.xml of: "URIEncoding="UTF-8"

In the error message referenced page it also asks for adding that to the 8009 connector - which is not part of the install instructions, but I tried it anyway. I get the same error message(s).

I was using mySQL - maybe I should try the HSQLDB instead/first.

Are there any restrictions or requirements for he tomcat version to use? I am using 7.0.67 which is the latest/current version.

I am not very mySQL literate, but will try to find a way to query the database for its properties.

Is there some way to just erase the autoddl database, and let it start over (clear/clean)?

-------------------------------------------

[Matthew Jones]

There was a discussion on the production list yesterday (and dev list last week but most people from the US were on vacation) that referenced

https://jira.sakaiproject.org/browse/SAK-30173

That basically says there's some bug with Tomcat 7.0.67 and it doesn't work. You should try 7.0.65 until the next version of Tomcat 7.0.x is released. 7.0.65 is the version that Sakai is running on the nighties and was QA'd with.

Though there is some new issue too with JSP's and stricter escaping that was also introduced with 7.0.65 that may be a problem for custom jsps, but everything OOTB should work.

https://bz.apache.org/bugzilla/show_bug.cgi?id=57136

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.
To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

[Gregory Guthrie]

Wow – thanks – this immediately eliminated many errors that have been mystifying and fighting me for a week now!

 

One elated question – to use mySQL, does one need to install any additional connector? None is described in the Confluence binary install document, but The “Sakai Database Support” page (https://confluence.sakaiproject.org/display/DOC/Sakai+10+database+support) does seem to indicate it.

 

Can the binary install work OOTB with mySQL?

 

-------------------------------------------

[Matthew Buckett]

For Sakai 10 you will need to get a copy of the MySQL Connector/J JAR
and put in in tomcat/common/lib.

Sakai 11 ships with a MariaDB connector which will connect to MySQL as
well as MariaDB so you don't have to install the connector. The reason
the MySQL connector isn't included by default is that it's license
isn't compatible with Sakai.

On 6 January 2016 at 14:33, Gregory Guthrie <gut...@mum.edu> wrote:
> Wow – thanks – this immediately eliminated many errors that have been
> mystifying and fighting me for a week now!
>
>
>
> One elated question – to use mySQL, does one need to install any additional
> connector? None is described in the Confluence binary install document, but
> The “Sakai Database Support” page
> (https://confluence.sakaiproject.org/display/DOC/Sakai+10+database+support)
> does seem to indicate it.
>
>
>
> Can the binary install work OOTB with mySQL?
>
>
>
> -------------------------------------------
>
> From: Matthew Jones [mailto:mat...@longsight.com]
> Sent: Tuesday, January 05, 2016 10:55 PM
> To: Gregory Guthrie

--
Matthew Buckett, VLE Developer, IT Services, University of Oxford

[Matthew Jones]

Yeah, right, we probably could backport this to 10 for 10.7 but currently you still need to take that extra step for 10. I've been using the Maria driver against both MySQL and Maria with no problems for at least 6 months since we added it to Sakai 11 in KNL-1364.

The only change is to change your driverClassName to

driverC...@javax.sql.BaseDataSource=org.mariadb.jdbc.Driver

Saves a step or two in the installation.

[Gregory Guthrie]

Thanks - even if it is not included, it would be good if this is mentioned in the install instructions page.

Same for the Tomcat version issues.

Thanks!!

-------------------------------------------

> -----Original Message-----
> From: Matthew Buckett [mailto:matthew...@it.ox.ac.uk]
> Sent: Wednesday, January 06, 2016 8:39 AM
> To: Gregory Guthrie
> Cc: Matthew Jones; Brian Baillargeon; saka...@apereo.org
> Subject: Re: [sakai-dev] Sakai-10 binary install
>

[Neal Caidin]

I've just updated the documentation. See if you can find it? Hopefully it is obvious. I added the caveat about Tomcat versions and tried to include information about the MySql connector. Please feel free to edit and modify! Make it better.

Thanks.

Under Install Guide for Sakai 10

https://confluence.sakaiproject.org/display/DOC/Sakai+10+Install+Guides

[Gregory Guthrie]

Matthew,

Thanks for the suggestion.
Still fighting with a new install for sakai-10.5.

Tomcat 7.0.65
Sakai 10.5
mariadb-java-client-1.3.3.jar
mysql-connector-java-5.1.38-bin.jar
mysql Ver 14.14 Distrib 5.5.46, for debian-linux-gnu (x86_64)

I did this driver change and installed the Maria Driver (V. ) and changed the Driver definition, but I get a lot of DB errors, so I am still missing something? The error message I get is “database Sakai does not exist”.

So I guessed that I needed to manually create the database first, as described in (https://confluence.sakaiproject.org/display/DOC/Sakai+10+database+support ) and which used to be a part of the install process in earlier versions (2.x), although it would seem curious if this is really required now yet not mentioned.

I get error messages; starting with:
2016-01-08 22:12:30,690 WARN localhost-startStop-1 org.hibernate.id.UUIDHexGenerator - Using org.hibernate.id.UUIDHexGenerator which does not generate IETF RFC 4122 compliant UUID values; consider using org.hibernate.id.UUIDGenerator instead

And then a lot of database warnings (I have autoddl=true);
2016-01-08 22:12:54,835 WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): recordAlreadyExists: false, failQuiet: true, : error code: 1060, sql: ALTER TABLE SAKAI_SITE_PAGE ADD (POPUP CHAR(1) DEFAULT '0' CHECK (POPUP IN (1, 0))), binds: , error: java.sql.SQLSyntaxErrorException: Duplicate column name 'POPUP'
...
2016-01-08 22:13:50,811 WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): recordAlreadyExists: false, failQuiet: true, : error code: 1146, sql: ALTER TABLE CONTENT_RESOURCE ADD (RESOURCE_UUID VARCHAR (36)), binds: , error: java.sql.SQLSyntaxErrorException: Table 'sakai.CONTENT_RESOURCE' doesn't exist
2016-01-08 22:13:50,814 WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbRead: sql: show columns from CONTENT_RESOURCE like 'FILE_SIZE'
java.sql.SQLSyntaxErrorException: Table 'sakai.CONTENT_RESOURCE' doesn't exist

And then lots of "Table doesn't exist' and "Table already exists" WARN messages

and then a lot of these:
2016-01-08 22:13:50,822 ERROR localhost-startStop-1 org.sakaiproject.content.impl.DbContentService -
The filesize column doesn't exit. Please make sure you ran the 2.4-2.5 DB Conversion
––––––––––––––––––––––––––––––––––––
Tomcat runs fine, but sakai (/portal) fails:
HTTP Status 500 - Servlet.init() for servlet sakai.portal.charon threw exception

type Exception report
message Servlet.init() for servlet sakai.portal.charon threw exception
description The server encountered an internal error that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet.init() for servlet sakai.portal.charon threw exception
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:745)
root cause
java.lang.NullPointerException
org.sakaiproject.portal.charon.SkinnableCharonPortal.init(SkinnableCharonPortal.java:2028)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:745)

Startup & log file:
https://www.filesanywhere.com/fs/v.aspx?v=8b7065895f6171b8a597

I guess I'll revert to a standard mysql drive, since mariadb is not official for 10.5 - yes?

-------------------------------------------
From: Matthew Jones [mailto:mat...@longsight.com]

Sent: Wednesday, January 06, 2016 8:56 AM
To: Matthew Buckett
Cc: Gregory Guthrie; Brian Baillargeon; saka...@apereo.org

Subject: Re: [sakai-dev] Sakai-10 binary install

[Neal Caidin]

Hi Greg,

Yes, you do need to create an empty database and grant permissions to a non-root account. Then you need to match your configuration in sakai.properties so that it has the database name, sakai user (to whom you granted lots of permissions), and the sakai user's password.

When the system starts up, it connects with the database and automatically creates the database schema and all the data necessary to get started. Am I answering your question?

Near the bottom of the page, I see the instructions to create a sakai database. You don't have to name the database sakai, and the sakaiuser and password can also be different.  You just need to make sure your properties match.

mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 272
Server version: 5.1.46 MySQL Community Server (GPL)

Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v2 license

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> create database sakai default character set utf8;
Query OK, 1 row affected (0.00 sec)

mysql> grant all on sakai.* to sakaiuser@'localhost' identified by 'sakaipassword';
Query OK, 0 rows affected (0.00 sec

mysql> grant all on sakai.* to sakaiuser@'127.0.0.1' identified by 'sakaipassword';
Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

mysql> quit

Not sure if that helps.

I don't know the answer to your maria vs mysql driver question.

-- Neal

[Gregory Guthrie]

Thanks.

 

I still don’t see any “create your database” instruction in the binary-install page, but now know that it is needed, and where to go for that guide and how to do it.

 

I think I did follow all the points and issues on that page which you mention, and so would have expected that it should all work. (!)

 

I did not disable autlddl on second runs, so that might have caused some warnings, but should not be fatal I think.

 

I was hoping that some of the errors I was getting would be recognizable, and point to a solution.

 

We have done some other local installs, using Centos, and an older version of tomcat (.55), but are trying to update our procedures and installation.

 

Thanks for the note and help.

 

 

-------------------------------------------
From: Neal Caidin [mailto:neal....@apereo.org]
Sent: Saturday, January 09, 2016 2:01 PM
To: Gregory Guthrie
Cc: Matthew Jones; Matthew Buckett; saka...@apereo.org

[Neal Caidin]

Sorry I couldn't be of more help.

-- Neal

[Matthew Jones]

It looks like some of those WARN's were because of an older 10.x fix and also because of an issue with the MariaDB driver. Others might just be missing merges from trunk. This should be cleaned up a bit more for Sakai 10.7.

As far as the driver, we use the MariaDB driver on the nightly servers (Against a MySQL server) and I use the MariaDB driver locally against a MariaDB database (10.0.22-MariaDB-0ubuntu0.15.10.1) and both seem to work great. The latest driver (1.3.3) works better than the one we had bundled with 10.x (1.2.2).

If you want to compare your logs to the ones on nightly, that's sometimes a good idea. You can at least see if you have the same "non-fatal" errors. (Tomcat logs link for the type of instance/database you're running) 

http://nightly2.sakaiproject.org/

All I can see from these logs is it's able to create some tables and fails when creating others and then the whole process fails. Some of the old Sakai code, what it did was attempt to run the first line of the ddl script (like CREATE TABLE) and if it failed because it already existed, it should have remained quiet and just continued on, but it got really verbose.

Though in your case it's fine when it says the CONTENT_COLLECTION table already exists (because that's the first like of the sakai_content.sql ddl), but not so fine when it says the CONTENT_RESOURCE doesn't exist. (Because that should have also been created on the very first run after this table) 

So something messed up for you on your first run on a clean database that is preventing future startups. You'd have to go back to see what happened with this first run or try to start again with a clean database. Maybe the user didn't have the correct permissions?

2016-01-08 22:13:50,370  WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): recordAlreadyExists: false, failQuiet: true, : error code: 1050, sql:  CREATE TABLE CONTENT_COLLECTION ( COLLECTION_ID VARCHAR (255) NOT NULL, IN_COLLECTION VARCHAR (255), XML LONGTEXT, BINARY_ENTITY BLOB ), binds: , error: java.sql.SQLSyntaxErrorException: Table 'CONTENT_COLLECTION' already exists

2016-01-08 22:13:50,811  WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): recordAlreadyExists: false, failQuiet: true, : error code: 1146, sql:  ALTER TABLE CONTENT_RESOURCE ADD (RESOURCE_UUID VARCHAR (36)), binds: , error: java.sql.SQLSyntaxErrorException: Table 'sakai.CONTENT_RESOURCE' doesn't exist

[Gregory Guthrie]

Thank you for the info and analysis.

I did a complete database reset (delete, recreate) of the database, and a restart with autoddl, seems like the same problems.

========= Sakai Versions:: ====================
lrwxrwxrwx 1 root root 20 Jan 6 07:57 tomcat -> apache-tomcat-7.0.65
version.sakai=10.5
auto.ddl=true
driverC...@javax.sql.BaseDataSource=org.mariadb.jdbc.Driver
Linux theta 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64 GNU/Linux
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
mysql Ver 14.14 Distrib 5.5.46, for debian-linux-gnu (x86_64) using readline 6.3
tomcat/common/lib/mysql-connector-java-5.1.38-bin.jar
tomcat/common/lib/mariadb-java-client-1.3.3.jar
Tomcat runs fine, but /portal fails:

HTTP Status 500 - Servlet.init() for servlet sakai.portal.charon threw exception

________________________________________

Tomcat runs file, but /portal fails:

type Exception report
message Servlet.init() for servlet sakai.portal.charon threw exception
description The server encountered an internal error that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet.init() for servlet sakai.portal.charon threw exception
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)

org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:745)

I like your suggestion to compare to standard build logs;

The first one that looks serious is:
2016-01-10 16:46:02,426 WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): java.lang.NullPointerException
2016-01-10 16:46:02,428 WARN localhost-startStop-1 org.sakaiproject.content.impl.DbContentService - init():
java.lang.RuntimeException: SqlService.dbWrite failure

which in the build logs is:
2015-12-22 17:41:25,868 WARN localhost-startStop-1 org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): recordAlreadyExists: false, failQuiet: true, : error code: 1050, sql: CREATE TABLE SAKAI_ALIAS ( ALIAS_ID VARCHAR (99) NOT NULL, TARGET VARCHAR (255) NULL, CREATEDBY VARCHAR (99) NOT NULL, MODIFIEDBY VARCHAR (99) NOT NULL, CREATEDON DATETIME NOT NULL, MODIFIEDON TIMESTAMP NOT NULL ), binds: , error: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'SAKAI_ALIAS' already exists

And then later:
2016-01-10 16:46:06,259 INFO localhost-startStop-1 org.sakaiproject.metaobj.shared.mgt.impl.StructuredArtifactDefinitionManagerImpl - Updating base Metaobj XSLT files (auto.ddl is on).
2016-01-10 16:46:06,300 ERROR localhost-startStop-1 org.sakaiproject.metaobj.shared.mgt.impl.StructuredArtifactDefinitionManagerImpl - .createResource
java.lang.NullPointerException

which in the build logs is fine:
2015-12-22 17:41:29,771 INFO localhost-startStop-1 org.sakaiproject.metaobj.shared.mgt.impl.StructuredArtifactDefinitionManagerImpl - Updating base Metaobj XSLT files (auto.ddl is on).

And as you point out, loading CONTENT_RESOURCE gives an exception in mine, but just an INFO in the build logs.

None of these really mean much to me.

https://www.filesanywhere.com/fs/v.aspx?v=8b706589606774adadaf (13048 lines!)
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

From: Matthew Jones [mailto:mat...@longsight.com]

Sent: Sunday, January 10, 2016 12:01 PM
To: Neal Caidin
Cc: Gregory Guthrie; Matthew Buckett; saka...@apereo.org

Subject: Re: [sakai-dev] Sakai-10 binary install

[Matthew Jones]

Certainly an NPE should not be happening. Are you using the latest MariaDB driver? I just upgraded locally to 1.3.3 and it started up for me fine on MySQL. It should start up in the morning on nightly trunk. It as running 1.2.2 prior to that. 

at org.sakaiproject.db.impl.BasicSqlService.dbWriteCount(BasicSqlService.java:1299)

I don't know what line this errorcorresponds to. Are you using the 10.6 tag? 1299 in 10.x has nothing that could throw an NPE and that file hasn't changed since 2014.05-29. So I don't know what source you're using.

In 10.x that line is just

   throw new RuntimeException("SqlService.dbWrite failure", e);