Hi all,

We have just had a problem with steeply-degrading performance on a
development MCMS instance.  It appears to have been caused by a
debugging session on another MCMS instance that shares the same MCMS
database.  Is this expected behaviour?  To clarify, once a debug
session was started on server2 (different copy of the application
obviously), server1 would only serve a dozen or so, gradually slowing,
requests before becoming inoperative (no more requests serviced, login
not working).  IIS then had to be restarted on server1 but to clean
the problem entirely debugging had to stop on server2.

Is there some kind of transactional buildup that would occur under
these circumstances?

Chandy

[ Post a follow-up to this message ]

Hi Chandy,

what exactly did you debug? The SQL stored procedures?
A VS.NET projects?

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Chandy" <chandy@totalise.co.uk> wrote in message
news:5af0375a.0408190527.78b5c87f@posting.google.com...
> Hi all,
>
> We have just had a problem with steeply-degrading performance on a
> development MCMS instance.  It appears to have been caused by a
> debugging session on another MCMS instance that shares the same MCMS
> database.  Is this expected behaviour?  To clarify, once a debug
> session was started on server2 (different copy of the application
> obviously), server1 would only serve a dozen or so, gradually slowing,
> requests before becoming inoperative (no more requests serviced, login
> not working).  IIS then had to be restarted on server1 but to clean
> the problem entirely debugging had to stop on server2.
>
> Is there some kind of transactional buildup that would occur under
> these circumstances?
>
> Chandy

[ Post a follow-up to this message ]

Hi Chandy,

I wouldn't want to be debugging a development CMS instance that shares a
database with a production CMS instance.

Your Development instance may start updates and then not complete them until
you step onto the correct line of code and your production system may be
reading the data inbetween...

Maybe you should move to a multiple database configuration or debug in your
production website's downtime.

Regards
--
 ________________________________________


Angus Logan  (MCAD/MCDBA/MCP)
Lead Software Developer
Microsoft Application Solutions
Data#3 Limited
E angus_logan@data3.com.au
BLOG www.anguslogan.com
 ________________________________________


"Chandy" <chandy@totalise.co.uk> wrote in message
news:5af0375a.0408190527.78b5c87f@posting.google.com...
> Hi all,
>
> We have just had a problem with steeply-degrading performance on a
> development MCMS instance.  It appears to have been caused by a
> debugging session on another MCMS instance that shares the same MCMS
> database.  Is this expected behaviour?  To clarify, once a debug
> session was started on server2 (different copy of the application
> obviously), server1 would only serve a dozen or so, gradually slowing,
> requests before becoming inoperative (no more requests serviced, login
> not working).  IIS then had to be restarted on server1 but to clean
> the problem entirely debugging had to stop on server2.
>
> Is there some kind of transactional buildup that would occur under
> these circumstances?
>
> Chandy

[ Post a follow-up to this message ]

Hi Angus,

There are no production instances involved, however there are several
development instances which share the same developments MCMS database.
Makes things a bit awkward if only one developer at a time can debug
unless they all have seperate MCMS databases!

Chandy

"Angus Logan" <angus_logan@data3.com.au> wrote in message news:<u8upB7lhEHA.3992@TK2MSFTNGP1
1.phx.gbl>...[vbcol=seagreen]
> Hi Chandy,
>
> I wouldn't want to be debugging a development CMS instance that shares a
> database with a production CMS instance.
>
> Your Development instance may start updates and then not complete them unt
il
> you step onto the correct line of code and your production system may be
> reading the data inbetween...
>
> Maybe you should move to a multiple database configuration or debug in you
r
> production website's downtime.
>
> Regards
> --
>  ________________________________________

>
> Angus Logan  (MCAD/MCDBA/MCP)
> Lead Software Developer
> Microsoft Application Solutions
> Data#3 Limited
> E angus_logan@data3.com.au
> BLOG www.anguslogan.com
>  ________________________________________

>
> "Chandy" <chandy@totalise.co.uk> wrote in message
> news:5af0375a.0408190527.78b5c87f@posting.google.com... 

[ Post a follow-up to this message ]

Hi Stefan,

Just the VB.NET MCMS Template project.

Chandy

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message news:<etVUm8fhEHA.1156@T
K2MSFTNGP10.phx.gbl>...[vbcol=seagreen]
> Hi Chandy,
>
> what exactly did you debug? The SQL stored procedures?
> A VS.NET projects?
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...nagement+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "Chandy" <chandy@totalise.co.uk> wrote in message
> news:5af0375a.0408190527.78b5c87f@posting.google.com... 

[ Post a follow-up to this message ]

I have run with this configuration before and its been OK.

Multiple developers debugging at the same time backing onto the same
database.

--
 ________________________________________


Angus Logan  (MCAD/MCDBA/MCP)
Lead Software Developer
Microsoft Application Solutions
Data#3 Limited
E angus_logan@data3.com.au
BLOG www.anguslogan.com
 ________________________________________


"Chandy" <chandy@totalise.co.uk> wrote in message
news:5af0375a.0408260227.21bee97f@posting.google.com...
> Hi Angus,
>
> There are no production instances involved, however there are several
> development instances which share the same developments MCMS database.
>  Makes things a bit awkward if only one developer at a time can debug
> unless they all have seperate MCMS databases!
>
> Chandy
>
> "Angus Logan" <angus_logan@data3.com.au> wrote in message
news:<u8upB7lhEHA.3992@TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen] 
until[vbcol=seagreen] 
your[vbcol=seagreen] 

[ Post a follow-up to this message ]

Same to me.
I have never heard about such a problem.
I would suggest to open a support case to get this analyzed.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Angus Logan" <angus_logan@data3.com.au> wrote in message
news:u53P901iEHA.2340@TK2MSFTNGP11.phx.gbl...
> I have run with this configuration before and its been OK.
>
> Multiple developers debugging at the same time backing onto the same
> database.
>
> --
>  ________________________________________

>
> Angus Logan  (MCAD/MCDBA/MCP)
> Lead Software Developer
> Microsoft Application Solutions
> Data#3 Limited
> E angus_logan@data3.com.au
> BLOG www.anguslogan.com
>  ________________________________________

>
> "Chandy" <chandy@totalise.co.uk> wrote in message
> news:5af0375a.0408260227.21bee97f@posting.google.com... 
> news:<u8upB7lhEHA.3992@TK2MSFTNGP11.phx.gbl>... 
a[vbcol=seagreen] 
> until 
be[vbcol=seagreen] 
> your 
slowing,[vbcol=seagreen] 
login[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]