java.lang.NullPointerException

Apereo Issues | Nick Bolton | 9 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    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.

    Apereo Issues | 9 years ago | Nick Bolton
    java.lang.NullPointerException
  2. 0

    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.

    Apereo Issues | 9 years ago | Nick Bolton
    java.lang.NullPointerException

    Root Cause Analysis

    1. java.lang.NullPointerException

      No message provided

      at org.apache.tomcat.dbcp.dbcp.PoolingConnection.normalizeSQL()
    2. org.apache.tomcat
      DelegatingConnection.prepareStatement
      1. org.apache.tomcat.dbcp.dbcp.PoolingConnection.normalizeSQL(PoolingConnection.java:173)
      2. org.apache.tomcat.dbcp.dbcp.PoolingConnection.createKey(PoolingConnection.java:165)
      3. org.apache.tomcat.dbcp.dbcp.PoolingConnection.prepareStatement(PoolingConnection.java:87)
      4. org.apache.tomcat.dbcp.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:185)
      4 frames