This project is archived and is in readonly mode.

#5202 ✓stale

Urgent: File cache fails to read

Reported by Sai | July 26th, 2010 @ 11:57 PM

Some one please help!

We tried to file cache and everything was fine in the mongrel server. When we switched to WAS, the cache file is created but it hangs (hung threads) when tries to read the file with over 25kb of size.

Has anyone experienced this issue before ? Any help would be greatly appreciated.

As we in a clustered env we hate to use memory cache..


Comments and changes to this ticket

  • Sai

    Sai July 26th, 2010 @ 11:59 PM


    Ruby - ruby 1.8.1 (2003-12-25) [i386-linux-gnu]
    Rails - Rails 2.3.8

    WAS - Websphere application server 7

  • iHiD

    iHiD July 27th, 2010 @ 04:43 PM

    I'm seeing a similar thing on 3.0.0rc1 on 1.9.2dev

    I don't know if it's related but I have the same symptom, which is my app hanging reading the cache. If I delete the cache between requests, it renders fine.

    This only happens in production mode, although I have config.action_controller.perform_caching on in BOTH modes.

    The only difference in my config files is that production.rb has:
    config.cache_classes = true

    I haven't tried production mode for about 3 weeks till today and it worked fine on rails trunk before then.

    This is NOT reproducible for me on a clean app. I will look to try and pinpoint it further.

  • Sai

    Sai July 28th, 2010 @ 02:17 AM

    Thanks for the reply ihid.

    <> This is exactly is the case with my app too.

    <<aven't tried production mode for about 3 weeks till today and it worked fine on rails trunk before then>> Means you have in DEV or TEST mode/environment ?

    <> I can easily simulate this issue in any app, that has filestore caching..

    Your help in this nightmare would be greatly appreciated.

    Thanks - Sai

  • Damien MATHIEU

    Damien MATHIEU July 28th, 2010 @ 09:02 AM

    Could you provide a test case ?

  • iHiD

    iHiD July 29th, 2010 @ 01:17 PM

    I'm updating our sandbox to the latest versions over the weekend so I'll try and track it down then, or at worst, get something reproducible.

  • Ryan Bigg

    Ryan Bigg October 11th, 2010 @ 05:01 AM

    • State changed from “new” to “needs-more-info”
    • Importance changed from “” to “Low”

    Please update this ticket with your findings.

  • Ryan Bigg

    Ryan Bigg October 19th, 2010 @ 08:25 AM

    • Tag cleared.

    Automatic cleanup of spam.

  • rails

    rails April 9th, 2011 @ 01:00 AM

    • State changed from “needs-more-info” to “open”

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

  • rails

    rails April 9th, 2011 @ 01:00 AM

    • State changed from “open” to “stale”

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href=""></a>

People watching this ticket