Shibboleth Developers

[Jim Fox <>]

It seems to be a known issue that the postgres jdbc library distributed 
with our java (1.6) doesn't support setQueryTimeout()

Setting the timeout to zero bypasses this issue.

Otherwise it is working fine.  I haven't seen any of the ldap delays that 
Russell encountered.

Jim


On Fri, 18 Jun 2010, Jim Fox wrote:

> Date: Fri, 18 Jun 2010 14:17:02 -0700
> From: Jim Fox 
> <>
> To: 
> ""
>  
> <>
> Reply-To: 
> ""
>  
> <>
> Subject: Re: [Shib-Dev] New IdP v2.2 Snapshot Available
>
>
> > Turn on debug logging for org.opensaml.saml2.metadata and see what it says.
>
> It appeared to be caused by missing saml2 endpoints in the metadata.  Just
> misleading messages.
>
>
> When I try to access a postgres DB for tgtid info I get:
>
>    ....RDBMSDataConnector:335] - RDBMS data connector
>      [tgtidDB2, select tid('6BB477326A7C11D5A4AE0004AC494FFE', 
> 'https://urizen2.cac.washington.edu/'), 0A000, 0]
>       Unable to execute SQL query org.postgresql.util.PSQLException:
>    Method org.postgresql.jdbc3.Jdbc3Statement.setQueryTimeout(int) is not yet
>    implemented.; SQL State: {}, SQL Code: {}
>
> I can run the select command from psql successfully.
>
> Jim