|
Home > Archive > Commerce Server General > June 2006 > Internal error occurred in 3rd party provider
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Internal error occurred in 3rd party provider
|
|
| Davidlev 2006-06-06, 1:22 am |
| Hi,
I have been trying to deploy a CS 2002 FP1 implementation and have run
across a serious problem. Apparently, when the site is put under some level
of load, the CPU begins to spike at 100% for the IIS Worker Process and the
site becomes completely unresponsive. When we implemented a error handler to
catch the errors, at the time of the cpu spike, we began receiving a bunch of
errors relating to the Profile System. Specifically, we received: Internal
error occurred in 3rd party provider when trying to invoke GetProfileByKey
and a few other methods. Can someone please help us in trying to identify the
root cause of this issue.
Thanks,
David
| |
|
| Hi,
Sounds as though you haven't turned caching on
Check your web.config and find a line that looks like the one below
<application siteName="yoursitename" debugLevel="Debug"/>
Set this to debugLevel="Production".
Be warned that this will implement page level caching. While this is
fast, if you have a basket value on each page of your site it will
cache this to.
Also check your database and see if its under just as much load as your
website.
Rory
Davidlev wrote:
> Hi,
> I have been trying to deploy a CS 2002 FP1 implementation and have run
> across a serious problem. Apparently, when the site is put under some level
> of load, the CPU begins to spike at 100% for the IIS Worker Process and the
> site becomes completely unresponsive. When we implemented a error handler to
> catch the errors, at the time of the cpu spike, we began receiving a bunch of
> errors relating to the Profile System. Specifically, we received: Internal
> error occurred in 3rd party provider when trying to invoke GetProfileByKey
> and a few other methods. Can someone please help us in trying to identify the
> root cause of this issue.
> Thanks,
> David
| |
| Ravi Shankar 2006-06-06, 1:20 pm |
| Hi Davidlev,
Depending on what all (IIS, SQL and such) running on your machine, you should
1. create a separate Application Pool for your application
2. set process recycling parameters for this app pool - This will cause an
process restart, typically start another process and hand over new requests
to that.. and close the existing process once all current request are done...
3. Do a perfmon using ASP.Net + Process+ System counters to identify the
bottlenecks (maybe you are running out of memory).
--
Ravi Shankar
"Davidlev" wrote:
> Hi,
> I have been trying to deploy a CS 2002 FP1 implementation and have run
> across a serious problem. Apparently, when the site is put under some level
> of load, the CPU begins to spike at 100% for the IIS Worker Process and the
> site becomes completely unresponsive. When we implemented a error handler to
> catch the errors, at the time of the cpu spike, we began receiving a bunch of
> errors relating to the Profile System. Specifically, we received: Internal
> error occurred in 3rd party provider when trying to invoke GetProfileByKey
> and a few other methods. Can someone please help us in trying to identify the
> root cause of this issue.
> Thanks,
> David
>
| |
| Davidlev 2006-06-07, 1:20 am |
| Rory,
Thanks for the reply.. Now that I have put the site in production mode, it
seems as though I am now inadvertantly merging profiles for the users of the
site. Its like I have 1 profile object and all the users of the site are
sharing it... Any ideas?
Thanks!
David
"Rory" wrote:
> Hi,
>
> Sounds as though you haven't turned caching on
>
> Check your web.config and find a line that looks like the one below
>
> <application siteName="yoursitename" debugLevel="Debug"/>
>
> Set this to debugLevel="Production".
>
> Be warned that this will implement page level caching. While this is
> fast, if you have a basket value on each page of your site it will
> cache this to.
>
> Also check your database and see if its under just as much load as your
> website.
>
> Rory
>
> Davidlev wrote:
>
>
| |
|
| Hi Davidlev,
I am guessing that when a user logs into your site they are greated by
a message on all the pages saying something like Welcome <username>
and you have 23.12 worth of products in your basket?
If this is the case then the page level caching that is happening when
you turn on production mode is basically caching the site for the first
user who visits the site. So every user afterwards sees the cached
version of the site and this includes basket values and greeting
messages to the first user as warned in my previous post:
"Be warned that this will implement page level caching. While this is
fast, if you have a basket value on each page of your site it will
cache this to"
What to do the options?
1) Leave your site in production mode and go to the following bit of
code in your web.config.
<OutputCaching>
<Param name="EnableCaching" value="true" type="System.Boolean"/>
and set the value to false and see if this makes a difference.
2) If you have the users basket value on each page and a greeting
message specific to that user then it is probably best to turn off page
caching and make use of ASP.NET fragment caching hooked to a dependency
file. This will require a bit of work finding the parts on your site
that would put the most strain on the site hopefully they are in
seperate usercontrols and try caching these to see if it makes a
difference.
3) If there are only a few pages that you identify the user on and
display messages and basket information to the user. Then remove these
pages from being cached by placing an entry into the Global.asax.cs (I
think this was the file you will need to check this).
Before you try any of the above, find out if turning on production mode
has made any difference to the CPU utilization.
Hope that helps, remember that when testing the above always to backup
files you have changed and to make change on a non production system to
test it first. Remember changing the web.config resets the app and can
cause issues for users who are in the process of purchasing on your
site.
Rory
Please note that all infomation is provided without warranty and is
used at your own risk.
Davidlev wrote:[vbcol=seagreen]
> Rory,
> Thanks for the reply.. Now that I have put the site in production mode, it
> seems as though I am now inadvertantly merging profiles for the users of the
> site. Its like I have 1 profile object and all the users of the site are
> sharing it... Any ideas?
> Thanks!
> David
>
> "Rory" wrote:
>
|
|
|
|
|