Re: [geomesa-dev] Accumulo Data Store

["Dave Sousa" <dasousa@xxxxxxxxxxx>]

Anthony,

You're right there is an Internal Server Error.  Here is the output:

wicket-ajax.js:641 POST
http://172.28.128.3:8080/geoserver/web/?wicket:interface=:11:dataStoreForm:.
ehaviorListener:0:&wicket:ignoreIfNotActive=true&random=0.8540484695570223
500 (Internal Server Error)doPost @ wicket-ajax.js:641(anonymous function) @
wicket-ajax.js:617schedule @ wicket-ajax.js:416schedule @
wicket-ajax.js:450post @ wicket-ajax.js:617submitForm @
wicket-ajax.js:776submitFormById @ wicket-ajax.js:760wicketSubmitFormById @
wicket-ajax.js:1458onclick @ ?wicket:interface=:11:::::427

Thanks,

Dave

-----Original Message-----
From: geomesa-dev-bounces@xxxxxxxxxxxxxxxx
[mailto:geomesa-dev-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Anthony Fox
Sent: Sunday, August 07, 2016 7:09 PM
To: Discussions between GeoMesa committers <geomesa-dev@xxxxxxxxxxxxxxxx>
Subject: Re: [geomesa-dev] Accumulo Data Store


Dave,

Usually this means there's something missing on the classpath.
Geoserver tends to swallow the exception in the http response.  Try
this: load up the network tab in Firebug or Chrome debug tools.  Then, click
the save button again.  Look at the network communication in the debug tool
output.  If there's an exception, send it back to the mailing list.  That'll
help sort things out.

Thanks,
Anthony


Dave Sousa <dasousa@xxxxxxxxxxx> writes:

> I'm using the following configuration in a VirtualBox instance, and 
> trying to run the Accumulo quick start tutorial:
>
>
>
> HADOOP_VERSION=2.7.2
>
> ACCUMULO_VERSION=1.7.2
>
> ZOOKEEPER_VERSION=3.4.8
>
> GEOSERVER_VERSION=2.8.1
>
> GEOTOOLS_VERSION=14.1
>
> GEOMESA_VERSION=1.2.4
>
> TOMCAT_VERSION=7.0.70
>
>
>
> Unfortunately, when I try to create an Accumulo data store following 
> the instructions in the tutorial, the add data store page in GeoServer 
> does not refresh after clicking Save.  I'm not seeing any errors in 
> catalina.out, or the GeoServer logs.  At this point, I'm stumped about 
> what the problem could be.  Any suggestions on possible places to look for
clues?
>
>
>
> The Zookeeper and Accumulo logs look OK as well.
>
>
>
> Dave
>
> _______________________________________________
> geomesa-dev mailing list
> geomesa-dev@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> http://locationtech.org/mailman/listinfo/geomesa-dev
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit http://locationtech.org/mailman/listinfo/geomesa-dev