1.
在tigase-console.log中的warning
2015-06-30 22:09:24.489 [ConnectionOpenThread] ConnectionOpenThread.run() WARNING: Cant obtain socket channel from selection key, throttling activated = {0}, for port: {1}
2015-06-30 22:09:24.517 [ConnectionOpenThread] ConnectionManager.serviceStarted() WARNING: c2s: Attempt to add different service with the same ID: null, type: accept, Socket: nullSocket[addr=/10.5.83.168,port=42100,localport=5222],
jid: null
解決辦法
Please adjust throttling settings:
2.
在tigase-console.log中
2015-07-05 16:57:47.205 [in_46-sess-man] AbstractMessageReceiver$QueueListener.run() SEVERE: [in_46-sess-man] Exception during packet processing: from=null, to=null, DATA=<iq id="ssl_82035848-5ced-4c1e-9cdf-2563a05bcfe9"
to="sess-man@localhost" from="c2s@localhost/10.61.5.78_5222_10.5.83.142_57121" type="get"><command node="GETFEATURES" xmlns="http://jabber.org/protocol/commands"/></iq>, SIZE=218, XMLNS=null, PRIORITY=HIGH, PERMISSION=NONE, TYPE=get
java.lang.NullPointerException
at tigase.server.xmppsession.SessionManager.processCommand(SessionManager.java:1321)
at tigase.server.xmppsession.SessionManager.processPacket(SessionManager.java:500)
at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1424)
解決辦法,使用tsung測試時減小用戶進入速度。
3.
java.lang.outofmemoryerror:gc overhead limit exceeded at ......
解決辦法在tigase.conf中java-options調整-xms,-xmx大小
1、-XX:newSize:表示新生代初始內存的大小,應該小於 -Xms的值;
2、-XX:MaxnewSize:表示新生代可被分配的內存的最大上限;當然這個值應該小於 -Xmx的值;
3、-Xmn:至於這個參數則是對 -XX:newSize、-XX:MaxnewSize兩個參數的同時配置,也就是說如果通過-Xmn來配置新生代的內存大小,那麼-XX:newSize = -XX:MaxnewSize = -Xmn,雖然會很方便,但需要注意的是這個參數是在JDK1.4版本以後才使用的。
上面所述即爲java虛擬機對外提供的可配置堆區的參數,接下來講述java虛擬機對非堆區內存配置的兩個參數:
1、-XX:PermSize:表示非堆區初始內存分配大小,其縮寫爲permanent size(持久化內存)
2、-XX:MaxPermSize:表示對非堆區分配的內存的最大上限。
4.
ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "sess-man tasks" exception、
據查資料瞭解是This is a result of using Tigase package build with JDK8 under previous version of
Java and can be ignored.
是說tigase使用jdk8,你的jdk版本不夠,不過可以忽略這個問題