Is there a way to disable recoveries from WARNING states (but keep the recovery messages from PROBLEM states?)
We only want to be notified when there is a PROBLEM with a service and when that service recovers. What happens is that each time the service enters a WARNING state and then recovers we get that RECOVERY notification. Any thoughts?
Thanks.
notification_options w,u,c
Related
I am using firestore with queries and i am getting data but something in network tab is loading none stop
as you can see its over a minute
should i be concerned about it?
It's hard to be certain without seeing the code that produces this problem, but most likely you're using a realtime listener (onSnapshot) in your code.
Such a listener keeps an active , open connection between the client and the server, so that the database can send a notification to the client when the data changes. The Chrome network tool shows this as a content download, because indeed data trickles in over this connection.
So likely what you're seeing is a normal part of Firestore's protocol for realtime, bi-directional communication between the client and server, but again.
The OPTION/POST Request is failing inconsistently with a console Error as err_timed_out. We get the issue inconsistently, it's only observed sometimes. Otherwise the request gets proper response from the back end. When it's timing out, the request doesn't even reach the server.
I have done some research on the stuff and found that due to maximum 6 connections to a resource restrictions it may wait for getting a connection released. But, I don't see any other requests pending ,all the other requests were completed.
In the timeline I can always see that it stalled for 20.00 seconds. Most of the time the time is same. But, it only shows that its been stalled for some time nothing else in the timeline.
The status of the request shows failed ERR_Connection_Timed_Out. Please help.
The Network Timing
Console Error
I've seen this issue when I use an authenticated proxy server and usually a refresh of the page fixes it.
Are you using an authenticated proxy server where you are seeing this behavior? Have you tried on a pc with direct access (i.e. without proxy) to the Internet?
I've got the same problem when I choose another ISP. I thought I would have only to put my new ID and password, but it wasn't the case.
I have an ADSL modem with a dry loop.
All others services were fine (DNS resolution, IP telephony, FTP, etc).
I did a lot of tests (disable firewall, try some others navigator, try under Linux, modem default factory, etc) none of those tests were successful.
To resolve the problem ERR_TIMED_OUT, I had to adjust the MTU and MRU values. I put 1458 rather than 1492, which is the default value.
It works for me. Maybe some ISPs use different values. Good luck.
I am using Service Broker external activation. I have created event notification for queue (QUEUE_ACTIVATION). Currently making a lots of tests and sometimes my queue gets deactivated.
After enabling queue Event notification does not work anymore and external activator does not start console app.
i found this, but that seems to be something else as "select * from sys.event_notifications" shows that there is already created event notification.
I do drop and create again the same event notification to make it work, but it seems to be wrong..
How can i detect automatically that event notification is not working?
You probably don't RECEIVE and commit the notification from the monitoring queue, causing the notification to go into NOTIFIED state but never transitioning to RECEIVES_OCCURING. See Understanding Queue Monitors.
I am trying to set up a new domain with only one domain controller.
My DNS role seems to be getting event warning 4013 and my Active Directory role is getting events 2886, 1844, 1463 and 614. I have tried just about everything I could search for and think of for getting rid of these errors. I would appreciate any suggestions.
For events 4013 you should not see this error at all, I run one domain controller with DNS also. This is stating that you have an issue with the way DNS was configured. You only see this if DNS has issues. As for 2886 it has to do with LDAP you can ignore this event if you wish or you can make the changes to have the warning go away.
Check out this forum for help what 2886.
http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/57f4048a-2743-453f-93a3-765de01d0ad0
If I am correct, I will always get these 2 warnings occasionally since it is only a single domain controller on the domain hosting its own DNS service. These warnings do not seem to impede any performance on the server itself.
We've got a program that runs on our network (it's published to our app-server and run from there as well) and I'd like to show an Alert window (by DevExpress) to all users who are running the app, whenever a new item is entered. Obviously the code would go in the Save event but when I put it in there, it only works for me, meaning I'm the only user who sees the alert, no one else. The same can be said for other users...they only see the alert when they enter it, not when someone else enters it.
Any ideas as to how this can be accomplished?
You can use straight MSMQ to put on a message and have clients listen on that queue. You can also use NServiceBus (which does use MSMQ) that has a publish subscribe framework built in. This way your clients can subscribe to all clients or certain clients.
Since WinXP, Vista and Win7 have MSMQ it just maybe a matter of installation and configuration (which NServiceBus will do 'automatically' for you)
You could try with Comet if you want true push mechanism. Otherwise you could use periodical pull using setInterval and ajax calls. However, both techniques have some performance repercussions.