Purge an item from Wowza Streaming Engine Media Cache

Use the Wowza Streaming Engine™ media server software Java API to purge assets from Media Cache.

Purge assets not in use


Use the following Java API methods to purge an asset from the cache if it's not being referenced or played by clients.

To purge an asset from the cache based on the asset mediaName, which is the asset stream name minus the prefix and after any play aliasing, use the following call:

MediaCache mediaCache = MediaCacheImpl.getMediaCache();
mediaCache.flushItemFromCache(mediaName);

You can also use the following call that includes the asset stream name with the prefix. This will take the stream name (with the prefix) and run it through an aliasing system to resolve it to the proper media name, and then purge the asset from the cache:

MediaCache mediaCache = MediaCacheImpl.getMediaCache();
mediaCache.flushStreamNameFromCache(appInstance, streamName);

Purge assets in use


Note: Purging assets that are in use requires Wowza Streaming Engine™ 4.3 or later.

Use the following Java API methods to purge an asset from the cache even if it's still being referenced or played by clients.

To purge an asset from the cache based on the asset mediaName, which is the asset stream name minus the prefix and after any play aliasing, use the following call:

MediaCache mediaCache = MediaCacheImpl.getMediaCache();
mediaCache.flushAndForceItemFromCache(mediaName);

You can also use the following call that includes the asset stream name with the prefix. This will take the stream name (with the prefix) and run it through an aliasing system to resolve it to the proper media name, and then purge the asset from the cache:

MediaCache mediaCache = MediaCacheImpl.getMediaCache();
mediaCache.flushAndForceStreamNameFromCache(appInstance, streamName);

These methods purge the specified asset 30 seconds after the last currently connected client is disconnected. After the call is made, Media Cache will disconnect all currently connected clients, purge the asset from the cache, and then, if a new request is made for the asset, get new copy of the asset from the source. These calls are useful if you want to remove a specific asset and/or remove an asset so it can be refreshed when a new client requests it.

The following example HTTP provider uses the flushAndForceItemFromCache method:

package com.wowza.demo.mediacache.gc;

import java.io.OutputStream;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import java.util.Map;

import com.wowza.wms.http.*;
import com.wowza.wms.logging.*;
import com.wowza.wms.mediacache.impl.MediaCacheImpl;
import com.wowza.wms.mediacache.model.MediaCache;
import com.wowza.wms.vhost.IVHost;

public class HTTPForceDelete extends HTTPProvider2Base {

	public void onHTTPRequest(IVHost vhost, IHTTPRequest req, IHTTPResponse resp) {
		if (!doHTTPAuthentication(vhost, req, resp))
			return;

		Map<String, List<String>> params = req.getParameterMap();
		String itemName ="";

		if ( params.containsKey("itemname") )
			itemName = params.get("itemname").get(0);

		boolean foundItem = false;
		if ( itemName.length() > 0 ) {
			String itemToDelete = null;
			MediaCache mediaCache = MediaCacheImpl.getMediaCache();
			Iterator<String> itemNamesI = mediaCache.cacheItemNames().iterator();
			while (itemNamesI.hasNext()) {
					String thisItem = itemNamesI.next();
					WMSLoggerFactory.getLogger(HTTPForceDelete.class).info("Item in list was called "+thisItem);
					if ( thisItem.endsWith(itemName) ) {
						itemToDelete = thisItem;
					}
			}
			// Do the flush separately from the iterator because flushAndForceItemFromCache modifies the iterator's underlying structure
			// and can cause a ConcurrentModificationException
			if (itemToDelete != null) {
				foundItem = mediaCache.flushAndForceItemFromCache(itemToDelete);  
			}

		}

		String retStr  = "Item "+itemName+" ";
		if ( foundItem == true )
			retStr += "found.";
		else
			retStr += "NOT FOUND.";

		try {
			OutputStream out = resp.getOutputStream();
			byte[] outBytes = retStr.getBytes();
			out.write(outBytes);
		}
		catch (Exception e) {
			WMSLoggerFactory.getLogger(null).error("HTTPForceDelete: " + e.toString());
		}
	}
}