|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
2.3-beta1
|
|
Assignee:
|
Andrea Aime
|
|
Components:
|
GWC, Oracle
|
|
Created:
|
20/Dec/12 10:59 PM
|
|
Description:
|
When configured to cache 3D data, GWC is slow to start up (with a DWC DiskQuota thread using 100% of one CPU). As a result initial GeoServer start up takes five minuets.
Pausing in a debugger shows:
Thread [GWC DiskQuota Store Writer-1] (Suspended)
owns: GeoServerTileLayer (id=73)
MolodenskiTransform(AbstractMathTransform).transform(DirectPosition, DirectPosition) line: 248
JTS.transformTo2D(GeneralDirectPosition, MathTransform, MathTransform) line: 407
JTS.transformTo2D(ReferencedEnvelope, CoordinateReferenceSystem, boolean, int) line: 350
ReferencedEnvelope3D.transform(CoordinateReferenceSystem, boolean, int) line: 1097
GeoServerTileLayer.getBounds(SRS) line: 806
GeoServerTileLayer.getGrids(ReferencedEnvelope, GridSetBroker) line: 749
GeoServerTileLayer.checkGridSubsets() line: 694
GeoServerTileLayer.getGridSubsets() line: 680
TilePageCalculator.getTileSetsFor(String) line: 91
BDBQuotaStore.createLayer(String, Transaction) line: 257
BDBQuotaStore.access$700(BDBQuotaStore, String, Transaction) line: 40
BDBQuotaStore$StartUpInitializer.call() line: 224
BDBQuotaStore$StartUpInitializer.call() line: 186
FutureTask$Sync.innerRun() line: 303
FutureTask<V>.run() line: 138
ThreadPoolExecutor$Worker.runTask(Runnable) line: 886
ThreadPoolExecutor$Worker.run() line: 908
Thread.run() line: 680
If you would like to quickly test this, try the point_test.properties file from GeoTools gt-renderer module.
|
|
Project:
|
GeoServer
|
|
Priority:
|
 Minor
|
|
Reporter:
|
Jody Garnett
|
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)