You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/10/11 15:52:00 UTC
[jira] [Commented] (FINERACT-1193) activeMq error log at startup,
while not a strict requirement ?
[ https://issues.apache.org/jira/browse/FINERACT-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211953#comment-17211953 ]
Michael Vorburger commented on FINERACT-1193:
---------------------------------------------
I can confirm the approach and state that a Pull Request with a proposed fix as you outline it would be most welcome! :D
> activeMq error log at startup, while not a strict requirement ?
> ----------------------------------------------------------------
>
> Key: FINERACT-1193
> URL: https://issues.apache.org/jira/browse/FINERACT-1193
> Project: Apache Fineract
> Issue Type: Improvement
> Components: System
> Affects Versions: 1.4.0
> Reporter: Vincent FUCHS
> Priority: Minor
>
> Hi,
> When starting Fineract according to the documentation, I get an error in the logs regarding ActiveMQ not being available. But the application starts nonetheless.
>
> The documentation doesn't mention the need for a messaging system (unlike th enedd for mySql DB) - I guess it's optional ?
>
> Then, shouldn't MessagingConfiguration be enabled only when a certain Spring profile is applied at startup ? This would avoid loading messaging related Spring beans, and getting a puzzling error message at startup.
>
> If somebody can confirm the approach to take, I can try to "fix" this.
>
> Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)