When I run orchestrations, some of them intermittently fail with an exception:
Exception while executing function: Orchestrator function 'x' failed: The activity function 'x' failed: "Failed to deserialize exception from TaskActivity: Unhandled exception while executing task: System.InvalidOperationException: RunAsync does not handle the function execution status FunctionsHostStoppingError.
at Microsoft.Azure.WebJobs.Extensions.DurableTask.TaskActivityShim.RunAsync(TaskContext context, String rawInput) in D:\a_work\1\s\src\WebJobs.Extensions.DurableTask\Listener\TaskActivityShim.cs:line 124
at DurableTask.Core.TaskActivityDispatcher.<>c__DisplayClass13_1.<b__2>d.MoveNext() in /_/src/DurableTask.Core/TaskActivityDispatcher.cs:line 178". See the function execution logs for additional details.
I've checked my app insights logs and I do not see any other underlying exceptions. What could be the issue?
Related
I'm using Error Handling in WorkFusion.
Is there a way to see the error message in the catch block i.e. exception occurred block.
How about using:
<log>exception_msg_var</log>
or
println exception_msg_var
exporting exceptions to datastore?
To get the error message in RPA Express, you can keep the code outside of exception handling and then, the software will through error message on its' own. Once you get the type of error (by running the bot once), you can put the solution in catch block by keeping the code inside exceptional handling feature.
I'm using CoreData in my app. Now add a new entry and try to save it. I don't know why but it fails with Thread 1: signal SIGABRT
This is my saving part:
var error: NSError? = nil
if !context.save(&error) {
abort()
}
It crashes in this line of code:
abort()
Does someone know why this happens and hoc I can solve it? I also use iCloud Sync if this could be a reason. Thanks a lot for your help!
Your code behaves exactly as intended. Google for "Unix abort".
NAME
abort - generate an abnormal process abort
SYNOPSIS
include
void abort(void);
DESCRIPTION
The abort() function causes abnormal process termination to occur, unless the signal SIGABRT is being caught and the signal handler does not return. The abnormal termination processing includes at least the effect of fclose() on all open streams, and message catalogue descriptors, and the default actions defined for SIGABRT. The SIGABRT signal is sent to the calling process as if by means of raise() with the argument SIGABRT.
The status made available to wait() or waitpid() by abort() will be that of a process terminated by the SIGABRT signal. The abort() function will override blocking or ignoring the SIGABRT signal.
RETURN VALUE
The abort() function does not return.
ERRORS
No errors are defined.
EXAMPLES
None.
APPLICATION USAGE
Catching the signal is intended to provide the application writer with a portable means to abort processing, free from possible interference from any implementation-provided library functions. If SIGABRT is neither caught nor ignored, and the current directory is writable, a core dump may be produced.
FUTURE DIRECTIONS
None.
SEE ALSO
exit(), kill(), raise(), signal(),
DERIVATION
Derived from Issue 1 of the SVID.
I am reproducibly getting an exception on this line
UIImage * image = [UIImage imageWithContentsOfFile:path]; // Always main thread
The exception is not fatal, if breakpoints are disabled the app continues normally. I presume the exception is caught in Apple's code.
The message logged is:
< Error >: ImageIO: CreateMetadataFromXMPBufferInternal
Threw error #11 (Acquire pthread write lock failed)
Stack-trace:
The code is accessing a file path that the ASI Networking library owns.
There is another background ASI thread thats checking for existence of the the URL string but I don't believe its actually writing anything to disk.
The code is iterates over 8 successfully, then fails on the 9th.
Anyone seen this issue before or know whats causing it?
all
the part of log :
** Reason for termination == **
{normal,
{gen_server,call,
[<0.9723.458>,
{create_jtxn_mon,
{player,34125,0,"gulexi",
why does it report error log when the reason is normal?
thanks for your help~~~
It seems like you made a call to a gen_server that exited with reason normal before it sent a response to the caller.
In general, if a gen_server exits with reason ServerExitReason during a call, gen_server:call will exit with the exit reason {ServerExitReason, {gen_server, call, [...]}}, even if ServerExitReason is normal. (See the source)
That is, the exit reason is not normal but {normal, ...}, and that's why you get a log message.
I have a project that runs perfect under windows xp.
Now I have tried to run it under Windows 7 and got there a lot of exceptions under Immediate window.
A first chance exception of type 'System.ArgumentNullException' occurred in Microsoft.VisualBasic.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in LP_Wizard.exe
A first chance exception of type 'System.ArgumentException' occurred in LP_Wizard.exe
A first chance exception of type 'System.NullReferenceException' occurred in LP_Wizard.exe
A first chance exception of type 'System.InvalidCastException' occurred in Microsoft.VisualBasic.dll
A first chance exception of type 'System.ArgumentNullException' occurred in Microsoft.VisualBasic.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in LP_Wizard.exe
A first chance exception of type 'System.InvalidCastException' occurred in Microsoft.VisualBasic.dll
A first chance exception of type 'System.ArgumentNullException' occurred in Microsoft.VisualBasic.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in LP_Wizard.exe
A first chance exception of type 'System.ArgumentNullException' occurred in Microsoft.VisualBasic.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in LP_Wizard.exe
Any idea what wrong with that Microsoft.VisualBasic.dll in windows 7 and how i correct that problem ?
Thanks a lot for help .
If you want to pinpoint where the exceptions are occurring, you can select the Debug->Exceptions menu item, and in the dialog that appears, check the first checkbox for "Common Language Runtime Exceptions". This will make the debugger break as soon as an exception occurs instead of only breaking on unhandled exceptions.
This is also one reason why it is generally a bad idea to catch generic exceptions unless you are clearly logging the information caught.
What is happening is the debugger can "see" exceptions as soon as they are raised (hence the "first chance") before any catch block is hit. Any exception which is not handled by a catch block is considered a "second chance" exception and will break normally.
If these exceptions aren't stopping the running of your application because they are unhandled then you are probably OK. Most of the time the exception is handled by code and this isn't a problem. The output is simply Visual Studio letting you know the exceptions were raised.
See the "Avoiding first chance exception messages when the exception is safely handled" question for some methods to reduce this if there are too many to ignore.
Are your in the debugger? Are these exceptions your program is handling? If so you need to find a setting that tells VB to supress warning you of handled exceptions. Maybey this was set when installed on XP but not when you installed on W7. See if this helps:
http://www.helixoft.com/blog/archives/24