Service Restarting

[ccdesktop]

Hi - I believe there is a similar issue to the one in LS 3.2 initially whereby the service crashes and restarts (I have it set to restart on failure). The problem in 3.2 I think was the service just hung. This was fixed with the final 3.2 service.

It seems when there is a large number of machines in the queue or when it is unable to connect to machines or something it fails.

The last event in the error log before the service restarted was:

13/03/2009 09:11:34: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
   at LansweeperService.MdlLicenceCode.checklicense()
   at LansweeperService.mdlActivescanning.ActiveScan()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

13/03/2009 09:12:50: Database connection successful, starting up service

[ccdesktop]

I had it set to 100.

This was what we always used.

What are you recommending - we have about 3000 clients? A large number of which logon all at the same time in the morning.

[Hemoco]

ccdesktop wrote:
I had it set to 100.
This was what we always used.
What are you recommending - we have about 3000 clients? A large number of which logon all at the same time in the morning.

Scanning should be a lot faster than in previous version.
In this case the service can run fine with the 100 threads, it's the database server that can't follow because it is out of connections.

Try lowering it to 50

[Hemoco]

On how many concurrent threads are you running?
Lowering this will solve the problem.