Projects tigase _server server-core Issues #902
Server has issues reconnecting to MySQL Server (#902)
Daniel Wisnewski opened 7 years ago

After upgrading to latest build b5055 the following errors sprung up:

2017-11-06 12:21:10.688 [main]             DataRepositoryImpl.checkSchemaVersion()  WARNING: Problem checking schema version
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: PROCEDURE tigasedb.TigGetComponentVersion 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:425)
	at com.mysql.jdbc.Util.getInstance(Util.java:408)
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:943)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3970)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3906)
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2524)
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2677)
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2549)
	at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)
	at com.mysql.jdbc.CallableStatement.executeQuery(CallableStatement.java:858)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at tigase.db.jdbc.PreparedStatementInvocationHandler.invoke(PreparedStatementInvocationHandler.java:41)
	at com.sun.proxy.$Proxy33.executeQuery(Unknown Source)
	at tigase.db.jdbc.DataRepositoryImpl.checkSchemaVersion(DataRepositoryImpl.java:108)
	at tigase.db.jdbc.DataRepositoryImpl.checkSchemaVersion(DataRepositoryImpl.java:95)
	at tigase.db.DataRepositoryPool.checkSchemaVersion(DataRepositoryPool.java:105)
	at tigase.http.upload.db.JDBCFileUploadRepository.setDataSource(JDBCFileUploadRepository.java:235)
	at tigase.http.upload.db.JDBCFileUploadRepository.setDataSource(JDBCFileUploadRepository.java:1)
	at tigase.db.beans.MDRepositoryBean$MDRepositoryConfigBean.setDataSourceAware(MDRepositoryBean.java:305)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at tigase.kernel.BeanUtils.setValue(BeanUtils.java:177)
	at tigase.kernel.core.Kernel.inject(Kernel.java:1075)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1158)
	at tigase.kernel.core.Kernel.injectDependency(Kernel.java:709)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:723)
	at tigase.kernel.core.Kernel.registerBean(Kernel.java:943)
	at tigase.kernel.core.BeanConfigBuilder.execWithoutInject(BeanConfigBuilder.java:115)
	at tigase.kernel.core.BeanConfigBuilder.exec(BeanConfigBuilder.java:102)
	at tigase.db.beans.MDRepositoryBean$MDRepositoryConfigBean.beanConfigurationChanged(MDRepositoryBean.java:286)
	at tigase.db.beans.MDRepositoryBean$MDRepositoryConfigBean.initialize(MDRepositoryBean.java:331)
	at tigase.kernel.core.Kernel.initBean(Kernel.java:136)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1100)
	at tigase.kernel.core.Kernel.injectDependency(Kernel.java:709)
	at tigase.kernel.core.Kernel$DelayedDependenciesInjection.inject(Kernel.java:1363)
	at tigase.kernel.core.Kernel.finishDependecyDelayedInjection(Kernel.java:519)
	at tigase.kernel.core.Kernel.initBean(Kernel.java:128)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1100)
	at tigase.kernel.core.Kernel.initBean(Kernel.java:131)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1100)
	at tigase.kernel.core.Kernel.initBean(Kernel.java:131)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1100)
	at tigase.kernel.core.Kernel.initBean(Kernel.java:131)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1100)
	at tigase.kernel.core.Kernel.injectDependency(Kernel.java:709)
	at tigase.kernel.core.Kernel$DelayedDependenciesInjection.inject(Kernel.java:1363)
	at tigase.kernel.core.Kernel.finishDependecyDelayedInjection(Kernel.java:519)
	at tigase.kernel.core.Kernel.initBean(Kernel.java:128)
	at tigase.kernel.core.Kernel.injectDependencies(Kernel.java:1100)
	at tigase.kernel.core.Kernel.injectIfRequired(Kernel.java:875)
	at tigase.kernel.core.Kernel.getInstance(Kernel.java:291)
	at tigase.server.Bootstrap.start(Bootstrap.java:162)
	at tigase.server.XMPPServer.start(XMPPServer.java:193)
	at tigase.server.XMPPServer.main(XMPPServer.java:147)

Several other errors cascaded as a result when loading the following components:

sess-man

http

muc

incoming connections cause errors like the one below, likely as a result of being unable to connect to db

2017-11-06 12:21:22.762 [ConnectionOpenThread]  ConnectionOpenThread.addAllWaiting()  WARNING: Error: creating connection for: {remote-host=localhost, port-no=5222, new-connections-throttling=200, ifc=[Ljava.lang.String;@14ab3e22, socket=plain, type=accept}
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at tigase.net.ConnectionOpenThread.addISA(ConnectionOpenThread.java:293)
	at tigase.net.ConnectionOpenThread.addPort(ConnectionOpenThread.java:326)
	at tigase.net.ConnectionOpenThread.addAllWaiting(ConnectionOpenThread.java:266)
	at tigase.net.ConnectionOpenThread.run(ConnectionOpenThread.java:231)
	at java.lang.Thread.run(Thread.java:745)

Console log attached for full details.

tigase-console.log

wojciech.kapcia@tigase.net commented 7 years ago

Daniel Wisnewski wrote:

After upgrading to latest build b5055 the following errors sprung up:

%Daniel, please run upgrade-schema and this will be resolved.

incoming connections cause errors like the one below, likely as a result of being unable to connect to db

Hmm, this looks more like an issue with two (or more) instances running at the same time.

Daniel Wisnewski commented 7 years ago

Starts up OK after upgrade-schema command is used. Closing issue.

issue 1 of 1
Type
Bug
Priority
Major
Assignee
RedmineID
6306
Version
tigase-server-8.0.0
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#902
Please wait...
Page is in error, reload to recover