wojciech.kapcia@tigase.net opened 1 decade ago
|
|
Applied in changeset tigase-pubsub|commit:1cb538353ec1640b408f39be6e498333f715c6be. |
|
I fixed schema, at least it worked correctly for me now, but schema for DerbyDB also did not report any errors before on my installation, which is weird. |
|
More issues with schema:
|
|
Applied in changeset tigase-pubsub|commit:103ac1f7b8e4529d67d2c3ae3c83833c74536d0f. |
|
MySQL issues, in (but not limited to):
_serviceJid instead of _service_jid |
|
Applied in changeset tigase-pubsub|commit:b466aa15130ff404e9f00afbce1673bc8d11db4d. |
|
Reported here: https://projects.tigase.org/boards/9/topics/4823?r=4921#message-4921 Installation is ok, but after startup Tigase shut down with:
|
|
As for issue with PosgreSQL schema, I checked and all is working fine if Tigase XMPP Server uses same user for database schema creation and later usage. In case if database schema is created with other user than user used later by Tigase XMPP Server this issue appears, as due to insufficient permissions default Tigase database user cannot execute procedure used verify if database contains proper version of schema. It is hard to tell how to fix it (I'm open on suggestions) but I think that we should print exception which causes Tigase XMPP Server to shutdown, so it would be easier for everyone to understand cause of this situation. Do you agree or have other suggestions? |
|
Andrzej Wójcik wrote:
This is with the default installation:
Yields in logs after startup:
Printing exception is definitely a good idea. |
|
Applied same change to the IzPack installer. |
|
Referenced from commit 1 year ago
|
Type |
Bug
|
Priority |
Blocker
|
Assignee | |
RedmineID |
1700
|
Spent time |
2h 45m
|
While loading schemas:
Derby:
SQL Server:
MySQL
no issue
Postgresql
Reported here: https://projects.tigase.org/boards/9/topics/4823?r=4921#message-4921
Installation is ok, but after startup Tigase shut down with: