I have found another detail I didn't see before. As a side effect of my having added the retrieval of person attributes from LDAP, the portal now has the template user name for user "admin" as "admin." Thinking that the admin user has not saved layout before, the templating logic kicks in the RDBMUserIdentityStore.__getPortalUID() method. Never mind that the templating would try to clone the layout for user "admin" from the template user "admin." I think that the issue may have nothing to do with the templating logic.
Adam Adam Rybicki wrote: > I think that I may have run into a bug, but being that I am not an > expert in this area, I'd like to ask the developers. > > I've configured uPortal 3.2.1 to support simple, LDAP, and CAS > authentication. When I try logging in as admin/admin, I get an > exception, which looks like this: > > Caused by: org.apache.commons.dbcp.SQLNestedException: Borrow > prepareStatement from pool failed > at > org.apache.commons.dbcp.PoolingConnection.prepareStatement(PoolingConnection.java:113) > at > org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:281) > at > org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:313) > at > org.jasig.portal.RDBMUserIdentityStore.updateUser(RDBMUserIdentityStore.java:730) > ... 37 more > Caused by: java.sql.SQLException: Column count does not match in > statement [INSERT INTO UP_USER_PROFILE (USER_ID, PROFILE_ID, > PROFILE_FNAME, PROFILE_NAME, DESCRIPTION, LAYOUT_ID, STRUCTURE_SS_ID, > THEME_SS_ID) VALUES(?, ?, ?, ?, NULL, ?, ?)] > at org.hsqldb.jdbc.Util.throwError(Unknown Source) > at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source) > at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source) > at > org.apache.commons.dbcp.PoolingConnection.makeObject(PoolingConnection.java:285) > at > org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1179) > at > org.apache.commons.dbcp.PoolingConnection.prepareStatement(PoolingConnection.java:107) > ... 40 more > > The SQL statement in RDBMUserIdentityStore declared on line 727 does > indeed look like the one reported in the exception, where the number of > parameters does not match the number of columns being inserted. > > Am I mis-diagnosing this? If this is something new, I'll be happy to > create a new JIRA issue. > > Thanks, > Adam > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
<<attachment: arybicki.vcf>>
