Can't initialise MAM processor with default installation (#1251)

Wojciech Kapcia (Tigase) opened 4 years ago

8.2.0-SNAPSHOT-b11367
derby
defaults in the installer:

[2021-04-23 16:47:41:070] [WARNING ] [                  main ] Kernel.injectDependencies()      :


=====================
Could not initialize bean urn:xmpp:mam:2 (class: class tigase.archive.processors.MAM2Processor), skipping injection of this bean
RootCause:
   -> tigase.kernel.KernelException: Can't inject <null> to field tigase.archive.processors.AbstractMAMProcessor.messageArchivePlugin
      [tigase.kernel.core.Kernel.inject(Kernel.java:1190)]
=====================

Activities

Wojciech Kapcia (Tigase) commented 4 years ago

wojtek@atlantiscity.local ~/dev/tmps/tigase-server-dists/tigase-issue #8.2.0-SNAPSHOT-b11367 $ cat etc/config.tdsl
admins = [
    'admin@atlantiscity'
]
'config-type' = 'default'
debug = [ 'server' ]
'default-virtual-host' = 'atlantiscity'
dataSource () {
    default () {
        uri = 'jdbc:derby:tigasedb;create=true'
    }
}
http () {}
'message-archive' (active: false) {}
pubsub () {
    trusted = [ 'http@{clusterNode}' ]
}
'sess-man' () {
    'urn:xmpp:mam:1' (active: false) {}
}

Andrzej Wójcik (Tigase) commented 4 years ago

I've fixed how default configuration is generated (to include MAM:2 and exclude disabled by default XEP-0136). I've also fixed MessageArchivePlugin to "enable" itself when only MAM:2 is enabled. That should fix the issue and make it work in all possible configuration options.
Wojciech Kapcia (Tigase) commented 4 years ago

It works.
Login to comment

Type	Bug
Priority	Normal
Assignee	Wojciech Kapcia (Tigase)
Version	tigase-server-8.2.0
Spent time	0

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#1251