Projects tigase _server server-core Issues #331
Tigase server is going to shutdown if it is ideal for 30mins (#331)
Sesha Reddy Mutyala opened 1 decade ago

Hi I installed tigase server in Windows and Linux operating system i observe that server is going to shutdown if it is ideal for 15mins can you please help me out what i need to configure to over come this issue.

Thanks,

M.Sesha Reddy.

wojciech.kapcia@tigase.net commented 1 decade ago

Does it shutdown after 15 or 30 minutes (you provide two numbers…).

Nevertheless - there is no such mechanism build into Tigase.

Can you share more details?

Sesha Reddy Mutyala commented 1 decade ago

yes it is going to shutdown irrespective of time interval exp(5,15,10,30) in Unix but in windows it is taking some good amount of time to shutdown

wojciech.kapcia@tigase.net commented 1 decade ago

Please share the logs from the Tigase run that manifests the self-shutdown.

Sesha Reddy Mutyala commented 1 decade ago

Not getting any error messages in console log and tigase.log files

wojciech.kapcia@tigase.net commented 1 decade ago

I did not ask if you are getting any errors, I asked you to share the logs so we can investigate the issue and provide you with help.

Otherwise, if you don't want to share those and go forward, we can conclude that this issue is not related to Tigase (as it was stated already - there is no such mechanism build in) and close the issue.

Sesha Reddy Mutyala commented 1 decade ago

[ec2-user@ip-10-128-141-228 logs]$ vi tigase-console.log

2014-06-10 20:55:44.785 [main]             ConfiguratorAbstract.setup()       CONFIG:   Component basic-conf configuration: {component-id=basic-conf@ip-10-128-141-228.ap-southeast-1.compute.internal, def-hostname=ip-10-128-141-228.ap-southeast-1.compute.internal, admins=[Ljava.lang.String;@6433a2, scripts-dir=scripts/admin, command/ALL=ADMIN, logging/.level=CONFIG, logging/handlers=java.util.logging.ConsoleHandler java.util.logging.FileHandler, logging/java.util.logging.ConsoleHandler.formatter=tigase.util.LogFormatter, logging/java.util.logging.ConsoleHandler.level=WARNING, logging/java.util.logging.FileHandler.append=true, logging/java.util.logging.FileHandler.count=5, logging/java.util.logging.FileHandler.formatter=tigase.util.LogFormatter, logging/java.util.logging.FileHandler.limit=10000000, logging/java.util.logging.FileHandler.pattern=logs/tigase.log, logging/tigase.useParentHandlers=true, logging/java.util.logging.FileHandler.level=ALL, logging/tigase.server.level=ALL, logging/tigase.xmpp.impl.level=ALL, logging/tigase.db.level=ALL, logging/tigase.archive.level=ALL, user-domain-repo-pool=tigase.db.UserRepositoryMDImpl, auth-domain-repo-pool=tigase.db.AuthRepositoryMDImpl, user-repo-pool-size=10, data-repo-pool-size=10, user-repo-class=mysql, user-repo-url=jdbc:mysql://54.251.87.63:3306/chat?user=chat&password=chat123, auth-repo-class=tigase.db.jdbc.TigaseCustomAuth, auth-repo-url=jdbc:mysql://54.251.87.63:3306/chat?user=chat&password=chat123, ssl-container-class=tigase.io.SSLContextContainer, ssl-certs-location=certs/, ssl-def-cert-domain=default, config-dump-file=etc/config-dump.properties}
2014-06-10 20:55:44.787 [main]             ConfiguratorAbstract.setProperties()  INFO:  Propeties size is 36, and here are all propeties: {component-id=basic-conf@ip-10-128-141-228.ap-southeast-1.compute.internal, def-hostname=ip-10-128-141-228.ap-southeast-1.compute.internal, admins=[Ljava.lang.String;@6433a2, scripts-dir=scripts/admin, command/ALL=ADMIN, logging/.level=CONFIG, logging/handlers=java.util.logging.ConsoleHandler java.util.logging.FileHandler, logging/java.util.logging.ConsoleHandler.formatter=tigase.util.LogFormatter, logging/java.util.logging.ConsoleHandler.level=WARNING, logging/java.util.logging.FileHandler.append=true, logging/java.util.logging.FileHandler.count=5, logging/java.util.logging.FileHandler.formatter=tigase.util.LogFormatter, logging/java.util.logging.FileHandler.limit=10000000, logging/java.util.logging.FileHandler.pattern=logs/tigase.log, logging/tigase.useParentHandlers=true, logging/java.util.logging.FileHandler.level=ALL, logging/tigase.server.level=ALL, logging/tigase.xmpp.impl.level=ALL, logging/tigase.db.level=ALL, logging/tigase.archive.level=ALL, user-domain-repo-pool=tigase.db.UserRepositoryMDImpl, auth-domain-repo-pool=tigase.db.AuthRepositoryMDImpl, user-repo-pool-size=10, data-repo-pool-size=10, user-repo-class=mysql, user-repo-url=jdbc:mysql://54.251.87.63:3306/chat?user=chat&password=chat123, auth-repo-class=tigase.db.jdbc.TigaseCustomAuth, auth-repo-url=jdbc:mysql://54.251.87.63:3306/chat?user=chat&password=chat123, ssl-container-class=tigase.io.SSLContextContainer, ssl-certs-location=certs/, ssl-def-cert-domain=default, config-dump-file=etc/config-dump.properties, shared-user-repo=null, shared-user-repo-params=null, shared-auth-repo=null, shared-auth-repo-params=null}
Jid vhost-manager;
2014-06-10 20:55:52.715 [main]             VHostManager.setProperties()       WARNING:  {54.251.87.63=Domain: 54.251.87.63, enabled: true, anonym: true, register: true, maxusers: 0, tls: false, s2sSecret: null, domainFilter: ALL, chat.my-doc.com=Domain: chat.my-doc.com, enabled: true, anonym: true, register: true, maxusers: 0, tls: false, s2sSecret: null, domainFilter: ALL}
Loading component: bosh :: componentInfo{Title=Tigase XMPP Server, Version=5.2.1-b3461/e362e35b (2014-04-07/13:47:05), Class=tigase.server.bosh.BoshConnectionManager}
Loading component: c2s :: componentInfo{Title=Tigase XMPP Server, Version=5.2.1-b3461/e362e35b (2014-04-07/13:47:05), Class=tigase.server.xmppclient.ClientConnectionManager}
---------------------->http://dev-api.my-doc.com/
Loading component: message-archive :: componentInfo{Class=tigase.archive.MessageArchiveComponent}
Loading component: monitor :: componentInfo{Title=Tigase XMPP Server, Version=5.2.1-b3461/e362e35b (2014-04-07/13:47:05), Class=tigase.server.monitor.MonitorComponent}
Loading component: muc :: componentInfo{Title=Tigase XMPP Server, Version=5.2.1-b3461/e362e35b (2014-04-07/13:47:05), Class=tigase.server.xmppcomponent.ComponentConnectionManager}
2014-06-10 20:56:10.496 [main]             ConfigRepository.setProperties()   WARNING:  Items list is not set in the configuration file!!
Jid rest;
2014-06-10 20:56:11.276 [main]             HttpServer.setProperties()         WARNING:  no HttpRegistrator instance where useLocal = true
~

logs i am getting

wojciech.kapcia@tigase.net commented 1 decade ago

This doesn't look like the complete output.

And then what? Tigase process is completely gone? Does it crash? do you have enough resources?

Please provide more details about the environment.

Sesha Reddy Mutyala commented 1 decade ago

I am using amazon-linux-ami operating system

and memory details are below

[ec2-user@ip-10-128-141-228 tigase-issue #5.2.1-b3461]$ free
             total       used       free     shared    buffers     cached
Mem:        608292     602016       6276          0       2420      34248
-/+ buffers/cache:     565348      42944
Swap:            0          0          0
[ec2-user@ip-10-128-141-228 tigase-issue #5.2.1-b3461]$
Sesha Reddy Mutyala commented 1 decade ago

if it is memory issue can you please let me know how much memory did tigase version 5.2.1 will occupy

wojciech.kapcia@tigase.net commented 1 decade ago

Sesha Reddy Mutyala wrote:

if it is memory issue can you please let me know how much memory did tigase version 5.2.1 will occupy

Yes, it's possible that this is caused by lack of memory. As it was stated ( Tigase with 10MB RAM ) Tigase is very efficient when it comes to memory usage, however by default JVM configuration used by Tigase assigns as much as 256M of memory. This can be fine tuned by editing etc/tigase.conf file.

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