|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
2.2.4
|
|
Assignee:
|
Gabriel Roldán
|
|
Components:
|
GWC
|
|
Created:
|
15/Feb/13 10:47 AM
|
|
Description:
|
Originally reported at GWC’s issue tracker:
Using the packaged GWC integration with GeoServer 2.2
Steps to reproduce
- We have the web cache integration turned on
- Configure the WFS layer to be cached
- Update WFS layers regularly via rest (our updates can happen as often as every second)
- GWC integration uses a TransactionPlugin to listen for WFS Transaction commits and automatically truncates the appropriate tiles from the associated tile layers
- This truncate starts several tasks (1 per projection/format pair)
Results
Each task gets a reference in the TileBreeder.currentPool
Our testing shows that eventually GeoServer runs out of memory
Expected Results
TileBreeder.drain is called periodically to remove completed tasks
Workaround
Visit http://:8080/geoserver/gwc/rest/seed.json which will trigger the TileBreeder.drain method and free up the memory.
|
|
Project:
|
GeoServer
|
|
Priority:
|
 Major
|
|
Reporter:
|
Gabriel Roldán
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your [JIRA administrators](https://jira.codehaus.org/secure/ContactAdministrators!default.jspa).
For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)