[ http://issues.apache.org/jira/browse/JS2-226?page=comments#action_12431770 ] Woonsan Ko commented on JS2-226: --------------------------------
I've investigated this issue for last two months to provide parallel processing feature for my client. During my work, I found the following: (I feel that this issue is so big and deep, as Ate said.) - The request of tomcat is not thread-safe, but anyway the last wrapper is org.apache.jetspeed.engine.servlet.ServletRequestImpl for portlets. (So the implementation can reference other sources, such as current thread.) - Portlet-level attributes are encoded in JS2, but upper-level ones are not. e.g) portlet instance, portlet config, portlet request, portlet response, method id, portlet name and context. - On the other hand, in parallel processing, there is a thread pool. (WorkerMonitor and Worker) - Therefore, I thought that some upper-level attributes (such as "javax.portlet.request") could be stored in the worker thread, not just in request, and then in parallel processing the attributes could be referenced via the worker thread, not just via request. (Actually, I implemented the java.util.Map interface in my test worker class.) I've been experimented the idea by writing some messy codes which extended or overrode the existing components, and it seems like working well now in point of functionality However, the performance is not as good as I expected in my test environment. (One CPU PC.) I'm not sure the parallel processing is better in point of performance (Response time). Anyway, I want to know how you think of my idea. (Some attributes can be stored and referenced in the worker thread for the parallel rendering portlets.) Any comment welcomed. > Page Aggregation using STRATEGY_PARALLEL severly broken > ------------------------------------------------------- > > Key: JS2-226 > URL: http://issues.apache.org/jira/browse/JS2-226 > Project: Jetspeed 2 > Issue Type: Bug > Components: Aggregation > Affects Versions: 2.1 > Environment: Tomcat 5.0.28 > Reporter: Ate Douma > Assigned To: David Sean Taylor > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
