Hello all.
We have started a 1500 user migration from an old jabberd1.4 to wildfire 3.01.
It’'s running on Windows 2003, AD authentication, SQL database.
We are up to about 575 connections, and I am starting to see the following over and over in the error log. The result is we have connection problems from frolks
Wildfire admin console shows java memory at 160.36 MB of 493.06 MB (32.5%) used
Is there anything else I can look at or fine tune for this?
2006.08.22 12:04:16 [org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java :104)
at org.jivesoftware.wildfire.net.SocketAcceptThread.run(SocketAcceptThread.java:11 1)
at org.jivesoftware.wildfire.net.BlockingAcceptingMode.run(BlockingAcceptingMode.j ava:52)
at java.lang.Thread.start(Unknown Source)
at java.lang.Thread.start0(Native Method)
java.lang.OutOfMemoryError: unable to create new native thread
] Trouble accepting connection
2006.08.22 12:03:52 [org.jivesoftware.wildfire.net.BlockingAcceptingMode.run(BlockingAcceptingMode. java:62)
at org.jivesoftware.wildfire.net.SocketAcceptThread.run(SocketAcceptThread.java:11 1)
at org.jivesoftware.wildfire.net.BlockingAcceptingMode.run(BlockingAcceptingMode.j ava:52)
at java.lang.Thread.start(Unknown Source)
at java.lang.Thread.start0(Native Method)
java.lang.OutOfMemoryError: unable to create new native thread
] Trouble accepting connection
2006.08.22 12:03:07 [org.jivesoftware.wildfire.net.BlockingAcceptingMode.run(BlockingAcceptingMode. java:62)
at org.jivesoftware.wildfire.net.SocketAcceptThread.run(SocketAcceptThread.java:11 1)
at org.jivesoftware.wildfire.net.BlockingAcceptingMode.run(BlockingAcceptingMode.j ava:52)
at java.lang.Thread.start(Unknown Source)
at java.lang.Thread.start0(Native Method)
java.lang.OutOfMemoryError: unable to create new native thread
Thanks
Pat