This issue is caused by data_repo field being @null@. This can happen only if there was issue with creation of repository and propably with some issue during establishing connection to database server during server instance startup.

I think that there is no way to recover from this properly and best would be to find root cause of this issue, ie. by searching logs for entries containing:

and then solving root cause of this issue.

Thank you for looking at this. In such case it is not such a big problem. However, I think, if there is no way Tigase can handle or recover from this properly and if this happens at startup time, then the best action would be to print a correct log message and stop the server.

This issue happened during server runtime, not during server instance startup. The data_repo was not null, but the statement was null and the code synchronized(stmt) thrown the NullPointerException.

I would suggest to catch exception in the method ConfigRepository.setAutoloadTimer() to prevent the timer thread being terminated when unexpected exception happens.

autoLoadTimer.schedule(new TimerTask()

{

		@Override

		public void run() {

                          try {

			reload();

                          } catch (Exception e) {

                            //print some log messages here.

                          }

		}

}, interval, interval);

I checked repository for version in which I could see that in file ClConSQLRepository.java in line 204 there is synchronized(stmt) but I could not find exact version, but assuming this might be issue and try {} catch {} in run() method of TimerTask will help protect timer from being killed in case of other unexpected exceptions I added this suggested try{} catch {}.

This change was added to master and stable branch.

Thank you for providing additional details and helping us with fixing the problem.