You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Adam Saghy (Jira)" <ji...@apache.org> on 2026/01/04 20:46:00 UTC

[jira] [Closed] (FINERACT-1895) Fineract doesn't start with spring profile activeMqEnabled

     [ https://issues.apache.org/jira/browse/FINERACT-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Saghy closed FINERACT-1895.
--------------------------------
    Resolution: Cannot Reproduce

> Fineract doesn't start with spring profile activeMqEnabled
> ----------------------------------------------------------
>
>                 Key: FINERACT-1895
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1895
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: System
>            Reporter: Hitesh Prajapati
>            Priority: Minor
>
> When I run fineract with activeMqEnabled profile, it doesn't start and failed with below excpetion. I have standalone ActiveMQ running with default port. so the MessagingConfiguration should work with it.
> java -Dspring.profiles.active=activeMqEnabled -jar fineract-provider/build/libs/fineract-provider-0.0.0-6c86e15e.jar
> {code:java}
> Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
> 2023-04-08 19:45:48.484 -ERROR 11140  --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   :***************************
> APPLICATION FAILED TO START
> ***************************Description:The dependencies of some of the beans in the application context form a cycle:   tenantAwareBasicAuthenticationFilterRegistration defined in class path resource [org/apache/fineract/infrastructure/core/config/SecurityConfig.class]
>       ?
>    tenantAwareBasicAuthenticationFilter (field private org.apache.fineract.notification.service.UserNotificationService org.apache.fineract.infrastructure.security.filter.TenantAwareBasicAuthenticationFilter.userNotificationService)
> ???????
> |  userNotificationServiceImpl defined in URL [jar:file:/D:/Work/fineract/source/fineract/fineract-provider/build/libs/fineract-provider-0.0.0-185551c5.jar!/BOOT-INF/classes!/org/apache/fineract/notification/service/UserNotificationServiceImpl.class]
> ?     ?
> |  activeMQNotificationEventPublisher defined in URL [jar:file:/D:/Work/fineract/source/fineract/fineract-provider/build/libs/fineract-provider-0.0.0-185551c5.jar!/BOOT-INF/classes!/org/apache/fineract/notification/eventandlistener/ActiveMQNotificationEventPublisher.class]
> ?     ?
> |  messagingConfiguration (field private org.apache.fineract.notification.eventandlistener.NotificationEventListener org.apache.fineract.notification.config.MessagingConfiguration.notificationEventListener)
> ?     ?
> |  notificationEventListener defined in URL [jar:file:/D:/Work/fineract/source/fineract/fineract-provider/build/libs/fineract-provider-0.0.0-185551c5.jar!/BOOT-INF/classes!/org/apache/fineract/notification/eventandlistener/NotificationEventListener.class]
> ???????
> Action:Relying upon circular references is discouraged and they are prohibited by default. Update your application to remove the dependency cycle between beans. As a last resort, it may be possible to break the cycle automatically by setting spring.main.allow-circular-references to true.{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)