X-EventCollector TimerTask execution failed unexpectedly: null

dummy@example.com (MarekR) — Mon, 05 Aug 2019 10:53:57 +0000

If the X-EventCollector logs give an error that looks as follows:

00:00:00.000 - TRACE - Successfully opened the mail folder Inbox to search for mails matching the given search terms
00:00:00.000 - ERROR - TimerTask execution failed unexpectedly: null
java.lang.StackOverflowError: null
	at javax.mail.search.AndTerm.match(AndTerm.java:109)
	at javax.mail.search.AndTerm.match(AndTerm.java:109)
	at javax.mail.search.AndTerm.match(AndTerm.java:109)
	at javax.mail.search.AndTerm.match(AndTerm.java:109)
	at javax.mail.search.AndTerm.match(AndTerm.java:109)

If you restart the X-EventCollector service it should work again. The cause of this is that X-EventCollector used more memory then it was CONFIGURED to.

To change this configuration go to the "SXI\X-EventCollector\bin" directory and edit a file named "X-EventCollector.vmoptions".

The contents of the file will look as follows:

# Enter one VM parameter per line
# For example, to adjust the maximum memory usage to 512 MB, uncomment the following line:
# -Xmx512m
# To include another file, uncomment the following line:
# -include-options [path to other .vmoption file]

Uncomment the 3rd line that contains "# -Xmx512m" by removing the "#" and then adjust the amount of memory that X-EventCollector can use. e.g. from "512m" to "1024m" (1gb).

Once the above steps are completed restart the X-EventCollector service and it should work.

SXI Forum / X-EventCollector TimerTask execution failed unexpectedly: null

X-EventCollector TimerTask execution failed unexpectedly: null