Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Distributed Applications / June 2005

Tip: Looking for answers? Try searching our database.

I need a pros help with this

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris - 18 May 2005 09:30 GMT
Hi,
I want to MSMQ in my ASP.net app. The app would pass the job to MSMQ and the
a service comp would pick it up from there and execute the job in database.
Now the stored proc in the database takes a while so is there a way not to
have the service comp not to pick up another job from MSMQ until the sp is
completed in the database. I want only one job to executed at a time because
multiple instance of the sp will use up a lot o ram on my server and really
slow the database.

Thanks
Klaus H. Probst - 19 May 2005 05:11 GMT
What's your question? If I understand correctly, your problem will be solved
by MSMQ, since it queues requests (obviously).

Or are you asking how to use MSMQ?

Signature

Klaus H. Probst, MVP
  http://www.simulplex.net/

> Hi,
> I want to MSMQ in my ASP.net app. The app would pass the job to MSMQ and the
[quoted text clipped - 6 lines]
>
> Thanks
Chris - 20 May 2005 01:04 GMT
I am confused as to where I should install MSMQ. I have it installed on my
domain controller. Do I need to also install it on the web server or just
have the asp.net app send the message to the msmq on the domain controller
and then my service comp will pickup message from the domain controller. Is
that how it should be done?

Thanks

> What's your question? If I understand correctly, your problem will be solved
> by MSMQ, since it queues requests (obviously).
[quoted text clipped - 15 lines]
> >
> > Thanks
Klaus H. Probst - 21 May 2005 22:51 GMT
It needs to be installed locally as well. Otherwise the client part won't
work.

Signature

Klaus H. Probst, MVP
  http://www.simulplex.net/

> I am confused as to where I should install MSMQ. I have it installed on my
> domain controller. Do I need to also install it on the web server or just
[quoted text clipped - 23 lines]
> > >
> > > Thanks
Ch. Hashir Ahmed - 16 Jun 2005 18:13 GMT
Have you proved that the database server is laging behind. I mean have u
really tested your application.

You can suspend the service comp thread which is picking the messages from
queue, but this is not a scalable solution because it will make service comp
the bottleneck in your app & your app won't be scalable any more. Trust the
DB server as Db servers are build for scalability, reliablity & all other
-bilities.

Have sufficient testing & collect evidence that doing so is the only solution.

> Hi,
> I want to MSMQ in my ASP.net app. The app would pass the job to MSMQ and the
[quoted text clipped - 6 lines]
>
> Thanks
Chris - 17 Jun 2005 05:45 GMT
The MSMQ works fine after hours or reading. I was basically looking for the
service comp to take one job at a time form MSMQ and process in database.

> Have you proved that the database server is laging behind. I mean have u
> really tested your application.
[quoted text clipped - 17 lines]
> >
> > Thanks

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.