Resources - wrong path to a specific bundle - causes 404

[SN]

Hello,

Does any one know why resources would generate wrong path to a specific bundle.. Just in production

All the bundles are referenced properly on that screen but just one specific bundle doesn't have '/static' appended to it and neither it's name is hashed (all other are hashed) and that causes 404 for that bundle.

any idea what might be going wrong with that bundle.. It works fine locally and on staging, just production has the issue.

Sudhir 

 

[SN]

Okey, This is the exact bug that I am facing http://jira.grails.org/browse/GPRESOURCES-102

However unlike the ticket says - we are not on windows but linux and the issue is not with css but js files.

 

   

Sudhir 

 

---

From: "[hidden email]" <[hidden email]>
To: Grails-user <[hidden email]>
Sent: Monday, 30 July 2012 7:38 PM
Subject: [grails-user] Resources - wrong path to a specific bundle - causes 404

Hello,

Does any one know why resources would generate wrong path to a specific bundle.. Just in production

All the bundles are referenced properly on that screen but just one specific bundle doesn't have '/static' appended to it and neither it's name is hashed (all other are hashed) and that causes 404 for that bundle.

any idea what might be going wrong with that bundle.. It works fine locally and on staging, just production has the issue.

Sudhir 

 

[Marc Palmer Local]

On 30 Jul 2012, at 15:08, [hidden email] wrote:

> Hello,
>
> Does any one know why resources would generate wrong path to a specific bundle.. Just in production
> All the bundles are referenced properly on that screen but just one specific bundle doesn't have '/static' appended to it and neither it's name is hashed (all other are hashed) and that causes 404 for that bundle.
> any idea what might be going wrong with that bundle.. It works fine locally and on staging, just production has the issue.
>

This is likely the condition in pre-1.2-RC1 releases of Resources, where if a client (more likely for production instances) requests a bundle before it has been prepared by the newly running app.

This can happen if (a) you don't use cached-resources to create unique file names, and/or (b) you have multiple app instances in a cluster, where one creates the link to an ad hoc resource, but the other has not had that request, so its metadata differs.

Try 1.2-RC1.

Marc

~ ~ ~
Marc Palmer
Freelancer (Grails/Groovy/Java/UX)

I offer commercial support for Grails plugins from as low as $50/mo.
For details see: http://grailsrocks.com

Blog: http://www.anyware.co.uk | Resumé: http://www.anyware.co.uk/marc
Contributor @ http://grails.org |  Founder @ http://noticelocal.com
Developer @ http://weceem.org | Member @ http://spottymushroom.com
Twitter: http://twitter.com/wangjammer5 


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[SN]

Okey I will give a try with 1.2-RC1

However - 

1. we are using cached resources, and disabling hasandcache mapper fixes issue.

2. Issue does not happen with just newly running app - we haven't restarted server since last few days.

3. I was able to reproduce this issue in development environment as well, by enabling hasandcache mapper (earlier it was disabled in dev mode) - Issue happens only with those bundles which has multuple js files (don't know if css has the same issue, but in our case it was js).

4. Not specific to windows, can be reproduced consistently on linux as well.

Shortly I will reply with my results for 1.2 RC1

 

Thanks for the response

   

Sudhir 

 

---

From: Marc Palmer <[hidden email]>
To: [hidden email]
Sent: Monday, 30 July 2012 8:54 PM
Subject: Re: [grails-user] Resources - wrong path to a specific bundle - causes 404

On 30 Jul 2012, at 15:08, [hidden email] wrote:

> Hello,
>
> Does any one know why resources would generate wrong path to a specific bundle.. Just in production
> All the bundles are referenced properly on that screen but just one specific bundle doesn't have '/static' appended to it and neither it's name is hashed (all other are hashed) and that causes 404 for that bundle.
> any idea what might be going wrong with that bundle.. It works fine locally and on staging, just production has the issue.
>

This is likely the condition in pre-1.2-RC1 releases of Resources, where if a client (more likely for production instances) requests a bundle before it has been prepared by the newly running app.

This can happen if (a) you don't use cached-resources to create unique file names, and/or (b) you have multiple app instances in a cluster, where one creates the link to an ad hoc resource, but the other has not had that request, so its metadata differs.

Try 1.2-RC1.

Marc

~ ~ ~
Marc Palmer
Freelancer (Grails/Groovy/Java/UX)

I offer commercial support for Grails plugins from as low as $50/mo.
For details see: http://grailsrocks.com

Blog: http://www.anyware.co.uk | Resumé: http://www.anyware.co.uk/marc
Contributor @ http://grails.org |  Founder @ http://noticelocal.com
Developer @ http://weceem.org | Member @ http://spottymushroom.com
Twitter: http://twitter.com/wangjammer5


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[SN]

Marc - I tried with Resources 1.2-RC1 and i can still reproduce the issue consistently. And its not specific to windows, reproduces on linux as well.

Environment

Grails 1.3.7

Resources 1.2-RC1

Cached resources

Zipped resources

Disabling hashandcache mapper fixes the issue.

 

   

Sudhir 

 

---

From: "[hidden email]" <[hidden email]>
To: "[hidden email]" <[hidden email]>
Sent: Monday, 30 July 2012 9:42 PM
Subject: Re: [grails-user] Resources - wrong path to a specific bundle - causes 404

Okey I will give a try with 1.2-RC1

However - 

1. we are using cached resources, and disabling hasandcache mapper fixes issue.

2. Issue does not happen with just newly running app - we haven't restarted server since last few days.

3. I was able to reproduce this issue in development environment as well, by enabling hasandcache mapper (earlier it was disabled in dev mode) - Issue happens only with those bundles which has multuple js files (don't know if css has the same issue, but in our case it was js).

4. Not specific to windows, can be reproduced consistently on linux as well.

Shortly I will reply with my results for 1.2 RC1

 

Thanks for the response

   

Sudhir 

 

---

From: Marc Palmer <[hidden email]>
To: [hidden email]
Sent: Monday, 30 July 2012 8:54 PM
Subject: Re: [grails-user] Resources - wrong path to a specific bundle - causes 404

On 30 Jul 2012, at 15:08, [hidden email] wrote:

> Hello,
>
> Does any one know why resources would generate wrong path to a specific bundle.. Just in production
> All the bundles are referenced properly on that screen but just one specific bundle doesn't have '/static' appended to it and neither it's name is hashed (all other are hashed) and that causes 404 for that bundle.
> any idea what might be going wrong with that bundle.. It works fine locally and on staging, just production has the issue.
>

This is likely the condition in pre-1.2-RC1 releases of Resources, where if a client (more likely for production instances) requests a bundle before it has been prepared by the newly running app.

This can happen if (a) you don't use cached-resources to create unique file names, and/or (b) you have multiple app instances in a cluster, where one creates the link to an ad hoc resource, but the other has not had that request, so its metadata differs.

Try 1.2-RC1.

Marc

~ ~ ~
Marc Palmer
Freelancer (Grails/Groovy/Java/UX)

I offer commercial support for Grails plugins from as low as $50/mo.
For details see: http://grailsrocks.com

Blog: http://www.anyware.co.uk | Resumé: http://www.anyware.co.uk/marc
Contributor @ http://grails.org |  Founder @ http://noticelocal.com
Developer @ http://weceem.org | Member @ http://spottymushroom.com
Twitter: http://twitter.com/wangjammer5


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email