Tigase XMPP Server Board

API and development: RE: Problem with kicking occupant

Thu, 02/09/2017 - 06:58

Vlad Buryj wrote:

Anyone know where is problem?

It's hard to tell with hidden details but a couple of things to consider:
  • do you have correct affiliation with the room?
  • do you use correct addresses?
  • do you include FullJID in from?

Which Version of the Server and Component do you use?

Categories: Tigase Forums

Tigase server ad-hoc scripts: RE: Get user presence in cluster

Thu, 02/09/2017 - 06:51

Tue Topholm wrote:

Can you point me to one of the scripts, so I can copy it and modify it

For example following scripts will get executed on all nodes:

It's also possible to get basic user info from whole cluster but it requires ACS to provide cluster data: GetUserInfo.groovy

Categories: Tigase Forums

Installation and maintenance: Private Certificate

Thu, 02/09/2017 - 02:37

Couldn't understand how to use my own certificate with tigase?
I was:
Stop server
clean certs directory
put my file.pem
add to init.properties next lines
--ssl-container-class=tigase.io.SSLContextContainer
basic-conf/virt-hosts-cert-*.domain.com=/etc/tigase/certs/file.pem

start server.
But after this actions tigase generate himself cert with domain.com.pem and use it.
What's my mistake?
tig v.7.1.0

Categories: Tigase Forums

API and development: Problem with kicking occupant

Thu, 02/09/2017 - 00:54

I trying to kick occupant. For that i use
<iq from='/pda'
id='kick1'
to=''
type='set'>
<query xmlns='http://jabber.org/protocol/muc#admin'>
<item nick='pistol' role='none'>
<reason>Avaunt, you cullion!</reason>
</item>
</query>
</iq>

also I was trying use that
<iq type=‘set’ to=’ id=‘ban1’>
<query xmlns=‘http://jabber.org/protocol/muc#admin’/>
<item affiliation=‘outcast’ jid=’/>
</query>
</iq>

Tigase show

<iq type="error" id="32b9602c-2718-414f-90d0-af5716a9df64" from="" xmlns="jabber:client" to="">
<query xmlns="http://jabber.org/protocol/muc#admin"/>
<item affiliation="outcast" jid=""/>
<error type="modify" code="406"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>, SIZE=415, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=AUTH, TYPE=error

or

<iq type="error" id="32b9602c-2718-414f-90d0-af5716a9df64" from="" xmlns="jabber:client" to="">
<query xmlns="http://jabber.org/protocol/muc#admin"/>
<item affiliation="outcast" jid=""/>
<error type="modify" code="406"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>, SIZE=415, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=error

Anyone know where is problem?

Best regards Vlad

Categories: Tigase Forums

API and development: RE: tigase server(v7.1.0) and client(v3.0.0) incompatibility

Wed, 02/08/2017 - 17:06

Thank you Arthur for a quick, detailed response. We will wait for Andrzej's suggestion.

Categories: Tigase Forums

API and development: RE: tigase server(v7.1.0) and client(v3.0.0) incompatibility

Wed, 02/08/2017 - 16:24

Normally, if XMPP protocol is used there re no incompatibilities between different XMPP servers and XMPP clients, or different versions. This is because all our software implement all the standard XMPP specifications and public extensions.
However, you are not using an XMPP protocol. Instead, you use Websockets and there, indeed were significant changes in the Websockets implementation in both the Tigase server and our library. This is because when we started supporting Websockets connection, the websockets specification was not even finalized yet, so changes are related to changes in specification and also, there were many improvements in the web socket handling by our software.

Our Websocket expert who implemented the protocol on the server and client is on holiday this week and he is back next week. He might offer better suggestions that I can. My suggestions would be:
  1. Use XMPP protocol instead of Websockets if possible. Do you really need to use Websockets in your Android client? It is much less efficient than standard XMPP connection and mobile devices can easily handle standard XMPP connections, so they do not need to use HTTP or Websockets. Unless, of course, you have a very specific use-case.
  2. If you really must use Websockets, then the best option would be to upgrade the library as well, when you switch to the new Tigase XMPP Server version.
  3. Wait until Monday, maybe Andrzej who implemented websockets in our software would have other solution for you.
Categories: Tigase Forums

API and development: tigase server(v7.1.0) and client(v3.0.0) incompatibility

Wed, 02/08/2017 - 16:13

We are testing an upgrade from Tigase v5.2.3 to v7.1.0 and are running into some compatibility issues with the Tigase JaXMPP client library. Our android clients using v3.0.0 of the JaXMPP lib are unable to connect to Tigase v7.1.0. I'm going to paste the problem details as reported by one of our android developers below, after the question..

Is there a compatibility mode or a configuration parameter that we can set in v7.1.0 to make the client v3.0.0 work? Or the client lib v3.0.0 too old to work with Tigase v7.1.0? Or are we missing something very trivial?

Details by android dev as follows..

Client requesting change of protocol sends the following:
GET / HTTP/1.1
Host: <host_url>
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Key: <key>
Sec-WebSocket-Protocol: xmpp,xmpp-framing
Sec-WebSocket-Version: 13

The response by tigase v5.2.3:
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Content-Type
Access-Control-Max-Age: 86400
Sec-WebSocket-Protocol: xmpp
Sec-WebSocket-Accept: <string>

The response by tigase v7.1.0:
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Content-Type
Access-Control-Max-Age: 86400
Sec-WebSocket-Protocol: xmpp-frame
Sec-WebSocket-Accept: <string>

"The difference in the Sec-WebSocket-Protocol from xmpp to xmpp-frame is making the client change to rfcCompatible mode, but the client freezes and isn't able to establish a connection."

Any help is appreciated.
Thanks!

Categories: Tigase Forums

Tigase server ad-hoc scripts: RE: Get user presence in cluster

Wed, 02/08/2017 - 13:50

Hi Wojciech,

thx

Can you point me to one of the scripts, so I can copy it and modify it

Categories: Tigase Forums

Tigase server ad-hoc scripts: RE: Get user presence in cluster

Wed, 02/08/2017 - 13:44

Tue Topholm wrote:

but is it correct that they don't show for all servers in the cluster, but do you need to ask each node for online users?

This is correct. For now scripts on the particular node are executed in the context of such node (except for a couple of scripts, which have capability be executed on all nodes).

Categories: Tigase Forums

Tigase server ad-hoc scripts: Get user presence in cluster

Wed, 02/08/2017 - 08:22

Hi All.

I have a set up where we have 3 machines, and we are using the provided scripts to get total online users etc out, but is it correct that they don't show for all servers in the cluster, but do you need to ask each node for online users?

Basically what I need is to ask GetPresence for a user and get their presence back and in my head I would only need to ask one node.

Hope you can understand my question.

/Tue

Categories: Tigase Forums

API and development: RE: MUC Group Avatar

Fri, 02/03/2017 - 04:50

It's not defined in MUC specification, but it should be possible to extend Tigase MUC implementation and add such non-standard functionality. If you are interested please contact us directly.

Categories: Tigase Forums

API and development: MUC Group Avatar

Thu, 02/02/2017 - 23:18

Is there a way to add avatar for tigase MUC group?

Categories: Tigase Forums

Installation and maintenance: RE: [WEBSITE] Certificate expired

Sun, 01/29/2017 - 09:24

Thanks, it's been renewed.

Categories: Tigase Forums

Installation and maintenance: [WEBSITE] Certificate expired

Sun, 01/29/2017 - 08:56

Hey team,
I guess you've already planned some action, I'll report it anyway just to be sure: your certificate for projects.tigase.org expired today.

Cheers

Categories: Tigase Forums

API and development: RE: Custom authentication

Sat, 01/28/2017 - 10:40
I think you followed proper way, however you need to either:
  • added to this authentication database in your case drupal database other functions/procedures which are used by TigaseCustomAuth, or
  • set SQL statements which will replace each of SQL queries done on autentication database by TigaseCustomAuth
Categories: Tigase Forums

API and development: Custom authentication

Thu, 01/26/2017 - 05:32

Hi,

By referring to tigase's documentation I was able to figure out how to implement custom user authentication for my application. (My purpose is to authenticate users from another database).
I therefore added few lines to my init.properties making it look as follows:

--comp-class-1 = tigase.muc.MUCComponent --virt-hosts = 192.168.2.121 --user-db-uri = jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12&autoCreateUser=true --user-db = mysql --admins = admin@user-pc --comp-name-4 = message-archive --comp-name-3 = proxy config-type = --gen-config-def --comp-name-2 = pubsub --comp-name-1 = muc --cluster-mode = true --sm-plugins = +message-archive-xep-0136 --debug = server --comp-class-4 = tigase.archive.MessageArchiveComponent --comp-class-3 = tigase.socks5.Socks5ProxyComponent --comp-class-2 = tigase.pubsub.PubSubComponent --auth-db = tigase-custom --auth-db-uri = jdbc:mysql://localhost/drupal?user=tigase&password=tigase12 basic-conf/auth-repo-params/user-login-query={ select username from users where (username = ?) AND (password = ?) }

However I'm unsure if this is the right way to do it because I'm getting the following exception:

2017-01-26 15:15:19.468 [main] ConfiguratorAbstract.setProperties() SEVERE: Can't initialize auth default repository: tigase.db.DBInitException: Problem initializing jdbc connection: jdbc:mysql://localhost/drupal?user=tigase&password=tigase12 at tigase.db.jdbc.TigaseCustomAuth.initRepository(TigaseCustomAuth.java:583) at tigase.db.RepositoryFactory.getAuthRepository(RepositoryFactory.java:387) at tigase.conf.ConfiguratorAbstract.addAuthRepo(ConfiguratorAbstract.java:857) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:834) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:1) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: FUNCTION TigInitdb does not exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1030) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2536) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465) at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1383) at com.mysql.jdbc.DatabaseMetaData.getCallStmtParameterTypes(DatabaseMetaData.java:1581) at com.mysql.jdbc.DatabaseMetaData.getProcedureOrFunctionColumns(DatabaseMetaData.java:4120) at com.mysql.jdbc.DatabaseMetaData.getProcedureColumns(DatabaseMetaData.java:4057) at com.mysql.jdbc.CallableStatement.determineParameterTypes(CallableStatement.java:809) at com.mysql.jdbc.CallableStatement.<init>(CallableStatement.java:609) at com.mysql.jdbc.JDBC4CallableStatement.<init>(JDBC4CallableStatement.java:46) at sun.reflect.GeneratedConstructorAccessor16.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.CallableStatement.getInstance(CallableStatement.java:505) at com.mysql.jdbc.ConnectionImpl.parseCallableStatement(ConnectionImpl.java:3881) at com.mysql.jdbc.ConnectionImpl.prepareCall(ConnectionImpl.java:3965) at com.mysql.jdbc.ConnectionImpl.prepareCall(ConnectionImpl.java:3939) at tigase.db.jdbc.DataRepositoryImpl.prepareQuery(DataRepositoryImpl.java:463) at tigase.db.jdbc.DataRepositoryImpl.initStatement(DataRepositoryImpl.java:410) at tigase.db.jdbc.DataRepositoryImpl.initPreparedStatement(DataRepositoryImpl.java:206) at tigase.db.DataRepositoryPool.initPreparedStatement(DataRepositoryPool.java:174) at tigase.db.jdbc.TigaseCustomAuth.initRepository(TigaseCustomAuth.java:499) at tigase.db.RepositoryFactory.getAuthRepository(RepositoryFactory.java:387) at tigase.conf.ConfiguratorAbstract.addAuthRepo(ConfiguratorAbstract.java:857) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:834) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:1) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112)

Thanks

Categories: Tigase Forums

API and development: RE: Starting the server with eclipse.

Thu, 01/26/2017 - 00:49

Thank you for your fast reply.

I'm now able to start the server with no exceptions or errors, thanks.

Categories: Tigase Forums

API and development: RE: Starting the server with eclipse.

Thu, 01/26/2017 - 00:35

Hi,

This error usually means that there is no JDBC driver in your classpath. In this case class com.mysql.jdbc.Driver is not found and it is part of MySQL JDBC driver. Please verify that MySQL driver is in your classpath.

Categories: Tigase Forums

API and development: Starting the server with eclipse.

Thu, 01/26/2017 - 00:05

Hi,
I have been getting the following exception when I try to run the server from eclipse.

Any help on this issue would be appreciated.

java.lang.ClassNotFoundException: com.mysql.jdbc.Driver at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at tigase.db.jdbc.DataRepositoryImpl.initRepository(DataRepositoryImpl.java:264) at tigase.db.RepositoryFactory.getDataRepository(RepositoryFactory.java:463) at tigase.db.jdbc.JDBCRepository.initRepository(JDBCRepository.java:590) at tigase.db.RepositoryFactory.getUserRepository(RepositoryFactory.java:672) at tigase.conf.ConfiguratorAbstract.addUserRepo(ConfiguratorAbstract.java:888) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:817) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) 2017-01-26 09:56:33.677 [main] ConfiguratorAbstract.setProperties() SEVERE: Can't initialize user default repository: tigase.db.DBInitException: Problem initializing jdbc connection: jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12 at tigase.db.jdbc.JDBCRepository.initRepository(JDBCRepository.java:627) at tigase.db.RepositoryFactory.getUserRepository(RepositoryFactory.java:672) at tigase.conf.ConfiguratorAbstract.addUserRepo(ConfiguratorAbstract.java:888) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:817) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) Caused by: tigase.db.DBInitException: Database initialization failed at tigase.db.jdbc.DataRepositoryImpl.initRepository(DataRepositoryImpl.java:300) at tigase.db.RepositoryFactory.getDataRepository(RepositoryFactory.java:463) at tigase.db.jdbc.JDBCRepository.initRepository(JDBCRepository.java:590) at tigase.db.RepositoryFactory.getUserRepository(RepositoryFactory.java:672) at tigase.conf.ConfiguratorAbstract.addUserRepo(ConfiguratorAbstract.java:888) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:817) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) Caused by: java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12 at java.sql.DriverManager.getConnection(DriverManager.java:689) at java.sql.DriverManager.getConnection(DriverManager.java:270) at tigase.db.jdbc.DataRepositoryImpl.initRepo(DataRepositoryImpl.java:440) at tigase.db.jdbc.DataRepositoryImpl.initRepository(DataRepositoryImpl.java:294) at tigase.db.RepositoryFactory.getDataRepository(RepositoryFactory.java:463) at tigase.db.jdbc.JDBCRepository.initRepository(JDBCRepository.java:590) at tigase.db.RepositoryFactory.getUserRepository(RepositoryFactory.java:672) at tigase.conf.ConfiguratorAbstract.addUserRepo(ConfiguratorAbstract.java:888) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:817) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) 2017-01-26 09:56:33.681 [main] DataRepositoryImpl.initRepository() SEVERE: null java.lang.ClassNotFoundException: com.mysql.jdbc.Driver at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at tigase.db.jdbc.DataRepositoryImpl.initRepository(DataRepositoryImpl.java:264) at tigase.db.RepositoryFactory.getDataRepository(RepositoryFactory.java:463) at tigase.db.jdbc.TigaseCustomAuth.initRepository(TigaseCustomAuth.java:495) at tigase.db.RepositoryFactory.getAuthRepository(RepositoryFactory.java:387) at tigase.conf.ConfiguratorAbstract.addAuthRepo(ConfiguratorAbstract.java:857) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:834) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) 2017-01-26 09:56:33.683 [main] ConfiguratorAbstract.setProperties() SEVERE: Can't initialize auth default repository: tigase.db.DBInitException: Problem initializing jdbc connection: jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12 at tigase.db.jdbc.TigaseCustomAuth.initRepository(TigaseCustomAuth.java:583) at tigase.db.RepositoryFactory.getAuthRepository(RepositoryFactory.java:387) at tigase.conf.ConfiguratorAbstract.addAuthRepo(ConfiguratorAbstract.java:857) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:834) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) Caused by: tigase.db.DBInitException: Database initialization failed at tigase.db.jdbc.DataRepositoryImpl.initRepository(DataRepositoryImpl.java:300) at tigase.db.RepositoryFactory.getDataRepository(RepositoryFactory.java:463) at tigase.db.jdbc.TigaseCustomAuth.initRepository(TigaseCustomAuth.java:495) at tigase.db.RepositoryFactory.getAuthRepository(RepositoryFactory.java:387) at tigase.conf.ConfiguratorAbstract.addAuthRepo(ConfiguratorAbstract.java:857) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:834) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112) Caused by: java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12 at java.sql.DriverManager.getConnection(DriverManager.java:689) at java.sql.DriverManager.getConnection(DriverManager.java:270) at tigase.db.jdbc.DataRepositoryImpl.initRepo(DataRepositoryImpl.java:440) at tigase.db.jdbc.DataRepositoryImpl.initRepository(DataRepositoryImpl.java:294) at tigase.db.RepositoryFactory.getDataRepository(RepositoryFactory.java:463) at tigase.db.jdbc.TigaseCustomAuth.initRepository(TigaseCustomAuth.java:495) at tigase.db.RepositoryFactory.getAuthRepository(RepositoryFactory.java:387) at tigase.conf.ConfiguratorAbstract.addAuthRepo(ConfiguratorAbstract.java:857) at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:834) at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519) at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152) at tigase.conf.Configurator.componentAdded(Configurator.java:50) at tigase.conf.Configurator.componentAdded(Configurator.java:33) at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116) at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138) at tigase.server.MessageRouter.setConfig(MessageRouter.java:644) at tigase.server.XMPPServer.start(XMPPServer.java:142) at tigase.server.XMPPServer.main(XMPPServer.java:112)
Categories: Tigase Forums

Installation and maintenance: RE: What is the max length of a message?

Wed, 01/25/2017 - 19:38

Right. Got the point! We'll go ahead and set a limit only in the front-end side, unfortunately.

Thanks for the quick response,

Best regards.
Mauricio Giacomello.

Categories: Tigase Forums

Pages

Get in touch

We provide software products, consulting and custom development services

Tigase, Inc.
100 Pine Street, Suite 1250
San Francisco, CA 94111, USA
Phone: (415) 315 9771

Follow us on:

Twitter

Back to Top