https://osgeo-org.atlassian.net/browse/GEOS-7961
My code fails with the same null pointer stacktrace as indicated there. I’m using a geoserver snapshot taken April 1 2016 running in Java 8/Tomcat 8.
I’ve setup an automated client with jMeter that submits GetFeature requests. I run jMeter full speed with a single thread and it works every time. Then with only two jMeter threads running I can make the GEOS-7961 null pointer happen frequently.
I attach a remote debugger to tomcat and place a conditional breakpoint:
public static QName getParticleName(XSDParticle particle) {
XSDElementDeclaration content = (XSDElementDeclaration) particle.getContent();
if ( content**.isElementDeclarationReference() ) {**
Stopping where “content==null”. I then hit the breakpoint while testing. So it would appear I have a decent context for developing a fix for this. However, I’m very unfamiliar with the details of how these XSD classes work and what might be the thread-synchronization/timing vulnerabilities.
Any developer with insight please help me point in the right direction – thanks!
Hi Walter,
see my last comment on the ticket
Cheers
Andrea
···
On Fri, Sep 1, 2017 at 12:41 PM, Walter Stovall <walter.stovall@anonymised.com> wrote:
https://osgeo-org.atlassian.net/browse/GEOS-7961
My code fails with the same null pointer stacktrace as indicated there. I’m using a geoserver snapshot taken April 1 2016 running in Java 8/Tomcat 8.
I’ve setup an automated client with jMeter that submits GetFeature requests. I run jMeter full speed with a single thread and it works every time. Then with only two jMeter threads running I can make the GEOS-7961 null pointer happen frequently.
I attach a remote debugger to tomcat and place a conditional breakpoint:
public static QName getParticleName(XSDParticle particle) {
XSDElementDeclaration content = (XSDElementDeclaration) particle.getContent();
if ( content**.isElementDeclarationReference() ) {**
Stopping where “content==null”. I then hit the breakpoint while testing. So it would appear I have a decent context for developing a fix for this. However, I’m very unfamiliar with the details of how these XSD classes work and what might be the thread-synchronization/timing vulnerabilities.
Any developer with insight please help me point in the right direction – thanks!
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Regards,
Andrea Aime
==
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 di Montramito 3/A
55054 Massarosa (LU)
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.