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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
