16
Views
1
Comments
[Discovery] Scheduler Service: Error executing request DiscoveryProbefor Timer SnapShot_Create
Forge component by Francisco Menezes
Application Type
Traditional Web

Hi,


Latest version will produce almost everyday the following error:

Scheduler Service: Error executing request http://127.0.0.1:80/DiscoveryProbe/ for Timer SnapShot_Create. Request duration = 120 secs.  [retry 2 of 1 scheduled]

eSpaceVer: Id=0, PubId=0, CompiledWith=11.12.0.30456
RequestUrl: (Method: )
AppDomain: Scheduler.exe
Path: e:\OutSystems\Platform Server\Scheduler\
Locale:
DateFormat: yyyy-M-d
PID: 4364 ('Scheduler', Started='8/11/2021 6:05:21 AM', Priv=50Mb, Virt=4812Mb)
TID: 12
Thread Name: Timer Processor #1 (Database: System)
.NET: 4.0.30319.42000

[1] The underlying connection was closed: An unexpected error occurred on a receive.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at OutSystems.Scheduler.Core.TimerHandler.ExecuteTimer(String ssKey, Int32 timeout, Int32 tenantId)
at OutSystems.Scheduler.Core.TimerJob.Execute()
at OutSystems.Scheduler.Core.SchedulerProducerConsumer`1.Execute(Job job)

[2] Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)

[3] An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)



It seems it has problems with the action Snapshot_GetReactiveAndMobileScreens, if you have plenty of modules.



mvp_badge
MVP

Ok,

It seems that it consumes a lot of memory during the creation and ends up recycling the application-pool.

Increased the app-pool to 3.5Gb and it still failed.


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.