I have a console application which consumes at most 5Gb RAM while running. I want to initiate this application using windows scheduler. The problem is windows scheduler closes the application when it reaches 400-500mb of RAM usage. I have also changed the priority of the app from 7 to 0 in the task's XML configuration but seen no improvement.
I have received the following error message while trying to run the application.
any help?
error message
Related
We Just ran into a problem with our website. We are running a Oracle 12c database and using IIS 8 on a Windows 12 Azure server. ODP.NET is the provider we use. The website is build in C# and run as a 64bit web application.
For Whatever reason, Oracle doesn't release our connections, and after a while we got an Oracle Error :
ORA-12520: TNS:listener could not find available handler for requested type of server
We reviewed all of our connections string, adding :
Min Pool Size=10;Max Pool Size=100;Connection Lifetime=120;Connection Timeout=60;Incr Pool Size=5; Decr Pool Size=2
We more than double the MAX Process and Sessions that was defined in the Oracle configuration.
It's help but only in delaying the problem.
For now what we have done is a batch file which run every 10 minutes and kills all inactive sessions that are still there after 30 minutes (ALTER SESSION KILL....IMMEDIATE).
That's where we are, we have enable the ODP.NET trace and waiting to look at it tomorrow, but by this time, what can cause this problem?
Finally what I found in the ODP.NET Trace was
TID: dac (ERROR) Oracle error code=28002; Oracle msg=ORA-28002: the password will expire within 6 days
Seems that this Error doesn't stop the access to the DB but hang the session in the pool.
After we fixed that, all was back to normal.
An Eclipse RCP application crashes in the jprofilerti.dll code once I move the app from relatively idle status to full operation.
Some initial profile results are available back on the remote GUI session. This suggests that the configuration of Jprofiler GUI, Jprofiler agent, and network settings is ok.
I wonder if the crash occurs due to buffer overruns. I ask because the network link between the remote JVM and the near laptop JProfiler GUI is very poor with a very low effective bit rate. Is it possible that the target JVM will crash if the remote GUI is too slow about consuming buffered profiling data?
I have a weblogic server running in clustered mode with one admin server(A) and 3 managed servers(M1,M2,M3). A and M1 reside on the same machine. In the weblogic, I am running a multi-tiered J2EE application, where an asynchronous batch process is invoked from the UI. We noticed, that when the M1 is killed (due to server load etc) - and restarted, the batch process that was invoked continues to run. My assumption would have been that the batch process also starts within the same JVM as M1. I have checked all the java processes running on the box, but none of them point to executing this batch in a separate JVM.
Appreciate your help !
Contrib
I have a w3wp.exe that is restarting on my IIS server (see specs below). Memory gradually climbs to ~3G then it randomly restarts itself about every 1-2min.
Memory Usage:
The odd thing is that once this memory drop (what looks like a restart - btw...the app pool does not get recycled/restarted) happens GET requests are queued but then serviced as soon as the service warms/starts up (causing a delay in responses to our clients - who were initially reporting delayed reponse times on occasion).
I have followed this link to get a stack dump once the .exe restarts (private bytes go to ~0) but nothing gets logged (no .dmp file) with diag debug once the service restarts.
I see tons of warnings in my webserver (IIS) log but that's it:
A process serving application pool 'MyApplication' suffered a fatal
communication error with the Windows Process Activation Service. The
process id was '1732'. The data field contains the error number.
ASK: I'm not sure if this is a memory limitation, if cacheing is not playing well with my threads/tasks, if cacheing is blowing up, if there is watchdog service restarting my application, etc,. Has anybody run across something similar with w3wp.exe restarting? It's hard to tell because diagdebug is not giving me a dump once it restarts.
SPECS:
MVC4 Web API servicing GET requests (code is debug build with debug=true)
Uses MemoryCache with Model and Business Objects with cache eviction set to 2hrs...uses
Task (TPS) for each new request.
Database: SQL Server 2008R2
Web Servers: Windows Server 2008R2 Enterprise SP1 (64bit, 64G RAM)
IIS 7.5
One application pool...no other LOB applications running on this server
Your first step is to reproduce the problem in your test environment. Setup some kind of load generation app (you can write it yourself pretty easily) and get the same problem happening. Then turn off debug in web.config and see if that fixes the issue. Then change it to be a release build and test again.
I've never used memorycache - try reducing the cache eviction time or just turn it off and see if that fixes the issue. Good luck :)
My environment: Windows Server 2008, IIE 7.0, ASP.NET
I developed a Silverlight client.
This client gets updates from the ASP.NET host through a WCF web service.
We get 100% CPU usage and connection drops when we have a very low number of users (~50).
The server should clearly be able to handle a lot more than that.
I ran some tests on our DEV server and indeed 100 requests / s maxes out the CPU.
What's odd is that even if the service is replaced by a dummy sending back hardcoded data the service still maxes out the CPU.
The thread count looked very low at about 20 so I thought there was some contention somewhere.
I changed all configuration options I could find to increase the worker threads (processModel, httpRuntime and the MaxRequestsPerCPU registry entry).
Nothing changed.
Then I stopped the IIS server and ran the web service as a console (removing all the ASP authentication references).
The service maxed out the CPU as well.
Then comes the magic part: I killed the console app and restarted IIS and now the service runs a 5-60% CPU with 100 requests / s and I can see 50+ worker threads.
I did the same thing on our preprod machine and had the same magic effect.
Rebooting the machines keeps the good behaviour.
So my question is: what happened to fix my IIS server? I really can't understand what fixed it.
Cheers.
Find out the root cause of the high CPU usage, and then you can find a fix,
http://support.microsoft.com/kb/919791