topic Re: JBoss server not starting after alfresco.war copied in Alfresco Archive

JBoss server not starting after alfresco.war copied

konsultex — Sat, 06 Jan 2007 18:26:55 GMT

I have a problem on Fedora Core 4 with JDK 1.5.0_10 and JBoss 4.0.5. I have 2 application running in the /server/default configuration that are working without any problems so I can vouch for the server. If I start the server with the alfresco war in /server/default/deploy nothing worksWhat I did i

Re: JBoss server not starting after alfresco.war copied

andy — Mon, 08 Jan 2007 09:46:47 GMT

Hi

You need to changes the debug settings for Alfresco within JBoss.
The default is indeed to log all debug messages for eveything. This is too much. You ned to restrict this to just INFO and enable anything else individually.

In ….\server\default\conf\log4j.xml you need to limit the debug … something like ….


…
   <!– ================ –>
   <!– Limit categories –>
   <!– ================ –>

   <!– Limit the org.apache category to INFO as its DEBUG is verbose –>
   <category name="org.apache">
      <priority value="INFO"/>
   </category>

   <!– Limit the org.jgroups category to WARN as its INFO is verbose –>
   <category name="org.jgroups">
      <priority value="WARN"/>
   </category>

   <!– Limit apache axis to INFO as its DEBUG is even more verbose –>
   <category name="org.jboss">
      <priority value="WARN"/>
   </category>
   
   <category name="net">
      <priority value="WARN"/>
   </category>
   
   <category name="org.hibernate">
      <priority value="WARN"/>
   </category>
   
   <category name="org.jboss.portal">
      <priority value="INFO"/>
   </category>
   
   <category name="org.jboss.portlet">
      <priority value="INFO"/>
   </category>
   
   <category name="org.alfresco">
      <priority value="INFO"/>
   </category>
   
   <category name="org.alfresco.repo.policy">
      <priority value="WARN"/>
   </category>
   
   <category name="org.alfresco.web">
      <priority value="DEBUG"/>
   </category>
   
   <category name="org.springframework">
      <priority value="WARN"/>
   </category>
   
   <category name="org.apache.myfaces">
      <priority value="INFO"/>
   </category>
   
   <category name="org.apache.myfaces.renderkit.html">
      <priority value="WARN"/>
   </category>
…
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Regards

Andy

Re: JBoss server not starting after alfresco.war copied

seanradford — Tue, 09 Jan 2007 12:33:37 GMT

Ah, but then you run into the java.io.NotSerializableException with org.apache.myfaces.el.MethodBindingImpl do you not?

– and if you play around with the myfaces source to see if you can fix that you end up with:

java.io.NotSerializableException: org.alfresco.web.bean.repository.QNameNodeMap

(and i haven't had time to see how/if that can be sorted)

Any suggestions, and I may be able to make time…

Re: JBoss server not starting after alfresco.war copied

konsultex — Tue, 09 Jan 2007 18:24:57 GMT

Thanks for the suggestions. Before going further, I want to point out that my JBoss does not have JBoss Portal installed. Could this be the reason for this strange behavior? If you confimr that I can run Alfresco without the portal them I think I should try to filter the log to see if I can detect the real problem.

Thanks.

Re: JBoss server not starting after alfresco.war copied

seanradford — Tue, 09 Jan 2007 19:11:13 GMT

I wouldn't say that not having the portal installed within JBoss is the cause - however you do seem to need it installed even if you end up running Alfresco as a standard WebApp (from memory, it tries to use some of the portal API classes).

Regards

Re: JBoss server not starting after alfresco.war copied

richmitc — Tue, 09 Jan 2007 19:37:05 GMT

Just for you information…

I did get it up and running, with HSQLDB to start, in a JBoss Portal 2.6.0DR1 installation.

I started with the JBoss community edition and moved the approriate config files and war into place. I, also, by trial-and-error and with the help of this forum, determine what changes I needed to make to the config files. This included changing the dir.root, making sure that took (the default configuration does not read in the file with the dir.root declaration!), and turning off the DEBUG as noted in the forum.

I haven't done much testing yet. I did log in and move around.

I'm excited to try and conceive of portal pages that have this portlet along with useful others.

I might also check if I can get this installation to operate against the content store and MySQL database of my earlier Tomcat edition install. It is just test data, and I can back it up as desired before I try.

I can give the details of what I moved over and changed if folks are interested. Let me know.

Re: JBoss server not starting after alfresco.war copied

mdbhokie — Tue, 09 Jan 2007 19:56:44 GMT

Thanks for the suggestions. Before going further, I want to point out that my JBoss does not have JBoss Portal installed. Could this be the reason for this strange behavior? If you confimr that I can run Alfresco without the portal them I think I should try to filter the log to see if I can detect the real problem.

Thanks.

I'm also trying this. I plan on using Liferay 4.2. I can get liferay to deploy by itself, but when I try to deploy alfresco I see the following error:

2007-01-09 14:46:27,100 ERROR [org.apache.commons.modeler.BaseModelMBean] Exception invoking method init
java.lang.reflect.UndeclaredThrowableException
   at org.apache.commons.logging.impl.Log4jProxy.log(Log4jProxy.java:296)
   at org.apache.commons.logging.impl.Log4jProxy.error(Log4jProxy.java:270)
   at org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:119)
   at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:507)
   at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
   at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
   at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
   at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
   at org.jboss.web.WebModule.startModule(WebModule.java:83)
   at org.jboss.web.WebModule.startService(WebModule.java:61)
   at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
   at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
   at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
   at $Proxy0.start(Unknown Source)
   at org.jboss.system.ServiceController.start(ServiceController.java:417)
   at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy38.start(Unknown Source)
   at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
   at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
   at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
   at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
   at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
   at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy39.start(Unknown Source)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
   at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy8.deploy(Unknown Source)
   at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
   at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
   at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
   at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
   at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
   at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
   at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
   at $Proxy0.start(Unknown Source)
   at org.jboss.system.ServiceController.start(ServiceController.java:417)
   at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy4.start(Unknown Source)
   at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy5.deploy(Unknown Source)
   at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
   at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
   at org.jboss.Main.boot(Main.java:200)
   at org.jboss.Main$1.run(Main.java:490)
   at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.OutOfMemoryError: PermGen space
2007-01-09 14:46:27,116 WARN [org.jboss.system.ServiceController] Problem starting service jboss.web.deployment:war=portal-web.war,id=-1124876655
org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.management.RuntimeOperationsException: Exception invoking method init)
…
Caused by: java.lang.OutOfMemoryError: PermGen space
2007-01-09 14:46:27,116 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

— Incompletely deployed packages —
org.jboss.deployment.DeploymentInfo@bcf3be91 { url=file:/C:/jboss-4.0.5.GA/server/default/deploy/liferay-portal.ear/portal-web.war }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: Error during deploy; - nested throwable: (javax.management.RuntimeOperationsException: Exception invoking method init)
state: FAILED
watch: file:/C:/jboss-4.0.5.GA/server/default/deploy/liferay-portal.ear/portal-web.war
altDD: null
lastDeployed: 1168371955497
lastModified: 1168371953742
mbeans:

org.jboss.deployment.DeploymentInfo@10800a8d { url=file:/C:/jboss-4.0.5.GA/server/default/deploy/liferay-portal.ear/tunnel-web.war }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Created
state: CREATED
watch: file:/C:/jboss-4.0.5.GA/server/default/deploy/liferay-portal.ear/tunnel-web.war
altDD: null
lastDeployed: 1168371958881
lastModified: 1168371955607
mbeans:

org.jboss.deployment.DeploymentInfo@665b5564 { url=file:/C:/jboss-4.0.5.GA/server/default/deploy/liferay-portal.ear/ }
deployer: org.jboss.deployment.EARDeployer@16ef705
status: Deployment FAILED reason: Error during deploy; - nested throwable: (javax.management.RuntimeOperationsException: Exception invoking method init)
state: FAILED
watch: file:/C:/jboss-4.0.5.GA/server/default/deploy/liferay-portal.ear/META-INF/application.xml
altDD: null
lastDeployed: 1168371958881
lastModified: 1168362456745
mbeans:

— MBeans waiting for other MBeans —
ObjectName: jboss.web.deployment:war=portal-web.war,id=-1124876655
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.management.RuntimeOperationsException: Exception invoking method init)

— MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM —
ObjectName: jboss.web.deployment:war=portal-web.war,id=-1124876655
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.management.RuntimeOperationsException: Exception invoking method init)

2007-01-09 14:46:27,226 INFO [org.apache.coyote.http11.Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
2007-01-09 14:46:30,626 ERROR [STDERR] Exception in thread "http-0.0.0.0-8080"
2007-01-09 14:46:30,626 ERROR [STDERR] java.lang.NoClassDefFoundError: org/apache/coyote/http11/Http11Processor
2007-01-09 14:46:31,675 ERROR [STDERR]    at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.init(Http11BaseProtocol.java:617)
2007-01-09 14:46:31,691 ERROR [STDERR]    at org.apache.coyote.http11.Http11Protocol$JmxHttp11ConnectionHandler.init(Http11Protocol.java:134)
2007-01-09 14:46:31,691 ERROR [STDERR]    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.start(MasterSlaveWorkerThread.java:131)
2007-01-09 14:46:31,691 ERROR [STDERR]    at org.apache.tomcat.util.net.PoolTcpEndpoint.newWorkerThread(PoolTcpEndpoint.java:595)
2007-01-09 14:46:31,691 ERROR [STDERR]    at org.apache.tomcat.util.net.PoolTcpEndpoint.createWorkerThread(PoolTcpEndpoint.java:574)
2007-01-09 14:46:31,691 ERROR [STDERR]    at org.apache.tomcat.util.net.PoolTcpEndpoint.run(PoolTcpEndpoint.java:631)
2007-01-09 14:46:31,691 ERROR [STDERR]    at java.lang.Thread.run(Thread.java:595)
2007-01-09 14:47:36,355 ERROR [STDERR] Exception in thread "ScannerThread"
2007-01-09 14:47:36,355 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space

Re: JBoss server not starting after alfresco.war copied

seanradford — Tue, 09 Jan 2007 22:37:45 GMT

What version of the JBoss AS is JBoss Portal 2.6.0DR1 based upon? The NotSerializableException is a result of the versions of MyFaces and Tomcat (5.5) in JBoss AS 4.0.5 apparently.

Re: JBoss server not starting after alfresco.war copied

richmitc — Tue, 09 Jan 2007 22:46:42 GMT

The jboss.log file says 4.0.4.GA.

Note, this is a DR - Developer Release. It just happens to be what I was working with at the moment.

Also, mine is installed on Fedora Core 6.

Also, remember, I have only logged in and moved around. Nothing significant yet.

All the best…

Re: JBoss server not starting after alfresco.war copied

seanradford — Tue, 09 Jan 2007 23:19:08 GMT

Ah, I think that'll be the reason you have got yours working. I have an application that runs on 4.0.5 and want to get Alfresco running on that along-side it…

Re: JBoss server not starting after alfresco.war copied

konsultex — Wed, 10 Jan 2007 01:29:46 GMT

Thanks a lot for the info and ideas. I decided to give it another try before installing the portal and put almost everything in WARN and INFO. I got the server to start (in 1 minute and 23 seconds with my 2 applicationas plus Alfresco)) and got the Alfresco main page. I have not played around with it yet.

So my conclusion is that the portal is NOT needed and my previous problem may have had to do with the immense number of log messages saturating the system. I only messed around in log4j.xml this time so why it now works is a mystery to me.

To wrap it up:

Fedora core 4
java jdk 1.5.0_10
jboss 4.0.5GA (zip install)
alfresco 1.4 community

Apparently work together (at least enough to start up).

Re: JBoss server not starting after alfresco.war copied

seanradford — Wed, 10 Jan 2007 09:17:46 GMT

Just click the 'log in' and see what happens - that's when I get the NotSerializableException

Re: JBoss server not starting after alfresco.war copied

konsultex — Fri, 02 Feb 2007 01:15:35 GMT

Sean; Sorry, I did not see this comment until today. Well, I logged in fine so I think the problem lies not with Jboss or Alfresco.

However, I made a small change to my JBoss installation. The init script for starting it from /etc/rc.d/init.d was not picking up the value for $JAVA_HOME (although it had $JBOSS_HOME fine and I set both of those in /etc/profile.d/jboss.sh), so I just defined $JAVA_HOME in this init scrit again. I think this might have been causing JBoss to ponit to thr JRE instead of the JDK. I found out when I once started JBoss by running bin/run.sh manually on the console. I did this because on one occasion I had JBoss crash due to an apparent out of memory error and I went to investigate. I'm not sure that this helps or even solves the problem which may lie elsewhere. But so far Alfresco is working for me. Keep in mind that due to lack of time I haven't done any work on it except create users.