[MGNLIMG-55] Preload AWT library Created: 25/Jun/09 Updated: 04/Dec/13 Resolved: 25/Jun/09 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
Under certain circumstances/environments, it seems that loading the awt library from several threads causes these threads to be blocked; if we generate ONE image on one instance that just started, everything works fine afterwards. If otoh the first requests goes to a page that attempts to generate multiple images at once (demo-project.html), it seems there is contention around calls to Toolkit.loadLibraries (and ColorModel.loadLibraries) If we have ensure the awt lib is loaded prior to using the imaging framwork, everything seems to work fine. As a simple workaround, we'll add a module that does just that. So far, we've seen this issue on
|
| Comments |
| Comment by Magnolia International [ 25/Jun/09 ] |
|
the workaround module is available at http://repo.magnolia-cms.com/enterprise-snapshots/info/magnolia/magnolia-module-imaging-fix-preload-awt/2.0.1-SNAPSHOT/ for now |