-
I finished fixing this issue. I needed to implement only few things to add support for MongoDB but I needed to do a lot of refactoring. Source code is ready in repositories and future nightly build should contain this fixes. Fixes are in Tigase XMPP Server project and in Tigase MongoDB project.
-
Andrzej, I've copied the most recent jars from jenkins: tigase-server.jar, and tigase-issue #1.0.0-SNAPSHOT.jar. Is it okay to drop those into the jars/ directory of b3669 or should I wait for a complete package... are there other dependencies?
2014-09-16 15:59:26.697 [default-threads-pool Queue Worker 1] WorkerThread.run() SEVERE: tigase.server.xmppsession.SessionManager$ProcessorWorkerThread,(default-threads-pool Queue Worker 1) Exception during packet processing: from=c2s@build.xmpp-test.net/127.0.0.1_5222_127.0.0.1_34453, to=sess-man@build.xmpp-test.net, DATA=<iq type="set" id="reg2" xmlns="jabber:client"><query xmlns="jabber:iq:register"><username>admin</username><password>stats</password><email>test_user@localhost</email></query></iq>, SIZE=180, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=set java.lang.ArithmeticException: / by zero at tigase.db.DataRepositoryPool.takeRepo(DataRepositoryPool.java:75) at tigase.db.DataRepositoryPool.getPreparedStatement(DataRepositoryPool.java:176) at tigase.db.DataRepositoryPool.getPreparedStatement(DataRepositoryPool.java:179) at tigase.db.jdbc.TigaseCustomAuth.addUser(TigaseCustomAuth.java:347) at tigase.db.AuthRepositoryMDImpl.addUser(AuthRepositoryMDImpl.java:82) at tigase.xmpp.RepositoryAccess.register(RepositoryAccess.java:473) at tigase.xmpp.impl.JabberIqRegister.process(JabberIqRegister.java:312) at tigase.server.xmppsession.SessionManager$ProcessorWorkerThread.process(SessionManager.java:2772) at tigase.util.WorkerThread.run(WorkerThread.java:132)
-
I think that dropping new versions of Tigase XMPP Server and Tigase MongoDB into old build should work, but I already know that current nightly was broken due to issue in Tigase HTTP API.
This exception which you received I suppose is due to
--auth-db
entry inetc/init.properties@. It should be omitted to make sure that Tigase XMPP Server will choose correct implementation of @AuthRepository
for MongoDB. -
Andrzej, Everything seems to be working fine now just the pubsub tests are failing consistently. Also Multi 6, and Privacy 1:
http://graph.cluster-c.xmpp-test.net/5.3.0-SNAPSHOT-b3674/func/mongodb/functional-tests.html
http://graph.cluster-c.xmpp-test.net/5.3.0-SNAPSHOT-b3674/lmem/mongodb/low-memory-tests.html
-
I looked in logs and I have seen that PubSub tests failed due to construction of requests I used when implementing support for MongoDB as I used newest stable version of MongoDB and new features introduced in it. In tests MongoDB 2.0.4 was used while I was developing support using MongoDB 2.6.3.
I suppose we can force usage of MongoDB at least in 2.6.3 version as it is stable now and we are adding support for MongoDB as a new feature to upcoming version. So I suppose we should rerun this tests using MongoDB 2.6.3. I will add a note on Tigase MongoDB project which states that to use it we require MongoDB at least in version 2.6.3 (my bad that I did not added this info before).
Moreover I think we have issue with
Privacy
tests as they send<iq id="privacy_9" xmlns="jabber:client" from="multi-reg_5_3@test-d/def-user-resource" type="set"><query xmlns="jabber:iq:privacy"><default/></query></iq>
while according to current code of Tigase XMPP Server
<default/>
element should contain name of list as CData (value of element).%kobit - could you check if I'm right about this issue with Privacy tests?
-
-
I do not see a problem with requiring MongoDB version 2.6.3 or later.
-
I am assigning this to Wojciech as he worked on the privacy lists some time ago. It is very likely the Tigase code was updated and tests were not.
Wojciech, please review the issue with privacy lists.
-
-
Artur Hefczyc wrote:
I am assigning this to Wojciech as he worked on the privacy lists some time ago. It is very likely the Tigase code was updated and tests were not.
Wojciech, please review the issue with privacy lists.
Those are the same tests run against other DBs and the tests pass just fine, see any results from http://build.tigase.org/nightlies/tests/, hence it seems issue is not related to Privacy Lists code or test run against it.
while according to current code of Tigase XMPP Server element should contain name of list as CData (value of element).
Actually it's not - it follows specs and name of the default list should be taken from
name
attribute of<default/>
element - not CData, but this attribute is optional and if such is not present then client simply declines use of default list.After digging deeper it looks like there may be a problem with
tigase.db.UserRepository.getSubnodes()
method in MongoDB repository implementation.
Type |
Task
|
Priority |
Normal
|
Assignee | |
RedmineID |
2252
|
Blocking: Automated TTS tests on MongoDB