You are correct. Open the connection just when you need to execute a
database command and then close it as soon as you're done. That way you
connection can be pooled.
> -----Original Message-----
> From: kenneth fleckenstein nielsen
> [mailto:kennethfleckensteinnielsen@discussions.microsoft.com]
> Posted At: Wednesday, December 29, 2004 2:35 AM
> Posted To: microsoft.public.dotnet.framework.webservices
> Conversation: restart webservice
> Subject: Re: restart webservice
>
> hmm, I developing in c# & .net, and open the session in the 'global'
class
> generated when you create a new webservice project. I open in
thefunction:
> protected void Session_Start(Object sender, EventArgs e)
> - you state that i should do it much later ? and that way can control
the
> licens use better. And catch exceptions thrown by the db better, and
wont
> have to force the app to restart.
>
> "Christoph Schittko [MVP]" wrote:
>
> > It sounds like you are storing database connections (or objects that
> > hold open database connections) in the session state? If that's the
case
> > you need to design your application to eliminate the root cause of
your
> > problems instead of addressing the symptom by killing the worker
> > process.
> >
> > You __have to__ follow the recommended usage for database
connections,
> > i.e. call open as late as possible, execute your SQL and
close/dispose
> > the connection. Otherwise you will see the problems you're
reporting.
> >
> > Killing the worker process will kill all sessions for all web
> > applications running in that instance. You can never be sure that
you
> > are not impacting other users of other applications when you just
kill
> > the process.
> >
> > HTH,
> > Christoph Schittko
> > MVP XML
> >
http://weblogs.asp.net/cschittko > >
> >
> > > -----Original Message-----
> > > From: kenneth fleckenstein nielsen
> > > [mailto:kennethfleckensteinnielsen@discussions.microsoft.com]
> > > Posted At: Tuesday, December 28, 2004 7:35 AM
> > > Posted To: microsoft.public.dotnet.framework.webservices
> > > Conversation: restart webservice
> > > Subject: Re: restart webservice
> > >
> > > I've just been looking around the user on my computer, ASPNET is
> > > appearently
> > > only used for running the aspnet_wp process, and i could set
> > appearently
> > > set
> > > som times to shorter than ever on my iss's properties.
> > > Which i guess will end the session and close the application and
> > retarting
> > > it again. ( and herby freeing licenses)
> > >
> > > "Christoph Schittko [MVP]" wrote:
> > >
> > > > What exactly do you mean when you say restart? You always get a
new
> > > > instance of your web service class for every new incoming
request.
> > Why
> > > > do you want to restart the service?
> > > >
> > > > You would have to restart the ASP.Net or the IIS worker process
> > which
> > > > would affect the availability of your web service and
potentially
> > other
> > > > web applications on that serve.
> > > >
> > > > Also you would need to run undo an account with administrator
> > > > privileges. Is that really something you want to do?
> > > >
> > > > HTH,
> > > > Christoph Schittko
> > > > MVP XML
> > > >
http://weblogs.asp.net/cschittko > > > >
> > > > > -----Original Message-----
> > > > > From: kenneth fleckenstein nielsen
> > > > > [mailto:kennethfleckensteinnielsen@discussions.microsoft.com]
> > > > > Posted At: Monday, December 27, 2004 4:14 AM
> > > > > Posted To: microsoft.public.dotnet.framework.webservices
> > > > > Conversation: restart webservice
> > > > > Subject: restart webservice
> > > > >
> > > > > hi guru's
> > > > > I want to restart my webservice when ever it throws an
exception
> > that
> > > > > isn't
> > > > > cought. can i do that by web.config or iss or how ??
> > > >
> > > >
> >
> >