03-16-2016 12:07 PM
Some users have noted that their local SDK extension JAR (the Jar in the plugin folder) is not getting auto-updated when we push out a release. This post describes the basics of how the auto-upgrade process works and how to ensure that your application correctly upgrades when a new extension JAR is available.
Cisco pushes new extension Jars to the cloud on a regular basis. These jars typically contain performance improvements, bug fixes, and occasionally new functionality. When your application starts:
It is important to note that if your application connects and then quickly exits (typically in less than 30 seconds) that a heartbeat receive never occurs and an upgrade does not take place because the first heartbeat can be up to 30 seconds after you init the connection. To ensure that your application downloads and installs the latest extension Jar, you should introduce a 30 second sleep after you init the management and client connectors to allow time for an extension upgrade.
03-21-2016 08:53 AM
I see the version test and update happening with no management connector and just the client connection active. This doesn't quite match your description. Is this not behaving as intended?
03-28-2016 07:20 AM
Hi Paul,
You are correct, thanks! The upgrade occurs on both the client and the management connection. If you are running both connections in the same JVM then you'll only get a single upgrade process, but it will also upgrade if you are running only one or the other.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide