I've found an article about the timeout, but I don't know which paramteter should be set to log me out after 10 minutes inactivity from the portal (by default it logs me out after 30 minutes). Where can I change this?
You need to set the session timeout in web.config:
<configuration>
<system.web>
<sessionState timeout="10" />
</system.web>
</configuration>
The above config fragment is just an example, please be aware that in your web.config there may be additional attributes on the sessionState node.
Please also make sure that the Idle Timeout of the app pool in IIS is set to 0 (meaning infinite, this is the recommended value), or to a huge amount so that the app pool does not recycle after a short period of idle time.
It appears to be in IIS on the application pool of the website. You can set it on Process Model Idle Time-Out as this article states.
Related
I have statistics enabled for a data source and can see that there are much more active connections than expected. I suppose some deployment on the server misses to call Connection.close() thus keeping connections active and not returning them to the pool.
I would like to ask for your advice regarding the method I can use to figure out who on server is keeping connections active. There are several deployments that are using a particular data source.
Profiler? JMX? anything else?
Thanks,
Valery
https://access.redhat.com/solutions/309913
Seems to be exactly what I was looking for.
Resolution To enable the cached connection manager (CCM) to identify a
connection leak:
Enable the CCM for the datasource. It defaults to true if it is not explicitly specified but you may set use-ccm="true" explicitly.
Verify that exists in the jca subsystem and set debug="true"
Setting debug="true" will:
Log an INFO message indicating that JBoss is "Closing a connection for
you. Please close them yourself" Generate a stacktrace for the code
where the leaked connection was first opened. Close the leaked
connection
I cannot seem to extend the 110 second timeout for requests to my Azure Web App. I have done the following in order to increase this limit, but with no success.
ASP.NET's HTTP request execution timeout (web.config):
<system.web>
<httpRuntime executionTimeout="600" />
</system.web>
IIS connection timeout (web.config):
<system.applicationHost>
<webLimits connectionTimeout="00:10:00" />
</system.applicationHost>
Kudu timeout before external commands are killed (site app setting):
SCM_COMMAND_IDLE_TIMEOUT = 600
What am I missing?
request timeout of 110s
It is very odd that your request timeout of 110s,From the Auzre official document, we could know that default timeout is about 4 minutes.It seems that we are not able to increase request timeout. The following is the snippet from the document. Please have a try to scale up and scale down back the App service plan. If still have the same issue, please connect to Azure support team for more help.
Azure Load Balancer has a default idle timeout setting of four minutes. This is generally a reasonable response time limit for a web request. If your web app requires background processing, we recommend using Azure WebJobs. The Azure web app can call WebJobs and be notified when background processing is finished. You can choose from multiple methods for using WebJobs, including queues and triggers.
+
WebJobs is designed for background processing. You can do as much background processing as you want in a WebJob. For more information about WebJobs, see Run background tasks with WebJobs.
Note :SCM_COMMAND_IDLE_TIMEOUT = 600 could use for your build process launches some command in the server side. But the request is timeout that will cause clients to get disconnected after 230 seconds, we could get more info from Azure Kudu Configurable settings.
We use JBoss 7.1 version in our environment. We have a scenario where one of the production databases was shut down for one hour due to a maintenance activity. Our JBoss application failed to automatically reconnect to that database after one hour and we had to manually restart the application to establish the connection.
Below are the database validation parameters we have defined in our code. Please let me know if I missed any parameter for automatic reconnection other than the below or if we have to make/add any changes/parameters to the existing.
<validation>
<check-valid-connection-sql>SELECT 1;</check-valid-connection-sql>
<validate-on-match>false</validate-on-match>
<background-validation>true</background-validation>
<background-validation-millis>180000</background-validation-millis>
</validation>
<background-validation-millis> ---> This parameter allows a connection checker to run for every three minutes as per our code and finds the availability of the DB connection.
Questions:
How long does this run for database connection?
Or, what is the maximum time/loops it will try for database connection?
Is there any default time it runs or will it run infinite times until the database comes back up?
I hope my questions are clear and please let me know if you need any more information.
I'm looking at this link and I read that <validate-on-match> is typically not used in conjunction with <background-validation>.
Try remove this tag and see what that gives.
i 'm working with asp.net 3.5 and i'm just upset with session handling of asp.net. here it's automatically log out from session period.
here is my web config session time out:
<sessionState mode="InProc" cookieless="false" timeout="20"/>
i just want to increase this time out for max as.
Is that possible for increase timeout="..." or buy default it's managed from iis machine.
Its better that you mention the time out in web.config file and it take timeout in minute not in sec.
I have a server running Windows 2003 R2 Enterprise Ediditon with Service Pack 2. I reset the Application Event Log Retention policy within EventVwr (right-click on Application, click the radio button next to "Overwrite events as needed".) A few hours later, somehow this setting got reset to "Overwrite events older than 7 days." This happened several times, so I started up RegMon to monitor what was changing this setting. The setting is located at HKLM\System\CurrentControlSet\Services\EventLog\Applicatin\Retention. I found out that services.exe is changing this setting on a regular basis. Can anyone tell me why services.exe would be automatically changing the Event Log retention policy, and how I can make it stop doing that?
The usual cause for this would be that the machine is part of a domain and Group Policy is being pushed down and applied by something running within services.exe.
That said - you'd probably be better asking this question at serverfault.com =)