topic Re: Bug with SectionImpl class and others???? in Alfresco Archive

Bug with SectionImpl class and others????

qsdmv — Thu, 25 Aug 2011 14:21:52 GMT

We are in highly multi-user environment. Recently we keep getting 500 or duplicate sections issues (randomly). But I could not duplicate from my local machine which is single user environment:1). Case one: We have section, and sub-sections under this section. Inside SectionImpl class, two properties

Re: Bug with SectionImpl class and others????

bremmington — Thu, 25 Aug 2011 14:39:41 GMT

Thanks for the report. It's not something we've seen in testing and neither has it been reported before, but we will certainly look into it. Again, please would you let me know exactly which version you're on? The options for the 3.4 stream are:
- Community 3.4.a, 3.4.b, 3.4.c, 3.4.d, 3.4.e
- Enterprise 3.4.0, 3.4.1, 3.4.2, 3.4.3

Re: Bug with SectionImpl class and others????

qsdmv — Thu, 25 Aug 2011 15:11:59 GMT

Enterprise 3.4.0
Thanks for quick response

Thanks for the report. It's not something we've seen in testing and neither has it been reported before, but we will certainly look into it. Again, please would you let me know exactly which version you're on? The options for the 3.4 stream are:
- Community 3.4.a, 3.4.b, 3.4.c, 3.4.d, 3.4.e
- Enterprise 3.4.0, 3.4.1, 3.4.2, 3.4.3

Re: Bug with SectionImpl class and others????

qsdmv — Sat, 27 Aug 2011 23:34:16 GMT

Deeply we did other tests. Whenever we modify or create new section, we got more problems

Enterprise 3.4.0
Thanks for quick response

Thanks for the report. It's not something we've seen in testing and neither has it been reported before, but we will certainly look into it. Again, please would you let me know exactly which version you're on? The options for the 3.4 stream are:
- Community 3.4.a, 3.4.b, 3.4.c, 3.4.d, 3.4.e
- Enterprise 3.4.0, 3.4.1, 3.4.2, 3.4.3

Re: Bug with SectionImpl class and others????

bremmington — Fri, 16 Sep 2011 08:05:11 GMT

I have committed a change to HEAD that I believe will address this issue, and also brought it into the 3.4 stream so it will be in the 3.4.5 release. I've also sent you a private message to follow it up.