[prev in list] [next in list] [prev in thread] [next in thread] 

List:       shibboleth-users
Subject:    Re: [Shib-Users] RDBMS NullPointerException
From:       Chad La Joie <lajoie () itumi ! biz>
Date:       2011-03-29 22:18:23
Message-ID: 4D925AAF.9080908 () itumi ! biz
[Download RAW message or body]

Okay so that error message is from the Mapped Attribute Definition, not
the RDBMS data connector.  So you'll need to file a bug against that.

On 3/29/11 2:25 PM, Russell Beall wrote:
> Ok.  Does that mean the DB connector is not meant to handle multi-valued data \
> items? 
> The actual error message is this:
> 17:21:57.358 DEBUG \
> [edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.attributeDefinition.ValueMap:98] \
> - Performing regular expression based comparison 17:21:57.384 ERROR \
> [edu.internet2.middleware.shibboleth.common.profile.ProfileRequestDispatcherServlet:88] \
>                 - Error occured while processing request
> java.lang.NullPointerException: null
> at edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.attributeDefinition.MappedAttributeDefinition.doResolve(MappedAttributeDefinition.java:68)
>  at edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.attributeDefinition.BaseAttributeDefinition.resolve(BaseAttributeDefinition.java:107)
>  
> This appears after successfully mapping two data items for a single attribute, but \
> the third row had null. 
> Russ.
> 
> On Mar 29, 2011, at 10:31 AM, Chad La Joie wrote:
> 
> > I'm not exactly clear what you were doing and where the regex you
> > mentioned comes in to play.
> > 
> > In general though, the DB connector I think expects you to return one
> > row per-user.
> > 
> > On 3/29/11 12:47 PM, Russell Beall wrote:
> > > I just hacked together a database of test users to replace my static data \
> > > connector in my test system.  I noticed that I got a NullPointerException when \
> > > the resolver was trying to parse a null value returned from the table read. 
> > > For instance, if I do the following:
> > > insert into testuser (accountname, singlevalueditem, multivalueditem) values \
> > > ('testuser', 'singlevalue', 'multivalue1'); insert into testuser (accountname, \
> > > multivalueditem) values ('testuser', 'multivalue2'); 
> > > There will be a null value returned for the single-valued item when the second \
> > > row matching that principal is read, and then a regex match is still attempted \
> > > but throws the exception. 
> > > Should I design this in a more normalized fashion with multiple tables and \
> > > separate dataconnectors for tables with multiple values, or was the above \
> > > supposed to work ok (albeit inelegantly)? 
> > > IdP 2.1.5
> > > jdk1.6.0_24
> > > 
> > > Thanks,
> > > Russ.
> > > 
> > > 
> > 
> > -- 
> > Chad La Joie
> > http://itumi.biz
> > trusted identities, delivered
> 
> 

-- 
Chad La Joie
http://itumi.biz
trusted identities, delivered


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic