PubServer Error when seeding Geowebcache from Bentley Geo Web Publisher.

Hello Xi,

Looking at the log it looks like you are publishing tDPR and tRaster layers (assumingly by the name of the layers) in WMS mode (MapViewerLite), while publishing the layers there was a time out and the GWP Service stopped.

If my interpretation is correct regarding the data that you are trying to publish (tDPR and tRaster) my first suggestion would be to confirm that the tDPR and tRaster layers were correctly created. You should do that by making sure the related tDRP and tRaster .db files show in each row the xy extensions, to verify the .db you can follow the steps described in the technote indicated below. If a row does not contain the x and y boundaries then the tDPR wasn’t correctly created.
communities.bentley.com/.../12549.gwp2055-how-to-view-tdpr-and-traster-index-files

On the other hand one possibility of a time out related error is that there could be too much data being requested causing the failure. The tDPR workflow has been designed to display at a large scale, with a minimum set of DGNs displayed at the same time. In tDPR 1 DGN = 1 DPR file and if you fit to the entire dataset, you will display (load in memory) all dpr files. Hence in this conditions if you use this type of layer as a startup layer and the layer contains hundreds or thousands of tiles (dprs) this could happen. In this scenario to prevent loading all the tiles, you can define a scale range for the layer in the Map Author. This type of layer is very detailed and hence there is no need for such detail when fitting the whole data. So what you can test is setting the Map Layer to 1:5000 scale range for example and then in the WMS viewer zoom below the scale (in a location where you know there is data) to see if it publishes the data correctly. What you can consider for a startup/overview layer is the use an iDPR layer that contains limited levels, for example a grid that loads the boundary of each tile.

Regards,
Carlos

Hello Xi,

Looking at the log it looks like you are publishing tDPR and tRaster layers (assumingly by the name of the layers) in WMS mode (MapViewerLite), while publishing the layers there was a time out and the GWP Service stopped.

If my interpretation is correct regarding the data that you are trying to publish (tDPR and tRaster) my first suggestion would be to confirm that the tDPR and tRaster layers were correctly created. You should do that by making sure the related tDRP and tRaster .db files show in each row the xy extensions, to verify the .db you can follow the steps described in the technote indicated below. If a row does not contain the x and y boundaries then the tDPR wasn’t correctly created.
communities.bentley.com/.../12549.gwp2055-how-to-view-tdpr-and-traster-index-files

On the other hand one possibility of a time out related error is that there could be too much data being requested causing the failure. The tDPR workflow has been designed to display at a large scale, with a minimum set of DGNs displayed at the same time. In tDPR 1 DGN = 1 DPR file and if you fit to the entire dataset, you will display (load in memory) all dpr files. Hence in this conditions if you use this type of layer as a startup layer and the layer contains hundreds or thousands of tiles (dprs) this could happen. In this scenario to prevent loading all the tiles, you can define a scale range for the layer in the Map Author. This type of layer is very detailed and hence there is no need for such detail when fitting the whole data. So what you can test is setting the Map Layer to 1:5000 scale range for example and then in the WMS viewer zoom below the scale (in a location where you know there is data) to see if it publishes the data correctly. What you can consider for a startup/overview layer is the use an iDPR layer that contains limited levels, for example a grid that loads the boundary of each tile.

Regards,
Carlos