Hey,
I 'am currently developing a custom transporter and combined it with an out of the box adapter.
But I'am struggeling with the connector lifecycle. If a special error occures in the transporter I want the connector to shutdown or be permanently in an error state. But if I set the RunningState to error or try to shutdown/stop the transporter, GeoEvent always trys to start the transport again.
I could skip the startup by start by using an additional error state and just return in the startup method, but i hope there is a better way to handle it.
Furthermore I receive a lot of log messages like this one while the transporter is starting because the initialization might take a few seconds. If i try to solve my issue by skipping the Startup I would also receive a lof of these messages:
com<SPAN class="punctuation token">.</SPAN>esri<SPAN class="punctuation token">.</SPAN>ges<SPAN class="punctuation token">.</SPAN>manager<SPAN class="punctuation token">.</SPAN>stream<SPAN class="punctuation token">.</SPAN>internal<SPAN class="punctuation token">.</SPAN>StreamBase Stream <SPAN class="punctuation token">(</SPAN>ConnectorName<SPAN class="punctuation token">)</SPAN> is trying to start its Transport <SPAN class="punctuation token">(</SPAN>de<SPAN class="punctuation token">.</SPAN>esri<SPAN class="punctuation token">.</SPAN>ges<SPAN class="punctuation token">.</SPAN>transport<SPAN class="operator token">/</SPAN>TransportName<SPAN class="operator token">/</SPAN><SPAN class="number token">10.7</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="number token">1</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="line-numbers-rows"><SPAN></SPAN></SPAN>
Grateful for any hint,
Stefan
