Awaiting 3.2.3:

Unwanted features include, yet not limited too:

Delete plugins <- does not remove them.

"And with all the problems with Content Filter and crashing java, I had to rm for now.

2007.02.22 15:44:18 org.jivesoftware.wildfire.interceptor.InterceptorManager.invokeInterceptors(Inte rceptorManager.java:239) Error in interceptor: org.jivesoftware.wildfire.plugin.ContentFilterPlugin@ea3932

java.lang.OutOfMemoryError: Java heap space

2007.02.22 15:44:24 org.jivesoftware.wildfire.interceptor.InterceptorManager.invokeInterceptors(Inte rceptorManager.java:239) Error in interceptor: org.jivesoftware.wildfire.plugin.ContentFilterPlugin@ea3932

java.lang.OutOfMemoryError: Java heap space

2007.02.22 15:44:30 org.jivesoftware.wildfire.interceptor.InterceptorManager.invokeInterceptors(Inte rceptorManager.java:239) Error in interceptor: org.jivesoftware.wildfire.plugin.ContentFilterPlugin@ea3932

java.lang.OutOfMemoryError: Java heap space

2007.02.22 15:44:36 org.jivesoftware.wildfire.interceptor.InterceptorManager.invokeInterceptors(Inte rceptorManager.java:239) Error in interceptor: org.jivesoftware.wildfire.plugin.ContentFilterPlugin@ea3932

java.lang.OutOfMemoryError: Java heap space"

Active Client Sessions: <- shows one more than it list.

Session Statistics: Packets Received/Sent: 1,601/0 <- always has /0 for sent.

Java Memory 45.30 MB of 63.31 MB (71.6%) used <- Is there a simple way to edit this value?

Other Log’'s:

2007.03.05 00:36:56 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

2007.03.05 00:36:56 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

2007.03.05 16:46:12 Could not route packet

2007.03.05 16:54:34 org.jivesoftware.wildfire.spi.PresenceManagerImpl.userUnavailable(PresenceManage rImpl.java:264) Error storing offline presence of user:

java.sql.SQLException: Unique constraint violation: SYS_IDX_75 in statement

at org.hsqldb.jdbc.Util.throwError(Unknown Source)

at org.hsqldb.jdbc.jdbcPreparedStatement.execute(Unknown Source)

at org.jivesoftware.wildfire.spi.PresenceManagerImpl.userUnavailable(PresenceManag erImpl.java:261)

at org.jivesoftware.wildfire.handler.PresenceUpdateHandler.process(PresenceUpdateH andler.java:121)

at org.jivesoftware.wildfire.SessionManager$ClientSessionListener.onConnectionClos e(SessionManager.java:1493)

at org.jivesoftware.wildfire.nio.NIOConnection.notifyCloseListeners(NIOConnection. java:161)

at org.jivesoftware.wildfire.nio.NIOConnection.close(NIOConnection.java:140)

at org.jivesoftware.wildfire.net.StanzaHandler.process(StanzaHandler.java:109)

at org.jivesoftware.wildfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:131)

Java Memory 45.30 MB of 63.31 MB (71.6%) used <- Is there a simple way to edit this value?

You may set the Xmx value to a higher value to increase the java heap.

Thanks for the hint.

Still this version seems to keep growing in heap space which older version did not.

How set the Xmx value in windows?

thank you

openfire/documentation/install-guide.html reads:

Custom Parameters

Advanced users may wish to pass in parameters to the Java virtual machine (VM) to customize the runtime environment of Openfire. You can do this by creating vmoptions files in the bin/ directory of your Openfire installation. For the Windows service, you’‘d create a new text file called openfire-service.vmoptions. Each parameter to the VM should be on a new line of the file. For example, to set the minimum heap size to 512 MB and max VM heap size to 1024 MB, you’'d use:

-Xms512m

-Xmx1024m

To create parameters for the normal launcher, create a file called openfired.vmoptions (since the openfire.exe launcher invokes the openfired.exe executable to actually start the server).

If you are still using Wildfire you should name the file “wild…” and not “open…”.

LG