[ 
https://issues.apache.org/jira/browse/FINERACT-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217793#comment-17217793
 ] 

Michael Vorburger commented on FINERACT-1228:
---------------------------------------------

Closing as WONTFIX, as we won't pursue FINERACT-931.

> java.lang.ClassCastException: class 
> org.apache.fineract.useradministration.domain.AppUser cannot be cast to class 
> org.apache.fineract.useradministration.domain.AppUser
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1228
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1228
>             Project: Apache Fineract
>          Issue Type: Bug
>            Reporter: Michael Vorburger
>            Priority: Major
>
> While playing with FINERACT-931, I've encountered:
> {{java.lang.ClassCastException: class 
> org.apache.fineract.useradministration.domain.AppUser cannot be cast to class 
> org.apache.fineract.useradministration.domain.AppUser 
> (org.apache.fineract.useradministration.domain.AppUser is in unnamed module 
> of loader 'app'; org.apache.fineract.useradministration.domain.AppUser is in 
> unnamed module of loader 
> org.springframework.boot.devtools.restart.classloader.RestartClassLoader 
> @7c4ff5b3)}}
> This seems to be caused by the scheduler somehow "hanging on" to a a domain 
> class.
> It's not blocking FINERACT-931, just means that the Spring Boot DevTools 
> Automatic Restart won't work for the Scheduler. Someone who enjoy a good 
> session of ClassLoader fun could dig into fixing this.
> Affects Dev only, will not happen in production.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to