On Thu, Oct 9, 2014 at 10:42 AM, Ismail, Mark <mark.ism...@knowsley.gov.uk>
wrote:
> Hi
>
>
>
> I updated from version 2.5.2 on windows server 2008 64bit which was using
> apache tomcat 8.09 and jre-8u11-windows-i586
>
> I upgraded apache to 8.14 and the jre to jre-8u20-windows-i586 to fix a
> security vulnerability
>
> I am using native jai and the tiles are in png8
>
Hmm... Java 8 is not tested with GeoServer.
>
>
> While I had to rebuild apache I decided to upgrade geoserver at the same
> time
>
>
>
> I have my data folder on the local c drive – the server is a Vmware
> server. The data folder included a 21gb cache of my 5 ordnance survey base
> maps as layer groups
>
>
>
> I decided that reseed wasn’t working by emptying one the of layers using
> tile caching / tile layers empty option and then reseeding.
>
> I opened the cache folder where there were no tiles and hit reseed
>
> The reseed form opened with 300k ish tiles to do and said it had done a
> few hundred – by checking the folder I could see the files there
>
> When you hit refresh on the seed form to update progress the job
> disappears, the cache folder still only has a few files in it
>
>
>
> I tried this on a few layers with exactly the same result.
>
>
>
> I spent some time this morning monitoring the network traffic and managed
> to find an error :-
>
>
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
> ServiceExceptionReport SYSTEM "
> http://geolive.knowsley.gov.uk:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd";>
> <ServiceExceptionReport version="1.1.1" > <ServiceException>
>
> Internal error
>
> Error occurred getting table name list.
>
> ORA-01000: maximum open cursors exceeded
>
>
>
> </ServiceException></ServiceExceptionReport>
>
Ah, this is a well known problem with Oracle, not much we can do on our
side, Oracle prepared statements keep
cursors open, prepared statements are associated to connections,
we keep connections open in the pool because opening a new one with Oracle
is _very_ expensive
(there is a long thread on this topic, maybe one or two year ago, in this
mailing list).
What you can do to limit the issue is to either tune your Oracle
installation to allow more cursors to be opened,
or go in the GeoServer store configuration and reduce the number of
prepared statements kept open per
connection (the default if 50), eventually also reduce the number of
connections in the pool
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
