Anonymous | Login | Signup for a new account | 11-17-2024 00:45 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001352 | [Resin] | minor | always | 09-18-06 09:23 | 06-18-07 10:11 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | |||||||
Summary | 0001352: JSPCompiler multithreaded | ||||||||
Description |
(rep by Caleb Richardson) I have quite a large number of JSPs to precompile, and these JSPs share many interdependent tag files. I am currently programatically invoking the JSPCompiler.main() method, my question is whether or not it is safe to fork multiple threads that in turn call JSPCompiler.main(), each thread handling a subset of the JSPs. Presumably JSPCompiler uses the same internal code as on demand JSP compilation post deployment, so I would expect it to be thread safe with regard to only compiling a given tag file once, even if it is shared among many JSPs. So is this safe, and does JSPCompiler already perform this optimization on SMP machines by checking Runtime.getAvailableProcessors (or checking via some other technique)? |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |