[coldbox:17391] [wirebox-1.5+] Error related to system/aop/tmp files

Communities ColdBox HMVC
1

Hi Wade,

This directory should have writeable permission /system/aop/tmp/ “/tmp”

2

Thanks Sana,

I will double-check my premissions on the “/tmp” folder!

3

I set the permissions on this directory to full access (777) on the server, and the error is still coming up. I happens for some users but not others and it seems to come and go. When I deploy changes to the server I reinit the framework rather than doing a full restart of tomcat… not sure if that is related or not.

Is there anything else I should check?

Thanks

4

Ahhhh what version of Railo are you on, I see 3.3.1 I believe this was a bug in Railo in that version that was resolved in a patch.

signature0.jpg

Luis F. Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com

ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com

Social: twitter.com/lmajano facebook.com/lmajano

5

I am on Railo 3.3.1 and unfortunately I’m stuck there until I can find a way to work around this issue with newer versions (https://issues.jboss.org/browse/RAILO-1785). Based on EJ’s post, I’m not sure a new version of Railo will help with the issue.

Aside from this issue, I couldn’t be happier with Wirebox. Nice work, and thanks for the help!

6

Unfortunately I cannot replicate it

Luis Majano
CEO
Ortus Solutions, Corp
Toll Free/Fax: 1-888-557-8057
Direct: 909-248-3408
www.ortussolutions.com
Twitter: @lmajano, @ortussolutions

7

I need to do some more testing to be sure, but I believe I have a repeatable scenario for reproducing this error on our test server. If I upload a change to the server, then re-init Wirebox, the error starts happening for everyone except me. I have the framework in the application scope so it’s odd that other people see the issue when I don’t, but that is what is happening. The load on our test server is so light and sporadic that I’m not always sure if things are working for everyone, or if no one is currently using it.

I re-init the server all the time in my development environment and never have an issue, but I’m the only one in that environment. Also, when I restart Tomcat/Railo after deploying changes to our test server I don’t see this issue. I’ll do a little more testing in our server environment to see if my scenario is as repeatable as I think it is and let you know what I find. Worst case, it looks like I can avoid the issue by restarting Tomcat/Railo after deploying changes.

Wade

8

Thanks wade. Also can you refresh me that this occurs when using AOP right?

Also, what type of caching do you have in railo for templates

Luis Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.com

ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Social: twitter.com/ortussolutions | twitter.com/coldbox | twitter.com/lmajano

9

I am using AOP. I am using the built in “wirebox.system.aop.aspects.CFTransaction” aspect, and a custom aspect I created for security.

I have the “Once” caching setup on the test server. I plan to change that to “Never” when we get to production, since our deployments will be more controlled and will involve a tomcat/railo restart.

Here is the code I am using to reinit the framework:

remote void function reloadFramework()
{
SystemCacheClear(“all”);lock scope=“application” type=“exclusive” timeout=“10”
{
application.wirebox = createObject(“component”,“wirebox.system.ioc.Injector”).init(“WireBox”);
}
}