Server Application Unavailable error when result set is big1

[Ricardo]

Hi, he has a problem at the moment w/ a datagrid in asp.net. There's
about 10000 rows and 25 columns; when it loads there is an error that
says the server application is unavailable. He can't do paging because
the client won't let him.

[Rahul Soni]

Hi Recardo,

Have a look at the event viewer and let me know the Event ID and message of
the error in your application event logs generated when you get that error.

That would help to know if it is an application crash, deadlock etc and then
I may be able to help you out.

That being said, it is never ever a good idea to retrieve such large number
of records. It is like inviting troubles, this one being just the first of
them!!
--
Thanks,
Rahul Soni

--->The secret to creativity is knowing how to hide your sources<---

"Ricardo" wrote:

Hi, he has a problem at the moment w/ a datagrid in asp.net. There's
about 10000 rows and 25 columns; when it loads there is an error that
says the server application is unavailable. He can't do paging because
the client won't let him.

[Patrice]

I would check the size of the response. IMO this is just not realistic for a
web application...

--

"Ricardo" <ri*************@gmail.com> a écrit dans le message de
news:11**********************@g14g2000cwa.googlegr oups.com...

Hi, he has a problem at the moment w/ a datagrid in asp.net. There's
about 10000 rows and 25 columns; when it loads there is an error that
says the server application is unavailable. He can't do paging because
the client won't let him.

[Ricardo]

the Event id its:
Tipo de suceso: Error
Origen del suceso: ASP.NET 1.1.4322.0
Categoría del suceso: Ninguno
Id. del suceso: 1001
Fecha: 01/12/2005
Hora: 06:28:27 p.m.
Usuario: No disponible
Equipo: COSAPI1
Descripción:
aspnet_wp.exe (PID: 2056) was recycled because memory consumption
exceeded the 151 MB (60 percent of available RAM).
thanks...

[Rahul Soni]

Hey Ricardo,

That implies that you have just around 256MB of RAM. And trying to fetch
that many records is an overkill.

At this point three things could be tried...
1) Increasing your physical RAM could be the best approach (if you really
can't do paging)
2) You can try giving debug="false" in your web.config file for that
application and see if that helps.
3) Increase the memoryLimit="120" in the Process model of your
machine.config so that it uses the virtual memory space. REALLY NOT
RECOMMENDED. Still, the reason to mention here is because you will not get
memory recycles, although, everything should be painfully slow and the
application could hang!!!

<processModel enable="true" timeout="Infinite" idleTimeout="Infinite"
shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000"
restartQueueLimit="10" memoryLimit="60" webGarden="false"
cpuMask="0xffffffff" userName="System" password="AutoGenerate"
logLevel="Errors" clientConnectedCheck="0:00:05"
comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:03:00" maxWorkerThreads="20" maxIoThreads="20"/>

Nothing much is there that could be done on that :-(

--
Thanks,
Rahul Soni

--->The secret to creativity is knowing how to hide your sources<---

"Ricardo" wrote:

the Event id its:
Tipo de suceso: Error
Origen del suceso: ASP.NET 1.1.4322.0
CategorÃ*a del suceso: Ninguno
Id. del suceso: 1001
Fecha: 01/12/2005
Hora: 06:28:27 p.m.
Usuario: No disponible
Equipo: COSAPI1
Descripción:
aspnet_wp.exe (PID: 2056) was recycled because memory consumption
exceeded the 151 MB (60 percent of available RAM).
thanks...