|
tom quas opened 1 decade ago
|
|
MUC needs history provider! In other case MUC is not able to send few latest messages to new occupant! Edit your init.properties and use this instead: |
|
|
hmm, i don't want any history at all. plus, with the loss of the muc-max-history-size patch of ticket #161 there's currently no way to turn it off – no, it's no longer in the code. i'm back where i've been over a year ago. |
|
|
Option to disable history: |
| Type |
New Feature
|
| Priority |
Minor
|
| Assignee | |
| RedmineID |
872
|
| Version |
tigase-muc-2.2.0
|
Issue Votes (0)
Watchers (0)
actual: when run as an external component for an SM which has clustering turned on, MUC sets tigase.muc.JDBCRepository as default for history if muc/history-db has not been set in the properties. this comes with a huge performance penalty.
expected: by default, MUC should set a NullHistoryProvider which does nothing. users who need MUC history should enable it.
note: assigned criticality critical because my MUC component processes started putting lots of load on my machines