|
wojciech.kapcia@tigase.net opened 1 decade ago
|
||||||
|
Eric, please verify that this configuration works. There should be some documentation on how to setup this but it may be outdated. Please update the docs if necessary. |
||||||
|
This does work in cluster mode. Docs seem correct --ext-comp is deprecated. http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#extComp http://docs.tigase.org/tigase-server/snapshot/Properties_Guide/html/#external |
||||||
|
|
Eric, we are not talking about the cluster mode. We are talking about non-clustered Tigase but with connection managers separate from SessionManager. This is more or less common use-case when you want to have parts of the system which keep critical data (database, SessionManager) in protected network (DMZ), while allowing for connectivity from the internet - connection managers. In theory it should work as it was designed that way. But the last time I checked that configuration was maybe 5 or more years ago. A lot has changed since than and I am no longer sure if Tigase works that way. Therefore, please deploy Tigase in a following way:
While you do this, please document all the configuration details so at the end of the task (assuming it is possible to run it that way) we have ready to use step-by-step guide. |
||||||
|
|
Doesn't seem to work. Maybe I am doing something wrong. Here is what I did... Running with --gen-config-sm on tpub.xmpp-test.net init.properties: I've tried "listen" and "accept" on --external, don't see a difference. The open ports look to be correct: No exceptions in the logs, no mention of connection manager trying to connect. For connection manager I'm using t4.tigase.org. init.properties: I don't see mention of trying to connect to tpub in logfiles. Tried with and without --bind-ext-hostnames. I know I will have to add the rest of the components but for now this should connect SessionManager. I see exceptions of this instance trying to connect to Derby DB. I removed DB "DRV" line from tigase.conf and it still happens. The log keeps repeating the following every 2 seconds: Changing init.properties to config-type=--gen-config-comp and adding muc component results in same Derby DB errors and this every 2 seconds: I am following instructions at these URLs http://docs.tigase.org/tigase-server/5.2.2/properties_guide/webhelp/configType.html http://docs.tigase.org/tigase-server/5.2.0/admin_guide/html_chunk/_configuration_wizards.html http://docs.tigase.org/tigase-server/5.2.2/properties_guide/webhelp/external.html |
||||||
|
|
Wojciech, please verify the setup is possible at all in our current code. It does not have to use --gen-config-cs, --gen-config-sm. It may use any configuration combination that actually works. Please dedicate to this no more than 16 hours. If after this time you won't find a way, assign it back to me. |
||||||
|
|
I was able to have such setup working (with working muc as an example component): Please note, this still uses the old I've spend on this less then 16h limit (ca 3,5h) - should I spend remaining time on clarifying the documentation and/or rework it to use EDIT: configs for reference:
|
||||||
|
|
Yes, please continue on this task. The most important thing is a documentation which describes step-by-step how to setup such a configuration. Using ext.ComponentProtocol is not critical but if it is not a lot of work, it would be good to have it, so we could drop the old implementation in the future versions. Also, I think it is important that the SM server works in a cluster mode. This was not mentioned before, but this is what a customer would expect to have. CS server does not need to be in a cluster mode I think. |
||||||
|
Referenced from commit 6 months ago
|
|||||||
|
|
wojciech.kapcia@tigase.net batch edited 4 months ago
|
| Type |
Task
|
| Priority |
Minor
|
| Assignee | |
| RedmineID |
1478
|
| Version |
Candidate for next major release
|
| Spent time |
145h 30m
|
Iterations
Issue Votes (0)
Watchers (2)
verify that the setup works correctly (in cluster environment?)
verify that correct external component is used for the connection (--ext-comp vs --external)