This results from a change in template user after a user has previously logged in.

java.lang.NullPointerException
    at org.apache.tomcat.dbcp.dbcp.PoolingConnection.normalizeSQL(PoolingConnection.java:173)
    at org.apache.tomcat.dbcp.dbcp.PoolingConnection.createKey(PoolingConnection.java:165)
    at org.apache.tomcat.dbcp.dbcp.PoolingConnection.prepareStatement(PoolingConnection.java:87)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:185)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingD
    at org.jasig.portal.RDBMUserIdentityStore.updateUser(RDBMUserIdentityStore.java:647)
    at org.jasig.portal.RDBMUserIdentityStore.__getPortalUID(RDBMUserIdentityStore.java:318)
    at org.jasig.portal.RDBMUserIdentityStore.getPortalUID(RDBMUserIdentityStore.java:291)
    at net.unicon.portal.common.PortalIdentityStoreImpl.getUserId(PortalIdentityStoreImpl.java:58)
    at net.unicon.academus.domain.lms.UserFactory.getUserId(UserFactory.java:1412)
    at net.unicon.portal.common.PersonDirectoryServiceImpl.getPerson(PersonDirectoryServiceImpl.java:124)
    at net.unicon.portal.common.PersonDirectoryServiceImpl.getPerson(PersonDirectoryServiceImpl.java:140)

The culprit is the creation of an emtpy prepared statement on line 647. The insert statement hasn't yet been defined at that point. The fix is to move the insert variable declaration just above line 647.