|
Home > Archive > WebSphere Commerce suite > August 2006 > DataBeanManager.activate IOException
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 |
DataBeanManager.activate IOException
|
|
|
| I'm seeing this exception:
2005.04.22 10:51:22.541 DataBeanManager activate CMN0419E: The following IO Exception occurred during processing: "{0}".
I've found that you will get this exception on the category pages (CategoryDisplay) and product detail page (ProductDisplay) if you click the refresh button in your brower multiple times as the page is loading. To reproduce, go to ProductDisplay, and sta
rt refreshing your browser quickly.
Has anyone else experienced this? It doesn't seem to affect the site (the page actually loads after you quit clicking refresh), but it litters your System.out which is NOT something you want on a production server.
Does anyone know how to fix this? Am I missing a fix?
| |
| George Niece 2005-04-25, 5:58 pm |
| Which version and fixpack level are you on?
<steve.justin@haverstickconsulting.com> wrote in message news:1
152629486.1114185749265.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> I'm seeing this exception:
>
> 2005.04.22 10:51:22.541 DataBeanManager activate CMN0419E: The following
IO Exception occurred during processing: "{0}".
>
> I've found that you will get this exception on the category pages
(CategoryDisplay) and product detail page (ProductDisplay) if you click the
refresh button in your brower multiple times as the page is loading. To
reproduce, go to ProductDisplay, and start refreshing your browser quickly.
>
> Has anyone else experienced this? It doesn't seem to affect the site (the
page actually loads after you quit clicking refresh), but it litters your
System.out which is NOT something you want on a production server.
>
> Does anyone know how to fix this? Am I missing a fix?
>
>
| |
|
| Thanks for the reply George. We are at fick pack level 3. I realize that fp 4 just came out, but in looking through the fixes included in that, I don't see anything related to this problem. I will apply this soon.
Can you replicate this error? Try hitting refresh repeatedly on the Product Detail page (ProductDisplay). It occurs randomly in different <wcbase:useBean> tags depending on how quickly I hit refresh.
| |
| Robert Brown 2005-04-27, 2:49 am |
| > I'm seeing this exception:
>
> 2005.04.22 10:51:22.541 DataBeanManager activate CMN0419E: The following IO Exception occurred during processing: "{0}".
>
> I've found that you will get this exception on the category pages (CategoryDisplay) and product detail page (ProductDisplay) if you click the refresh button in your brower multiple times as the page is loading. To reproduce, go to ProductDisplay, and s
tart refreshing your browser quickly.
>
> Has anyone else experienced this? It doesn't seem to affect the site (the page actually loads after you quit clicking refresh), but it litters your System.out which is NOT something you want on a production server.
>
> Does anyone know how to fix this? Am I missing a fix?
I can reproduce the error here on v5.6 FP3. Even commands like
PrivacyView are affected. Strange...
R
| |
|
| Ok. It makes me feel better that I'm not the only one seeing this!
I think it will happen on any page using <wcbase:useBean>, because it ultimately uses the DataBeanManager.activate() method. The PrivacyView includes the header and sidebar which I think both use the <wcbase:useBean> to populate beans.
I didn't see it before we went live, but now that it's in production I think users that may have to wait on a page to load are impatient and click refresh.
| |
| Robert Brown 2005-04-27, 5:58 pm |
| Correct, if you remove the header, sidebar, and footer includes the
error cannot be reproduced. v5.4 and prior should have had only
scriptlet code in the JSPs so doubt those versions of WC are affected.
R
> Ok. It makes me feel better that I'm not the only one seeing this!
>
> I think it will happen on any page using <wcbase:useBean>, because it ultimately uses the DataBeanManager.activate() method. The PrivacyView includes the header and sidebar which I think both use the <wcbase:useBean> to populate beans.
>
> I didn't see it before we went live, but now that it's in production I think users that may have to wait on a page to load are impatient and click refresh.
| |
|
| I am also facing same problem. I/O exception is reported in log file but I am not able to reproduce the bug.
Did anyone find any solution to this problem??
quote:
Originally posted by Robert Brown
Correct, if you remove the header, sidebar, and footer includes the
error cannot be reproduced. v5.4 and prior should have had only
scriptlet code in the JSPs so doubt those versions of WC are affected.
R
> Ok. It makes me feel better that I'm not the only one seeing this!
>
> I think it will happen on any page using <wcbase:useBean>, because it ultimately uses the DataBeanManager.activate() method. The PrivacyView includes the header and sidebar which I think both use the <wcbase:useBean> to populate beans.
>
> I didn't see it before we went live, but now that it's in production I think users that may have to wait on a page to load are impatient and click refresh.
|
|
|
|
|