-
It looks like that Tigase is starting normally but for some reason Windows is stopping the service:
INFO | jvm 1 | 2016/03/03 06:35:26 | 2016-03-03 06:35:26.939 [WrapperSimpleAppMain] ConfigurationCache.store() WARNING: Dumping server configuration to: etc/config-dump.properties INFO | jvm 1 | 2016/03/03 06:37:52 | ShutdownThread started...
INFO | jvm 1 | 2016/03/03 06:54:06 | 2016-03-03 06:54:06.626 [WrapperSimpleAppMain] ConfigurationCache.store() WARNING: Dumping server configuration to: etc/config-dump.properties INFO | jvm 1 | 2016/03/03 06:54:14 | ShutdownThread started... INFO | jvm 1 | 2016/03/03 06:54:14 | == Removing cluster_nodes item: lafd
First time after two minutes, second - after couple of seconds.
Please check Windows services logs for more informations.
-
I feel that the issue is not specific to Windows service. I am getting this issue even when I run Tigase in Console mode. Error message is : -
_java -cp "jars/" -Djdbc.drivers=com.mysql.jdbc.Driver tigas
e.server.XMPPServer --property-file etc/init.properties
Error: Could not find or load main class tigase.server.XMPPServer*_
Please note, I have configured the server to run with MS SQL, but the error message seem to contain entries related to mysql driver.
Please find the attached init.properties file attached.
-
Vijay, Did you run the Setup.bat file? That error will show if you run run.bat in the win-stuff/scripts folder, it needs to be in the Tigase Root directory. Try that and see if a more verbose error occurs.
From the logs nothing seems to be causing the shutdown from Tigase's end. Wrapper will close Tigase if an error occurs outside the program and may not give us useful information.
I would also recommend adding db to the --debug line and see if any DB errors pop up after another series of runs.
Type |
Bug
|
Priority |
Major
|
Assignee | |
RedmineID |
3989
|
Version |
tigase-server-7.1.0
|
After configuring the nightly build from 20 Feb 2016 in a Windows machine (Windows Server 2008 R2 with 64 - bit OS), I am able to start Tigase XMPP as a windows service. But I am not able to connect to the XMPP server using any client. Message I am getting is "Could not connect to server".
I tried the same with nightly build from 20 January 2016 and was able to successfully deploy in some other machines with the same configuration. But it also failed in this particular machine.
Getting the following message in wrapper.log file : -
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: The file is located on the path at the following location but
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: could not be loaded:
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: C:\Tigase\jars\wrapper.dll
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: Please verify that the file is both readable and executable by the
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: current user and that the file has not been corrupted in any way.
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: One common cause of this problem is running a 32-bit version
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: This is a 64-bit JVM.
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: Reported cause:
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: C:\Tigase\jars\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager: System signals will not be handled correctly.
INFO | jvm 1 | 2016/03/03 06:35:15 | WrapperManager:
TigaseLog.zip init.properties