I recently noticed my NSB log files where growing up significantly because of a warning I have never noticed before.
2017-03-21 12:17:50.554 WARN NServiceBus.Timeout.Hosting.Windows.TimeoutPersisterReceiver Failed to fetch timeouts from the timeout storage
System.NullReferenceException: La référence d'objet n'est pas définie à une instance d'un objet.
à NServiceBus.Timeout.Hosting.Windows.TimeoutPersisterReceiver.Poll(Object obj) dans C:\BuildAgent\work\3206e2123f54fce4\src\NServiceBus.Core\Timeout\Hosting\Windows\TimeoutPersisterReceiver.cs:ligne 90
à System.Threading.Tasks.Task.Execute()
2017-03-21 12:17:50.560 INFO NServiceBus.CircuitBreakers.RepeatedFailuresOverTimeCircuitBreaker The circuit breaker for TimeoutStorageConnectivity is now in the armed state
This warning appears every seconds so you can imagine the size of my log files.
I noticed this warning when I adjust the NServiceBus log level because I had several unexplained crash in my service. I have found that this warning makes my service crashing after a while causing a FatalExecutionEngineError exception (see screenshot below).
I am using NServiceBus 5.2.21.
Does anyone can help me getting rid of this warning?
I solved my problem using an older version of NServiceBus (5.2.14). Above this version, the problem appears and everything works fine from and below this version.
According to my tests, it seems that crashes don't appear when NServiceBus logging feature is disabled. As I am not using Timeouts in NServiceBus, everything works fine when logs are disabled. It looks like a conccurent access issue between thread occurs.
Maybe this bug has never been seen since this is an old version and as NServiceBus current version is 6.x (7.x coming), it has never been fixed.
This is due to a breaking change on the timeout contracts. Make sure that not only you are using the latest version of the Core, but also for the persistence.
Related
In relation to this post:
After upgrading from revit 21 to 22 in my company, we can no longer view anything else than the default 3D model in our forge viewer. Initially, i thought the issue arose due to this warning:
"Deprecated API usage: No "GlobalWorkerOptions.workerSrc" specified.".
However, i got that same message in the console of a working implementation i made today, leading me to believe that it has nothing to do with this warning at all.
However, i also see another warning:
"Warning: getOperatorList - ignoring errors during "GetOperatorList: page 0" task: "r: Cannot read properties of undefined (reading 'X')"."
I have tried creating a new nuxt app on Node version 14.9.0, implemented a forge viewer in accordance with the official v7 documentation, and the bug is no longer present.
I then tried to mimic that in my actual production app where the problem exists, by running it on Node version 14.9.0 instead of 10.0.0, getting rid of my entire forge implementation and implemented a simple viewer like above. That did not solve the problem, and i still see above warnings in the console.
The warning is thrown in pdf.worker.jss, which is loaded in via "webpack://adsk/node_modules/#adsk/pdfjs-dist/legacy/build/pdf.worker.jss".
I hope someone has a suggestion.
I have been trying to use just_audio (0.9.18) with the loudness enhancer and just_audio_background (0.0.1-beta.3) getting an error: UnimplementedError: androidLoudnessEnhancerSetTargetGain() has not been implemented.
I am using the provided Github effects example which runs as expected but throws the Unimplemented error if just_audio_background is added as per instructions. Is this a bug?
Not all features are supported on all federated implementations, and you get this error to indicate that that feature isn't supported. You could submit a feature request (as opposed to a bug report) to the project.
I tried looking for some descriptive answer but didn’t found one.
What I did
Upgraded NserviceBus from 5x to 7x
This implicitly upgraded nugets:
NserviceBus.RavenDb (3x to 5x)
RavenDb.Client (3.0 to 3.5.5)
Raven.Abstractions (3.5.5)
RavenDb client build is 35247. So cannot upgrade RavenDbClient nuget to higher version.
Error:
RunTime error. "System.MissingMethodException: Method not found: Raven.Abstractions.Data.BatchResult"
The service handling messages is also having some already processed RavenMigrations (inheriting from Migration). I tried to test them (by changing id and find out that Migrations crash with some error as shown in image underneath:
Scratching my head on this error for a while now. Any hints what could be wrong?
Note: This error was not happining with RavenDb.Client nuget 3.0
Running nest start
The module initialization fails silently without error at const app = await NestFactory.create<NestExpressApplication>(AppModule);
This seems to fail after the CqrsModule dependency is initialized. I dont see anything in the logger I have setup, would this be reported anywhere else?
It quits directly after the last line above.
The problem for me was using a newer version of node. Once I switched to the original node version in my project, I started getting errors.
I had the same issue and solved it after realising that I had a service that was calling itself in its constructor.
Once removed, everything started working back as usual.
I need help understanding an error why I'm seeing an error.
The feature api is already enabled with the correct ApiListener object, and Api logs are being updated in /var/lib/icinga2/api/log/current .
But I'm getting this error when I restart icinga2:
Error: Error while evaluating expression: The type 'ApiUser' is unknown: in /etc/icinga2/conf.d/api-users.conf: 1:0-1:20
I'm running version r2.3.10-1 of Icinga2 on Ubuntu.
Can someone explain what the problem is?
You are probably mixing the current snapshot packages with the released stable versions. The 'ApiUser' object is part of the upcoming Icinga 2 v2.4 release and only available in git master (and therefore snapshot packages as well as docs). The stable 2.3.x tree does not have that kind of configuration object type and therefore bails out with an error.
Remove that file or its content, you don't need it for 2.3.x.