Announcement

**Isomorphic** · 6 Apr 2011, 18:51

Assuming this is not a legitimate error (eg, you're running the server process in such a way that it really can't read/write to these files), then this looks like a bogus warning related to some kind of filesystem issue. Is this server running Windows? What version if so?

Have you considered setting up a script so that all assembled files are created in advance (if this is possible, eg, no user-dependent files)?

**senordhuff** · 6 Apr 2011, 19:02

No, this is a Linux server. And, we've successfully used FileAssembly for years in many different environments. And, it is oddly working properly in some cases right now but not in others.

It is definitely not a bogus warning though. I am looking at the content being delivered to the browser for the uri defined in FileAssembly like this:

Code:

      <FileAssemblyEntry uri="/js/at_js_public_static.js">
             <compress>true</compress>
             <components>
                  <component>
                     <type>file</type>
                     <fileName>/js/at_atproperties.js</fileName>
                     <jsStripping>full</jsStripping>
                     <jsObfuscation>1</jsObfuscation>
                 </component>
                 ...

and, it is returning that error message I pasted.

I'm not sure what you mean by setting up a script. Do you mean copying all of the files into the isomorphicCache/stripped directory via script rather than having your component do it at runtime?

**Isomorphic** · 6 Apr 2011, 19:05

What we meant by a "bogus warning" is whether it could possibly be legitimate that Java / the OS are reporting "Permission Denied" here. Unless the files are not writeable by the Unix userId that's running the server process, this error condition should be impossible, and is probably masking some other, real cause.

Are you seeing anything other than "Permission denied" as the error message when this happens?

Are you using any kind of unusual filesystem - NFS or something that might not support synchronous saves?

By using a script, we mean writing a simple Java program that would invoke the FileAssembler manually to cause all the files to be generated, so you could just deploy the already-assembled files with your application.

**senordhuff** · 6 Apr 2011, 19:18

Well, looking closely at the logs, I see that one of our two servers is responsible for all of these exceptions. And, it is throwing this warning in the logs right before it throws the exception originally pasted

2011-04-06 17:52:56,698 INFO [STDOUT] === 2011-04-06 17:52:56,698 [0-12] WARN FileAssembler - js/at_atproperties.js requests obfuscation level 1 - but this package is not capable of obfuscation - NOT OBFUSCATING

So, does that suggest this server has some permission problems? Or, perhaps there is a corrupt deploy on this one server?

I guess an easy fix would perhaps be to remove the obfuscation setting as well?

**Isomorphic** · 6 Apr 2011, 19:30

The different behavior certainly suggests a corrupt deployment. Perhaps you've got different server.properties settings in each deployment?

You should remove settings for jsObfuscation unless you're deeply familiar with this - it doesn't make much of a file size difference and it puts some subtle constraints on your JavaScript code.

**senordhuff** · 6 Apr 2011, 19:39

I really appreciate the prompt help. We should be able to figure it out from here.

Announcement

problem with FileAssembly

Comment

Comment

Comment

Comment

Comment

Comment