Admin Fastnet
Rank: #70434
520Views
14Comments
PerformanceProbe - The operation was canceled
Question

After our recent upgrade to Version 11, we are getting the following REST error from the Performance Probe, any assistance of suggestion will be appreciate to resolve this issue:

eSpaceVer: 0 (Id=2906, PubId=0, CompiledWith=11.0.212.3)
RequestUrl: https://xxx.xxx.xxx.xxx/PerformanceProbe/rest/BeaconInternal/WebScreenClientExecutedEvent (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/PerformanceProbe-73-131995433540583602
FilePath: C:\...\PS\running\PerformanceProbe.01429902314\
ClientIp: xxx.xxx.xxx.xxx
Locale: en-US
DateFormat: yyyy-MM-dd
PID: 3712 ('w3wp', Started='2019/04/11 08:52:03 PM', Priv=2243Mb, Virt=16396Mb)
TID: 100
Thread Name: 
.NET: 4.0.30319.42000


The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Net.Http.HttpContentExtensions.<ReadAsAsyncCore>d__0`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.ModelBinding.FormatterParameterBinding.<ExecuteBindingAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.HttpActionBinding.<ExecuteBindingAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()

0
0
on 2019-04-26
Copy link to comment
Eduardo Jauch
mvp_badge
MVP
Rank: #6

Hi, 

What application this module is part of? 

You upgrade from version 10 to 11 or from 11.minor version to a 11. Newer version? 

Cheers 

0
0
on 2019-04-26
Copy link to comment
Admin Fastnet
Rank: #70434

We upgrade from 10 to 11. From what I figured out the Performance Probe sends information to Lifetime for Analytics. Attached is a screenshot of the error log.

Capture.PNG

0
0
on 2019-04-26
Copy link to comment
Eduardo Jauch
mvp_badge
MVP
Rank: #6

Hello, 

I don't have experience with this error, but being an upgrade error on what seems to be a native feature of the application, I recommend you to open a support ticket, as this shouldn't be happening. 

I'll try to see if someone else has encountered this problem before. 

Cheers

0
0
on 2019-04-26
Copy link to comment
sadhanshu arora
Rank: #0

I feel this problem is related to multithreading in OS. I hope it resolve your issue.

0
0
on 2019-04-26
Copy link to comment
Tony Abedini
Rank: #37285

@admin fastnet:  Did you open a ticket?  I'm having the same issue in 11, and Lifetime Analytics doesn't show any data for us.

1
0
on 2019-08-23
Copy link to comment
Gerrit van Heusden
Rank: #34895

Tony Abedini wrote:

@admin fastnet:  Did you open a ticket?  I'm having the same issue in 11, and Lifetime Analytics doesn't show any data for us.


Hi Tony,


We're experiencing the same issue. Have you found a solution yet?


0
0
on 2019-09-20
Copy link to comment
Jim Crawford
Rank: #5480

Bump,


We're experiencing this too.

0
0
on 2019-09-26
Copy link to comment

We are experiencing the same issue.

Has anyone found out why this is happening?


0
0
on 2019-10-15
Copy link to comment
Ruben Olivier
Rank: #10126

Sæunn Sif Heiðarsdóttir wrote:

We are experiencing the same issue.

Has anyone found out why this is happening?



Nothing that resolved the issue, Logged a ticket and the only explanation they found was the page timed out before a response could be send.

0
0
on 2019-10-15
Copy link to comment

Ruben Olivier wrote:

Sæunn Sif Heiðarsdóttir wrote:

We are experiencing the same issue.

Has anyone found out why this is happening?



Nothing that resolved the issue, Logged a ticket and the only explanation they found was the page timed out before a response could be send.

Any update on this issue? We have the same issue here after an upgrade from 10 to 11.


0
0
on 2020-03-17
Copy link to comment
Ruben Olivier
Rank: #10126

Annemarie Sonnenberg wrote:

Ruben Olivier wrote:

Sæunn Sif Heiðarsdóttir wrote:

We are experiencing the same issue.

Has anyone found out why this is happening?



Nothing that resolved the issue, Logged a ticket and the only explanation they found was the page timed out before a response could be send.

Any update on this issue? We have the same issue here after an upgrade from 10 to 11.


Unfortunately not


0
0
on 2020-03-17
Copy link to comment
Ilkka Ruuskanen
Rank: #18488

Any updates on this error?

Also we are now having it after platform upgrade from version 10 to 11.

0
0
on 2020-06-02
Copy link to comment
José Queirós
Rank: #318

Ilkka Ruuskanen wrote:

Any updates on this error?

Also we are now having it after platform upgrade from version 10 to 11.

This is not a problem and something I wouldn't stop any upgrade because of it. I do experience it as well and the support, being helpful, couldn't troubleshoot it easily either. 

My belief, is that it is an error that users were having already before, in some specific scenarios in our applications, and, in one of the upgrades of the platform 11 the error started to be successfully making its way into the Service center logs. (maybe it was a bug there error wasn't so noticeable before?)

Having opened a support ticket this was the response:

After checking the logs provided, we could check that the error message in the Production environment is always associated with the following URL: https://yourdomain/PerformanceProbe/rest/BeaconInternal/WebScreenClientExecutedEvent (Method: POST)  

The Performance Probe main purpose is to collect performance metrics using an API called Performance Monitoring API. You can find more information here.

By looking at the error stack, there is not much information we can retrieve. It indicates the request was cancelled, which could be caused by a variety of reasons, but unfortunately, the stack does not provide us with many clues on what could be the cause. For instance, this thread suggests that the client closed the request connection before the server could respond.

Taking this into consideration, since this does not have signs of being platform-related, we can only suggest you use Wireshark in order to analyze the traffic and better understand what can be cancelling the requests.

- by Outsystems support


From this response, it seems that I could be anything from application bug to network. if it prevents that post to be made at the beginning of each page request then it gets logged as such. 

I suggested that it could be muted somehow just not to fill some logs with errors that, in my view, should be a warning. 

Bear in mind, that in my case the error happened in very small numbers, thousands of requests daily but only 5 to 20 errors get logged on a normal day.

Hoped that helped someone. 

0
0
on 2020-06-09
Copy link to comment
Ajay Andrew
Rank: #26570

We are experiencing the same issue.

Has anyone found out why this is happening?

Regards

Ajay A

0
0
on 2020-11-20
Copy link to comment