|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1352 | minor | always | 09-18-06 09:23 | 06-18-07 10:11 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.2 | ||
|
|
|||||
| 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)? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||