We just upgraded geoevent to 10.8 from 10.6.1 and have encountered this error when we the receive json on a rest end point input us used:
| com.esri.ges.adapter.genericJson.JsonInboundAdapter | Error converting JSON node to GeoEvent. |
The data is being sent to the endpoint via a python script. Here is a boiled version of what it looks like...
<SPAN class="keyword token">import</SPAN> requests
<SPAN class="keyword token">import</SPAN> json
url <SPAN class="operator token">=</SPAN> <SPAN class="operator token"><</SPAN>endpoint url<SPAN class="operator token">></SPAN>
mes <SPAN class="operator token">=</SPAN> <SPAN class="punctuation token">{</SPAN><SPAN class="string token">"trackID"</SPAN><SPAN class="punctuation token">:</SPAN><SPAN class="string token">"testing"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"comment"</SPAN><SPAN class="punctuation token">:</SPAN><SPAN class="string token">"testing comment"</SPAN><SPAN class="punctuation token">}</SPAN>
r <SPAN class="operator token">=</SPAN> requests<SPAN class="punctuation token">.</SPAN>post<SPAN class="punctuation token">(</SPAN>url<SPAN class="punctuation token">,</SPAN> json<SPAN class="operator token">=</SPAN>mes<SPAN class="punctuation token">,</SPAN> verify<SPAN class="operator token">=</SPAN><SPAN class="token boolean">False</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>r<SPAN class="punctuation token">.</SPAN>status_code<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>r<SPAN class="punctuation token">.</SPAN>content<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN></SPAN>The data is being sent to the endpoint and the definition is being generated by geoevent correctly but the input is not processing the data appropriately. The input count does not go up and the mentioned error is found in the log. Also, this method worked just fine on the 10.6.1 version.
Anyone have an idea on why this would happen?
GeoEvent
RJ Sunderman