.JAR files successfully uploaded but about activemq-for-geoevent

[brudo]

@hanoch I think it is safe to say this issue can now closed as not repeatable since PR #5 was merged (thank you), and current master targets 10.6.1 specifically (but works with 10.7.x in my experience). Any comment from original poster @kuranjpr on how the current master works on 10.6.x and 10.7.x?

[kuranjpr]

Could you please help on getting inbound and outbound connector in the components?

[mzesri]

I was unable to reproduce this with our development version 10.6.1. I would imagine it should work with previous versions as well. GeoEvent does have problem loading large jar files. But if the jar file is uploaded successfully, it should be available for connectors and inputs.

Here is what I did:

1. clone this repo.
2. run mvn clean install WITHOUT making any changes.
3. start GeoEevent. Used "add local transport" button to add this jar.
4. Verified that the inbund/outbound transports do show up and their versions are 10.4.1.
5. Created a connector with the inbound amqp transport
6. Went to create input with this new connector. All transport properties showed up.

What version of GeoEvent are you using? Which step didn't go as expected.

[kuranjpr]

Hello Ming,
I was able to add local Active MQ transport in 10.5.1 and create the connector and input. I did all the necessary changes with the TCP port. How do i know that the TCP port is sending the messages to the Geo event manager in Input in Monitor tab correctly.
Here is the screen shot

[kuranjpr]

Hello Ming, I was able to add local Active MQ transport in 10.5.1 and create the connector and input. I did all the necessary changes with the TCP port. How do i know that the TCP port is sending the messages to the Geo event manager in Input in Monitor tab correctly. Here is the screen shot With Best Regards, Prashant R. Kuranjekar, GISP Senior Technologist - Geospatial Cellno: [phone]

…

On Wed, Apr 25, 2018 at 6:58 PM, Ming Zhao ***@***.***> wrote: I was unable to reproduce this with our development version 10.6.1. I would imagine it should work with previous versions as well. GeoEvent does have problem loading large jar files. But if the jar file is uploaded successfully, it should be available for connectors and inputs. Here is what I did: 1. clone this repo. 2. run mvn clean install WITHOUT making any changes. 3. start GeoEevent. Used "add local transport" button to add this jar. 4. Verified that the inbund/outbound transports do show up and their versions are 10.4.1. 5. Created a connector with the inbound amqp transport 6. Went to create input with this new connector. All transport properties showed up. What version of GeoEvent are you using? Which step didn't go as expected. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AL_yygwUV-cDsIvwqgdnKTH0TWiAMju4ks5tsP-MgaJpZM4TisPt> .

[mzesri]

I am not familiar with this particular transport. But generally speaking, the input count on the monitor page indicates how many events this input has received. If you think it should be receiving events but the count is still 0, you may need to take a look at the karaf.log file or the log tab on the manager page. If no error is showing up in the logs, I will suspect whether you are connected to the right message queue. You can also try debug through your transport code. I believe the GeoEvent Develop Guide that comes with the install talks about how to debug a custom component.

[brudo]

I also had issues with the transport failing to deploy consistently on 10.6.0, which could be similar to what the original poster described. I made changes included in PR #5 to fix it. The version in Esri:master did work on 10.5.1. However, I did not re-test the original version with 10.6.1 when it came out.

[hanoch]

@brudo I left some comments on PR #5