Then this issue is not because of user login. i have written the code to to modify the features like add, update, delete through REST service.
this is making issue i think. Can i send the code? can you guys help me on this. -Chiru On Tue, Aug 25, 2015 at 1:16 PM, Andrea Aime <[email protected]> wrote: > On Thu, Aug 20, 2015 at 12:36 PM, Chiranjeevi GK < > [email protected]> wrote: > >> we have geoserver and we are 13 in our team >> >> when we are login with same user name and password >> >> can any one please tell me is this because of load or because of the same >> username and password? >> >> >> i can see this error, >> >> 2015-08-20 15:48:47,050 ERROR [wicket.RequestCycle] - >> org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null >> is still locked by: Thread[http-nio-9090-exec-15,5,main], giving up trying >> to get the page for path: 13:form >> > > This kind of error can be caused by the "big configuration lock" (BCL). > The BCL protects the internal catalog from concurrent modification, as > it's not thread safe, and it does not support > transactions, so that inconsistent changes are not done as part of two > admins concurrently changing the same > resource, or related resources. > > The BCL is acquired as the HTTP request comes in on the UI, or on the REST > interface, and its held > for as long as the request takes to run. > > On configuration with small amounts of layers most interactions are quick > and you don't notice the > issue, with one exception: computing the bbox of a layer. > If the layer is big, the computation can span several minutes (I once > waited 20 minutes computing > the bbox of a Oracle table with 50 million polygons), during that time > nothing else can be done, > and the PageMap timeout will trigger, causing the issue you've seen. > > If you have a large catalog instead, hundreds of thousands of layers, the > problem might occurr > more often, especially since only one admin at a time will really get > GeoServer attention, > e..g, if an operation takes 6 seconds, and you have all 13 admins waiting > in line, the > last 3 will likely see the timeout > > Adding more users won't help solving the above problem, a re-architecture > of the inner catalog > is needed instead. The unsupported JDBCConfig community module helps > dealing with large catalogs, > but still does not have transaction support, so there is still a chance > you will get incosistent changes > if two admins end up editing the same group of resources (e.g., one > deletes a layer, the other edits > a layer group containing that layer, you might get a layer group with a > dangling reference). > > Cheers > Andrea > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V 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. > > ------------------------------------------------------- >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
