|
Vijay Kaimal opened 9 years ago
|
|
Tigase XMPP Server do not support XEP-0313 Message Archiving Management only XEP-0136 Message Archiving I checked and wrapper.conf do not have entries to load Message Archiving component jar, so it will not work. %wojtek - maybe we should somehow generate this file instead of having static version in repository? so it would autoupdate during compilation/packaging? |
|
Andrzej Wójcik wrote:
As discussed in #3735#note-3 - I've proposed using wildcards (I've briefly tested it and it worked for me) but %daniel said it has some issues. I think it would be most convenient approach. |
|
Tanuki wrapper does support wildcards natively now(with the upgraded version), so we can use that. Condensing the java.classpath list to the following wrapper.java.classpath.1=jars/wrapper.jar wrapper.java.classpath.2=jars/*.jar Wrapper must have wrapper.jar specified as a single classpath. However, I run into the following error |
|
|
This issue could be caused by old version of Groovy (old version of As for now I suppose that there might be issue with order of classpath, ie. if Tigase HTTP API jar is loaded before groovy-all.jar then maybe it is not possible for HTTP API to use classes from groovy-all.jar? but I do not know how this wrapper actually work and I do not have Windows machine to check. %daniel - could you check if following list of classpaths in wrapper.conf file will help? This way we would force loading |
|
|
%kobit - please check http://wrapper.tanukisoftware.com/doc/english/licenseOverview.html for licensing options as I look on this we may not be able to use this wrapper for -dist builds as not all code is open sourced. |
|
|
%andrzej.wojcik the configuration listing you gave yields the same error, I'm including some more information prior to the error if it might help, I'm going to experiment with settings in the meantime. |
|
|
%wojtek I've tried a number of settings and configurations for loading Tigase VIA wrapper, but any time a wildcard is invoked, it results in the same error when loading pubsub component. Even if the tigase-pubsub.jar is specifically listed in the wrapper.conf the, I still get the same error when pubsub component is loaded. I'm not sure if the calls to groovy files are relative (i.e. uses the call to tigase-pubsub.jar as the reference point). Loading order seems to not effect changes either as renaming jar files using numbers yielded no changes. We have two options to proceed I think:
|
|
|
Daniel Wisnewski wrote:
Which updated version? Why? I've tried latest nightly installer: Then I've opened Can you check, that you have groovy libraries in the |
|
|
Wojciech Kapcia wrote:
Older versions of Tigase had Tanuki wrapper v2.7.1, wildcards were not supported until v3.3.8 which is now enabled since we last updated in #3449
I repeated the same actions as you on two windows machines, however I still got that error. groovy-all.jar is in the jars directory (are any others required for groovy?), and using the currently configured wrapper.conf file, the servers start up. Configuration-wise defaults except for enabling HTTP API, and using derbyDB. MySQL shows the same error. (I don't think the issue is DB related). |
|
|
Daniel Wisnewski wrote:
OK, I'm sticking with what we are distributing.
OK, I've done 'next-next-next' installation, changed the I think that as a last resort we could have an online session.... |
|
|
Both copies are Windows 7 x64 (one running on a clean environment in vmware), Java is Oracle JDK v8u65 (x86) File list: I also tried the same installation on a 3rd machine, Windows 7 x64, Oracle JDK v8_u51 x64 with the same result. Again in all machines if the jar files were specified without using wildcards, no issues. |
|
|
Daniel Wisnewski wrote:
I've tried Windows Server 2012 and Windows 10tp2, both x64 but I doubt this could make such big difference.
I've noticed there is some problem with the wrapper while using x64 JDK. |
|
|
OK, it turned out that the problem was cause by the older version of |
|
|
New build works OK with wildcards, and all included components are functional. Vijay, please give a try to latest build 4128 or later and let us know if it works for you. |
|
No feedback, assuming it is working now. |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
3800
|
| Version |
tigase-server-7.1.0
|
| Spent time |
30h
|
Base Bug : Bug #3735
Description :
When running XMPP server as windows service, tables for XEP-0313: Message Archive Management are not created (tig_ma_jids,tig_ma_msgs, tig_ma_msgs_tags,tig_ma_tags) and archive management is not working.
Everything seems to work fine when running in console mode.
I am using the nightly build from Dec 10,2016 as suggested in the Base bug.