cancel
Showing results for 
Search instead for 
Did you mean: 

Error when deploying alfresco.war on Windows platform

lcandido
Champ in-the-making
Champ in-the-making
I have installed a lot of Alfresco servers - Community Edition - on RHEL platform without any problem. The way is install the Tomcat and the JRE in the candidate Alfresco server and a remote corporative PostgreSQL BD. Then, unzip the alfresco-community-xxx.zip file, put the folders into theirs correct places and edit the configuration files, specially the global properties, and start the application server to deploy the alfresco.war and share.war files.

I did this on na Windows 2008 Server R2, but the error listed bellow has occurred. Note that the deploy of Share has been completed: its login page is presented to users, but it's impossible to log in, once the BD tables were empty due to the previous error in alfresco.war deploy.

To debug, I've tried do use the regular Alfresco Community pack (alfresco-community-4.2.b-installer-win-x64.exe) choosing the remote PostgreSQL BD. The result was exactly the same. Finally, I did a "total local" installation with the local PostgreSQL from the bundle. It works! Installation with no error. Does the problem came from the corporative BD?

So, if anyone know what is happening, I really appreciate all the help you can give me.

Thanks,


FILE c:\tomcat\logs\catalina.2012-11-16:

Nov 16, 2012 10:14:48 AM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR version 1.4.6.
Nov 16, 2012 10:14:48 AM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Nov 16, 2012 10:14:49 AM org.apache.catalina.core.AprLifecycleListener initializeSSL
INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
Nov 16, 2012 10:14:49 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-8080"]
Nov 16, 2012 10:14:49 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-apr-8009"]
Nov 16, 2012 10:14:49 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1969 ms
Nov 16, 2012 10:14:49 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 16, 2012 10:14:49 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.28
Nov 16, 2012 10:14:49 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\alfresco.war
Nov 16, 2012 10:14:55 AM org.apache.catalina.core.StandardContext addApplicationListener
INFO: The listener "org.apache.myfaces.webapp.StartupServletContextListener" is already configured for this context. The duplicate definition has been ignored.

Nov 16, 2012 10:15:11 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
Nov 16, 2012 10:15:11 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/alfresco] startup failed due to previous errors
Nov 16, 2012 10:15:11 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/alfresco] created a ThreadLocal with key of type [com.sun.xml.bind.v2.ClassFactory$1] (value [com.sun.xml.bind.v2.ClassFactory$1@68a9f8a1]) and a value of type [java.util.WeakHashMap] (value [{class javax.xml.bind.annotation.W3CDomHandler=java.lang.ref.WeakReference@6f0247b5}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Nov 16, 2012 10:15:11 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/alfresco] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@7eb1f502]) and a value of type [org.apache.cxf.bus.CXFBusImpl] (value [org.apache.cxf.bus.CXFBusImpl@554c9749]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

Nov 16, 2012 10:15:11 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\share.war
Nov 16, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\docs
Nov 16, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\examples
Nov 16, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\host-manager
Nov 16, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\manager
Nov 16, 2012 10:15:26 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\apache-tomcat-7.0.28-windows-x64\apache-tomcat-7.0.28\webapps\ROOT
Nov 16, 2012 10:15:26 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8080"]
Nov 16, 2012 10:15:26 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8009"]
Nov 16, 2012 10:15:26 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 37031 ms
4 REPLIES 4

mrogers
Star Contributor
Star Contributor
Need your alfresco.log rather than catialina.log

lcandido
Champ in-the-making
Champ in-the-making
The old installations of release 3.4.d on RHEL have the alfresco.log file, but the all-new 4.2.b on Windows 2008 Server whose installation have failed haven't, only the catalina, host-manager, localhost, localhost_access and manager log files. The well-succeed installaton from alfresco-community-4.2.b-installer-win-x64.exe file has alfrescotomcat-stderr and alfrescotomcat-stdout log files. It seems that when error has occurred these log files haven't been created yet.

Thanks a lot,

jonbarril
Champ in-the-making
Champ in-the-making
I just got nailed by this very same problem – waiting for the answer.

lcandido
Champ in-the-making
Champ in-the-making
After some trials I'm quite sure that the problem comes from the server configuration. Another installation on a workstation has connected to the DB, created the tables and is running fine. So the problem is just the connection from Alfresco server (the platform) to BD server, it don't seem to be an Alfresco issue.

Thanks to everyone,