topic Re: On Debian : LogConfigurationException on Tomcat deploy in Alfresco Archive

On Debian : LogConfigurationException on Tomcat deploy

liotier — Fri, 27 Oct 2006 17:03:25 GMT

Hi, I am encountering this exception on the deployment of Alfresco by Tomcat ct 27, 2006 6:56:42 PM org.apache.catalina.startup.HostConfig deployWARSEVERE: Error deploying web application archive alfresco.warorg.apache.commons.logging.LogConfigurationException: java.lang.ExceptionInInitializerErro

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Mon, 30 Oct 2006 15:42:33 GMT

I just try with Alfresco 1.3 and I have exactly the same results.

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Mon, 30 Oct 2006 15:48:32 GMT

Same thing with 1.2.1

I certainly have a Log4J problem but I don't understand it…

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Mon, 30 Oct 2006 17:07:56 GMT

A french user noted the following line :

Caused by: java.security.AccessControlException: access denied (java.io.FilePermission alfresco.log write)‍

He hinted that it might be a stupid write permission problem and I tend to agree. I'll keep this thread posted.

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Fri, 12 Jan 2007 14:16:59 GMT

Problem still not solved - but I won't give up. I'll keep this thread posted when I find a solution.

Re: On Debian : LogConfigurationException on Tomcat deploy

marco — Sun, 14 Jan 2007 15:58:19 GMT

My work-around is:

In /var/lib/tomcat5.5/webapps/alfresco/WEB-INF/classes/log4j.properties change:
log4j.appender.File.File=/var/log/tomcat5.5/alfresco.log

Check that tomcat55 is the owner of the this log directory.

In /etc/default/tomtom5.5 change:
TOMCAT5_SECURITY=no

The last point is the one which I don't like. Above all because I'm not aware of the implications. If you know please tell me!

Regards,
Marco

Re: On Debian : LogConfigurationException on Tomcat deploy

marco — Mon, 15 Jan 2007 14:09:15 GMT

How can I make an equivalent change in tomcat5.5/shared/classes/alfresco/extension/ instead of tomcat5.5/webapps/alfresco/WEB-INF/classes/?

I can't find where log4j.properties is imported.

/m

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Fri, 19 Jan 2007 17:50:38 GMT

My work-around is:

In /var/lib/tomcat5.5/webapps/alfresco/WEB-INF/classes/log4j.properties change:
log4j.appender.File.File=/var/log/tomcat5.5/alfresco.log

Check that tomcat55 is the owner of the this log directory.

In /etc/default/tomtom5.5 change:
TOMCAT5_SECURITY=no

It sure did something positive as I have now moved on to a whole new 100 classes deep exception - looks like my database is not quite well configured…

Anyway thanks you for the help.

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Fri, 19 Jan 2007 18:19:09 GMT

It sure did something positive as I have now moved on to a whole new 100 classes deep exception - looks like my database is not quite well configured…

Problem solved… For the first time Tomcat 5.5 launches with Alfresco 1.4 with no fatal exception apart from the ones complaining it can't bind on the FTP port nor the SMB one. And I still can't connect to it but I have to deal with strict firewalling so that shall probably be solved soon…

Feels good to be moving forward again…

Re: On Debian : LogConfigurationException on Tomcat deploy

marco — Wed, 24 Jan 2007 10:42:10 GMT

liotier,

How did you solve the permission conflict with the log file?

/m

Re: On Debian : LogConfigurationException on Tomcat deploy

liotier — Wed, 24 Jan 2007 11:38:11 GMT

How did you solve the permission conflict with the log file?

- I gave ownership of /var/log/tomcat5.5/alfresco.log to the tomcat55 user.
- I added TOMCAT5_SECURITY=no to /etc/default/tomtom5.5

Re: On Debian : LogConfigurationException on Tomcat deploy

jml75 — Thu, 10 May 2007 19:55:27 GMT

Here is how i fixed this problem:

In "/etc/tomcat5.5/policy.d/40webapps.policy"

I added the following line at the end :

grant codeBase "file:/var/lib/tomcat5.5/webapps/alfresco/-" {
permission java.io.FilePermission "/var/log/tomcat5.5/alfresco.log", "read,write";
};

and it fixed the permission problem for file /var/log/tomcat5.5/alfresco.log without turning tomcat5.5's security.

But then I have new problems regarding security.

So I think that this shows the right direction for the config of Tomcat. I just have to fond the rest of the changes I have to do.

I'll keep you guys posted!

Thanx!

Re: On Debian : LogConfigurationException on Tomcat deploy

jlhenry — Thu, 31 May 2007 21:34:18 GMT

Hello,

Thanks for this help!

I tried it and it works for me too. I'm no trying to resolve the other errors but stop on one quite difficult.

First this error does not seems to be tomcat_security related (as there is no "denied" message), but when I use "TOMCAT5_SECURITY=no" alfresco works like a charm and there is no error!

First here is the result of my work trying to complete this file: /etc/tomcat5.5/policy.d/40webapps.policy :

grant codeBase "file:/var/lib/tomcat5.5/webapps/alfresco/-" {
        permission java.io.FilePermission "/var/log/tomcat5.5/alfresco.log", "read,write";
        permission java.net.SocketPermission "java.sun.com:80", "connect,resolve";
        permission java.lang.RuntimePermission "shutdownHooks";
        permission java.security.SecurityPermission "putProviderProperty.CryptixCrypto";
        permission java.security.SecurityPermission "insertProvider.CryptixCrypto";
        permission java.util.PropertyPermission "alfresco.jmx.dir", "read,write";
        permission java.util.PropertyPermission "form.name", "read";
        permission java.util.PropertyPermission "avm.remote.port", "read";
        permission java.util.PropertyPermission "source", "read";
        permission java.util.PropertyPermission "options", "read";
        permission java.util.PropertyPermission "target", "read";
        permission java.util.PropertyPermission "cache.strategy", "read";
        permission java.util.PropertyPermission "db.script.dialect", "read";
        permission java.lang.RuntimePermission "accessDeclaredMembers";
        permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
        permission java.util.PropertyPermission "user.home", "read";
        permission java.util.PropertyPermission "user.dir", "read";
        permission java.util.PropertyPermission "java.io.tmpdir", "read";
        permission java.util.PropertyPermission "net.sf.ehcache.disabled", "read";
        permission java.util.PropertyPermission "net.sf.ehcache.useLRUMap", "read";
};

As you can see, I've resolved a certain number of issues.

But it seems that there is more to be done as my file is full of error. I'll not dump it all here, but there are error lines like this one:
14:34:52,862 ERROR [org.hibernate.proxy.BasicLazyInitializer] CGLIB Enhancement failed: org.alfresco.repo.avm.MergeLinkImpl

It's not always "org.alfresco.repo.avm.MergeLinkImpl", it's also "org.jbpm.graph.exe.ProcessInstance", "org.jbpm.context.log.VariableLog"…. In fact, I have 117 lines like this one!…

Looks like this error, but it's not exactly the same: http://www.hibernate.org/116.html#A5

Any idea here ????

…. I definitely do not like using "TOMCAT5_SECURITY=no"

Jluc

Re: On Debian : LogConfigurationException on Tomcat deploy

jml75 — Tue, 05 Jun 2007 19:10:12 GMT

Hi jlhenry,

I'm at the same point than you now.

I found out the same as you, the same twenty permissions are granted on my server and now I too have errors in the alfresco.log file.

I'll keep on looking on my side and keep you posted with my findings.

Please do the same to.

Jonathan

Re: On Debian : LogConfigurationException on Tomcat deploy

jml75 — Tue, 12 Jun 2007 20:10:21 GMT

How can I make an equivalent change in tomcat5.5/shared/classes/alfresco/extension/ instead of tomcat5.5/webapps/alfresco/WEB-INF/classes/?

I can't find where log4j.properties is imported.

/m

I finally found a way to bypass this!!!

Simply copy the file "/var/lib/tomcat5.5/webapps/alfresco/WEB-INF/classes/log4j.properties" in "/usr/share/tomcat5.5/common/classes" and edit it there.

After just restart tomcat server!

P.S.: I don't know thought if this will interfere with any other tomcat apps…

Re: On Debian : LogConfigurationException on Tomcat deploy

jml75 — Wed, 13 Jun 2007 15:54:58 GMT

Sorry for editing again my post.

Actually, my trick works only intermittently. Some times it works, some times it does not work.

I just don't get it.

Any one has an other idea else than turning off tomcat security?

Re: On Debian : LogConfigurationException on Tomcat deploy

fms — Wed, 04 Jul 2007 21:29:09 GMT

… is to grant Alfresco all permissions; in /etc/tomcat5.5/policy.d/04webapps.policy (this is the file I have in unstable):

Just to clarify things, this is rather different than turning security off: it simply means that I trust this application. Also, keep in mind that if you don't play to have developers deploying applications on your server, and you simply need to run Alfresco, there is little point in turning tomcat security on.

I should also mention that, in my experience, on top of the packages mentioned in the first post, you also need tomcat5.5-admin, otherwise Alfresco (and I'd suppose, any application) will not deploy. I didn't check whether it starts when tomcat is started, since I didn't care much.

There has always been a short period when I got this error when deploying Alfresco:

(I got it again today by trying to use the list of permissions mentioned in the forum). I solved it by binding Tomcat to port 8080, which Alfresco tries to use, rather than the default of 8180; this is changed in the file /etc/tomcat5.5/server.xml, find the section that reads

and change 8180 to 8080. I don't know how, but this issue disappeared: today, if I give Alfresco all permissions, I can have Tomcat on 8180 and Alfresco on 8080 - as it is reasonable, since "all permissions" should allow to bind to a port.

Another issue I had was that sometimes Alfresco deployment starts before Tomcat startup is complete. In this situation, I undeploy and redeploy Alfresco- this is ugly, I'm looking for a better solution. Anyway, this is a potential source of intermittent errors.

I'll be glad to help if anybody has further problems. Keep in mind that I am on a costantly upgraded "unstable" Debian machine.