Topic
  • 6 replies
  • Latest Post - ‏2007-06-06T19:21:25Z by SystemAdmin
Chris_Churchill
Chris_Churchill
2 Posts

Pinned topic VoiceXML audio cache problem

‏2006-10-31T15:58:44Z |
After installing a new audio wav file named the same as a previous file, it is not being refreshed. I stopped the apps, appnodes, host, deleted the VXML2cache, there was no cache directory and also stopped and started the WAS. I have placed the following tag to stop caching:
<meta http-equiv="Expires" content="0"/>
Also the maxage is listed below and is needed to ensure that the performance of the application is acceptable:
<property name="audiomaxage" value="10000" />
I do want this audio file to be cached once the new file is loaded.

I am not sure where this audio file is being cached. Any direction to how to ensure that the audio file is removed from cache would be appreciated.
Updated on 2007-06-06T19:21:25Z at 2007-06-06T19:21:25Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    835 Posts

    Re: VoiceXML audio cache problem

    ‏2006-11-10T17:54:24Z  
    From your description it sounds as if you're having a problem with WebSphere Voice Response. What version do you have installed? Possibly the best way to manage the caching of audio files is to put the caching directives you want applied on the HTTP server. My interpretation of the meta tag is that it applies to the vxml document only, so it will not affect any other resource. The default time for expires used by WVR is 24 hours, so even though your maxage value of the audio file will have be exceeded after 2.7 hours, it will not be expired so the cached version will be used.
  • Chris_Churchill
    Chris_Churchill
    2 Posts

    Re: VoiceXML audio cache problem

    ‏2006-11-10T18:19:44Z  
    From your description it sounds as if you're having a problem with WebSphere Voice Response. What version do you have installed? Possibly the best way to manage the caching of audio files is to put the caching directives you want applied on the HTTP server. My interpretation of the meta tag is that it applies to the vxml document only, so it will not affect any other resource. The default time for expires used by WVR is 24 hours, so even though your maxage value of the audio file will have be exceeded after 2.7 hours, it will not be expired so the cached version will be used.
    The audio file is being cleared from the cache in the 2.7 hrs (after 8 hrs for sure). The problem I want to resolve is that after I install a new audio file I want to be able to test it right away. Not 3 or 8 hours later. Any other ideas?
  • SystemAdmin
    SystemAdmin
    835 Posts

    Re: VoiceXML audio cache problem

    ‏2006-11-30T16:17:05Z  
    The audio file is being cleared from the cache in the 2.7 hrs (after 8 hrs for sure). The problem I want to resolve is that after I install a new audio file I want to be able to test it right away. Not 3 or 8 hours later. Any other ideas?
    chris_churchill@manulife.com wrote:
    > The audio file is being cleared from the cache in the 2.7 hrs (after 8 hrs for sure). The problem I want to resolve is that after I install a new audio file I want to be able to test it right away. Not 3 or 8 hours later. Any other ideas?

    I've been having exactly the same need and problem lately, with WVR/S 4.2.
    The only workaround I've found was to temporarily modify my vxml source
    to add maxage and maxstale arguments:
    <audio src="./audio/myaudio.wav" maxage="0" maxstale="0">

    This forces a refresh of the audio file from whatever cache it's hiding
    (it's not in the WVR caches, since the usual command "rm -f
    /var/dirTalk/DTBE/native/aix/VXML2Cache/*
    /var/dirTalk/DTBE/native/aix/cache/*" does not help, and the old audio
    file is still cached if I don't use this trick.)

    After the new audio file is loaded once, I can remove the
    maxage/maxstale arguments to let it be cached again as designed.

    Needless to say, that is rather cumbersome.

    --
    Hubert Crepy
  • SystemAdmin
    SystemAdmin
    835 Posts

    Re: VoiceXML audio cache problem

    ‏2007-01-10T09:30:15Z  
    chris_churchill@manulife.com wrote:
    > The audio file is being cleared from the cache in the 2.7 hrs (after 8 hrs for sure). The problem I want to resolve is that after I install a new audio file I want to be able to test it right away. Not 3 or 8 hours later. Any other ideas?

    I've been having exactly the same need and problem lately, with WVR/S 4.2.
    The only workaround I've found was to temporarily modify my vxml source
    to add maxage and maxstale arguments:
    <audio src="./audio/myaudio.wav" maxage="0" maxstale="0">

    This forces a refresh of the audio file from whatever cache it's hiding
    (it's not in the WVR caches, since the usual command "rm -f
    /var/dirTalk/DTBE/native/aix/VXML2Cache/*
    /var/dirTalk/DTBE/native/aix/cache/*" does not help, and the old audio
    file is still cached if I don't use this trick.)

    After the new audio file is loaded once, I can remove the
    maxage/maxstale arguments to let it be cached again as designed.

    Needless to say, that is rather cumbersome.

    --
    Hubert Crepy
    I encountered this problem before, here is my solution:

    1. Telnet to the machine where WVR is installed.
    2. Login as dtuser.
    3. Issue "dtjstop"
    4. Issue "cd $CUR_DIR/voice/ext/v2c/<IP address>". <IP address> is the IP address of the machine where WVR is installed.
    5. Remove all directories and files under this path. (Using rm -rf)
    6. Issue "dtjstart".

    By applying the above procedures, you'll remove all audio caches for your voice applications.

    PengWen
  • SystemAdmin
    SystemAdmin
    835 Posts

    Re: VoiceXML audio cache problem

    ‏2007-01-11T12:39:43Z  
    I encountered this problem before, here is my solution:

    1. Telnet to the machine where WVR is installed.
    2. Login as dtuser.
    3. Issue "dtjstop"
    4. Issue "cd $CUR_DIR/voice/ext/v2c/<IP address>". <IP address> is the IP address of the machine where WVR is installed.
    5. Remove all directories and files under this path. (Using rm -rf)
    6. Issue "dtjstart".

    By applying the above procedures, you'll remove all audio caches for your voice applications.

    PengWen
    pwchen@tw.ibm.com wrote:
    > I encountered this problem before, here is my solution:

    Thanks for the tip, I'll try that next time the need arises.

    --
    Hubert Crepy
  • SystemAdmin
    SystemAdmin
    835 Posts

    Re: VoiceXML audio cache problem

    ‏2007-06-06T19:21:25Z  
    I encountered this problem before, here is my solution:

    1. Telnet to the machine where WVR is installed.
    2. Login as dtuser.
    3. Issue "dtjstop"
    4. Issue "cd $CUR_DIR/voice/ext/v2c/<IP address>". <IP address> is the IP address of the machine where WVR is installed.
    5. Remove all directories and files under this path. (Using rm -rf)
    6. Issue "dtjstart".

    By applying the above procedures, you'll remove all audio caches for your voice applications.

    PengWen
    > I encountered this problem before, here is my
    > solution:
    >
    > 1. Telnet to the machine where WVR is installed.
    > 2. Login as dtuser.
    > 3. Issue "dtjstop"
    > 4. Issue "cd $CUR_DIR/voice/ext/v2c/<IP address>".
    > <IP address> is the IP address of the machine where
    > WVR is installed.
    > 5. Remove all directories and files under this path.
    > (Using rm -rf)
    > 6. Issue "dtjstart".
    >
    > By applying the above procedures, you'll remove all
    > audio caches for your voice applications.
    >
    > PengWen
    I'm having a similar problem and thanks for the tip. In a production environment, though, it may not be enough. Issuing "dtjstop" will kill the browsers, which means downtime. Is there a less disruptive way to force refresh the audio cache? Thx -- lcua.