Forum Discussion
Web Accelerator not responding to iControl invalidation commands
Greetings. Your actual XML message in test_f5.txt is valid; it works for me with the appropriate change to the app name and the URI.
I have not looked at your Java program. But here is a pearl of wisdom followed by a very simple example which you might use as a better starting example than the rather sordid Perl script to which I think you're referring.
Search your log /var/log/tomcat/catalina.out for an error similar to this:
Exception in thread "Thread-5" java.lang.NullPointerException
at com.f5.wa.esi.server.InvalidationSocketServer.processInvalidation(InvalidationSocketServer.java:157)
at com.f5.wa.esi.server.InvalidationSocketServer.run(InvalidationSocketServer.java:103)
at java.lang.Thread.run(Unknown Source)
If this error occurred since last time you restarted tomcat, then you will find yourself in an unfortunate predicament, a predicament subversive to developing your working invalidation script. Because subsequent iControl calls to the method will silently fail in the meantime even with a properly base64 encoded XML message. Restart the tomcat service for to recover.
tmsh restart sys service tomcat
The condition occurs after certain invalid / corrupt messages to esi_invalidate_content, which makes it easily stumbled upon trying to develop a new script.
That Python example is attached. It seems to require more effort than it's worth to render it correctly within the posting.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com