Forum Discussion
Jim_Morgan_4481
Sep 09, 2010Nimbostratus
Hi,
I just wanted to post an update to anybody following this. In the end, all we doing thru iControl is sending the invalidation messages. After struggling to get the iControl assembly to work with this, we just went back to plain old Java objects without any specialized SOAP libraries.
I'm just manually creating the entire message including the envelope. I'm using a plain old URL HttpURLConnection (and overriding the TrustManager so we don't care about getting a valid cert back). I add the required headers, send the message over to the iControl.cgi and then get the entire SOAP response back.
This returns a void in any case, so we don't need to parse it. We'll just log the return result so if there are any issues (say password changed, no connection, etc) we'll see them.
So, that is the work around we are going to use to send these messages using Java.
One thing that would be nice for a future release is to fix the NullPointerException in the server code.
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)
At times we need to do on the fly page invalidation where we'll be hand crafting the xml message.
Regards,
Jim Morgan