You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have an AGS Server on 10.4.1 with the GeoEvent Extension and were able to build, test and successfully use the Kafka adapter. We now have the the GeoEvent Server on 10.5 and have also built the Kafka Transport Adapter with the mvn install command and even though the install said the build was successful it did spit out this warning: [WARNING] Bundle com.esri.geoevent.transport:kafka-transport:bundle:10.5.0 : Did not find matching referal for !kafka.*
Additionally, after building this as an input on a GeoEvent Server 10.5 model such as we did exactly on the 10.4.1 server it will no accept any data and we do not get any errors. I know this tool was updated to work on 10.5 and the .jar file created matches the POM file but just can't understand what the issue might be.
Any ideas? Is the warning mentioned above real more of an error?
Thanks, Jason
The text was updated successfully, but these errors were encountered:
We currently have an AGS Server on 10.4.1 with the GeoEvent Extension and were able to build, test and successfully use the Kafka adapter. We now have the the GeoEvent Server on 10.5 and have also built the Kafka Transport Adapter with the mvn install command and even though the install said the build was successful it did spit out this warning: [WARNING] Bundle com.esri.geoevent.transport:kafka-transport:bundle:10.5.0 : Did not find matching referal for !kafka.*
Additionally, after building this as an input on a GeoEvent Server 10.5 model such as we did exactly on the 10.4.1 server it will no accept any data and we do not get any errors. I know this tool was updated to work on 10.5 and the .jar file created matches the POM file but just can't understand what the issue might be.
Any ideas? Is the warning mentioned above real more of an error?
Thanks, Jason
The text was updated successfully, but these errors were encountered: