Strange PermGen out of memory error - Shib IdP V3

[Stefan Santesson]

I tried to change to BeanManagedConnection.

I used the example from the Wiki:
https://wiki.shibboleth.net/confluence/display/IDP30/BeanManagedConnection

I had to add commons-dbcp-1.4.jar to the lib.
I added the bean declaration in global.xml.

I get an error trying to start the IdP, saying that the drivarClass
property is not writable:

Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
property 'driverClass' of bean class
[org.apache.commons.dbcp.BasicDataSource]: Bean property 'driverClass' is
not writable or has an invalid setter method. Does the parameter type of
the setter match the return type of the getter?
	at 
org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.
java:1076) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at 
org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.
java:927) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at 
org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(Abstra
ctPropertyAccessor.java:95) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at 
org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(Abstra
ctPropertyAccessor.java:75) ~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]
	at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactor
y.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1502)
~[spring-beans-4.1.5.RELEASE.jar:4.1.5.RELEASE]


/Stefan



On 12/07/15 02:55, "users on behalf of Cantor, Scott"
<users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

>On 7/11/15, 8:30 PM, "users on behalf of Stefan Santesson"
><users-bounces at shibboleth.net on behalf of stefan at aaa-sec.com> wrote:
>
>>Hi,
>>
>>I wander if anyone recognise this problem.
>
>c3p0 has known memory leaks, which means the ApplicationManagedConnection
>pooling in the resolver does.
>
>You should get off it at the earliest opportunity, and you definitely
>don't want to be using it for load testing. The recommended strategy is
>BeanManagedConnection, but you can use a ContainerManagedConnection if
>you prefer, that's more work though, involving changes to web.xml.
>
>-- Scott
>
>-- 
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net