> Feel free to include me (or let me know how to include myself) in release
> candidate testing.
It's really a matter of simply taking initiative to test your overlays
against release candidates when we announce them. If you're on
cas-user, you should see the announcements.
I appreciate your wi
.6419jgas...@ewu.eduwww.ewu.edu
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Wednesday, November 09, 2011 11:41 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] 3.4.11 Null Pointer in Login
> I came across https://issues.jasig.org/browse/C
> I came across https://issues.jasig.org/browse/CAS-930. The last comment by
> Marvin indicates that the JdbcLockingStrategy should be deprecated.
It is indeed deprecated:
https://github.com/Jasig/cas/blob/master/cas-server-core/src/main/java/org/jasig/cas/ticket/registry/support/JdbcLockingStrat
My question was, although maybe not clearly articulated, does it make sense
> to switch that too?
>
> John
>
>
> -Original Message-
> From: Vitty, Paul [mailto:p.vi...@ulster.ac.uk]
> Sent: Wednesday, November 09, 2011 10:00 AM
> To: cas-user@lists.jasig.org
> Su
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] 3.4.11 Null Pointer in Login
Hi John,
If you follow the updated wiki instructions it works perfectly. All my
integration tests passed.
Thanks
Paul Vitty
Apache/MySQL Web Platform Engineer
Application Platform Delivery
Information Services
arvin.addi...@gmail.com]
> Sent: Wednesday, November 09, 2011 9:38 AM
> To: cas-user@lists.jasig.org
> Subject: Re: [cas-user] 3.4.11 Null Pointer in Login
>
>> Adding > class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"
>> /> t
g.org/display/CASUM/JpaTicketRegistry.
Thanks,
John
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Wednesday, November 09, 2011 9:38 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] 3.4.11 Null Pointer in Login
> Addin
> Adding class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"
> /> to the ticketRegistry.xml resolves the issue and appears to ensure that
> the entityManager is wired up.
That's absolutely right. It's sitting right there in my overlay and I
simply forgot that confi
Marvin,
I believe I may have solved the issue, for some reason PersistenceContext is
not being set via annotation
https://github.com/Jasig/cas/blob/v3.4.11/cas-server-core/src/main/java/org/jasig/cas/ticket/registry/JpaTicketRegistry.java#L38
so the entityManager is null causing the null pointe
Thanks for getting back to me Marvin. I'd be more than willing to QA our JPA
overlay in the future.
Thanks
Paul
On 9 Nov 2011, at 16:28, Marvin Addison wrote:
>> I've modified the vanilla cas-server-webapp to reproduce the issue,
>> see:
>> https://github.com/pvitty/cas/commit/d28f811ccd02eb8
> I've modified the vanilla cas-server-webapp to reproduce the issue,
> see: https://github.com/pvitty/cas/commit/d28f811ccd02eb838a4de17f0a056bb5c410add2 for
> details. It creates the database tables correctly but still throws the
> errors above, you can use mvn integration-test jetty::run to repr
I have tried without auditing and there is no more information in the log
output.
With all log levels up to DEBUG:
2011-11-09 14:38:24,628 DEBUG
[org.springframework.transaction.annotation.AnnotationTransactionAttributeSource]
-
2011-11-09 14:38:24,628 DEBUG
[org.springframework.orm.jpa.JpaT
> I switched log4j up to debug, the area that seems to be causing the issue is:
>
> 2011-11-09 02:21:49,422 DEBUG
> [org.springframework.transaction.annotation.AnnotationTransactionAttributeSource]
> - [PROPAGATION_REQUIRED,ISOLATION_DEFAULT]>
> 2011-11-09 02:21:49,422 DEBUG
> [org.springfram
The only major difference I see is that @Transactional annotations got
added (which I didn't realize or somehow missed). Any thoughts, Marvin?
On Tue, Nov 8, 2011 at 9:24 PM, Vitty, Paul wrote:
> Hi Scott,
>
> I've narrowed it down to be something to do with JpaTicketRegistry. If I
> change
Hi Scott,
I've narrowed it down to be something to do with JpaTicketRegistry. If I change
my ticket registry to be the default ticket registry, everything works ok, but
if I try to use the JpaTicketRegistry it fails.
I switched log4j up to debug, the area that seems to be causing the issue is:
As a test, can you try to see if login succeeds with auditing disabled?
(just trying to narrow down the problem).
On Tue, Nov 8, 2011 at 8:45 PM, Vitty, Paul wrote:
> Hi,
>
> Currently experiencing issues with 3.4.11 when attempting to log in. As
> you can see, the WHAT section of Inspektr log
16 matches
Mail list logo
