David Sean Taylor wrote:
Ate Douma (JIRA) wrote:
There was a refactoring done a while back that removed the threaded aggregation by default:Page Aggregation using STRATEGY_PARALLEL severly broken -------------------------------------------------------
Key: JS2-226
URL: http://issues.apache.org/jira/browse/JS2-226
Project: Jetspeed 2
Type: Bug
Components: Aggregation Versions: 2.0-dev/cvs, 2.0-M2 Environment: Tomcat 5.0.28
Reporter: Ate Douma
Assigned to: Ate Douma Priority: Critical
While trying to evaluate the status of JS2-17 I tested PageAggregation with PageAggregatorImpl.STRATEGY_PARALLEL and the effect is a total breakdown!
I'll look into this AFTER the M2 release.
Not sure if the current problem is related to JS2-17 but I'll check that too.
http://cvs.apache.org/viewcvs.cgi/jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PageAggregatorImpl.java?r1=1.18&r2=1.19&diff_format=h
I know the purpose of the refactoring was to make the improve the aggregator, but not sure why it removed (and broke) multithreading
My vote is to hold the release until this is fixed
-1 on the M2 release until multithreaded aggregation (which worked in M1) is fixed
I'm quite unhappy with this if it means not being able to do the M2 release this weekend... (or do you expect it to be fixed within the next 24 hours?).
Although I agree this is a serious problem and I set its priority to Critical accordingly, I don't think it is, nor should be Blocking for the M2 release.
As it is, we have a workaround, namely using (the default configured) STRATEGY_SERIAL. If PARALLEL rendering worked in M1 (I don't know, never tested it out) then indeed it is a setback, but we have many, many improvements and fixes in cvs ready which I want (and need) to have released.
There are other serious problems not resolved either which I personally would consider even more important than this one because there are no workarounds available. But, I have a client going to initiate several new J2 projects starting next week and for that they really need a formal release available (especially now that I probably won't be around anymore formally to support them).
If you really think the release should be hold up for this then could you please explain why having it fixed first is so important. Of course, your -1 will be enough to prevent us doing the release, but I kindly request you to reconsider this...
Regards, Ate
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
