Forum Discussion

Jim_Morgan_4481's avatar
Jim_Morgan_4481
Icon for Nimbostratus rankNimbostratus
Aug 26, 2010

Web Accelerator not responding to iControl invalidation commands

We have an eCommerce site and need to be able to invalidate the cache programatically under certain conditions (e.g. a product goes out of stock and we don't want the product page to show a Buy Now button). We also invalidate the entire cache on a daily basis after our stock and price updates. We currently do this now with our old Piva v4 servers. We have been told that we could do this with v10 using iControl. We have tried several methods to do this, but the cache is not being invalidated.

 

 

Things we have tried:

 

 

1. Using the provided Perl script

 

2. Using soapUI to send the message and look at the results. We get the response but the cache is not invalidated.

 

3. Using a Java class along with the iControl assembly iControl.jar (recompiled under JDK 1.4.2)

 

 

In all cases, we are not seeing the cache invalidated. We have tried both the invalidate_content as well as the esi_invalidate_content methods.

 

 

We've tried sending the message with the START_INVALIDATION_MESSAGE:b2c before the xml as well as without it. I can send the exact same message to our v4 server (without the START_INVALIDATION_MESSAGE:b2c and just the xml) and the cache invalidates. In all cases, we are Base64 encoding it as it shows in the Perl script:

 

 

Message must be Base64 encoded inorder to send in SOAP message

 

my $encoded_message = encodeBase64($message);

 

 

We can get SystemInfo just fine using soapUI and Java (haven't tried it with Perl) so we know we are able to connect and get good responses back

 

 

If I login to the admin console and invalidate the entire cache there, it works just fine as well.

 

 

We can see the response coming back thru soapUI. It just looks like the backend process to invalidate the cache isn't triggered.

 

 

We need to get iControl working so we can put these servers into our production environment and retire our v4 servers.
No RepliesBe the first to reply