Alfresco Labs config issues

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

rsen

Hi,

I'm trying to install/configure a "demo" version of Labs 3 (Stable) on my desktop running WinXP. If this works, I plan to install the same on a WIn 2003 Server.
I've been working through a series of problems during the initial start-up and deployment of the webapps, where the alfresco WAR (web client ?) was failing consistently, while share and studio WAR's went through. Although it's finally at a point where the deployment looks clean and I can login to the Alfresco webapp and view the "My Alfresco" dashboard, I am still unable to login to either the share or studio apps.

The studio default page comes up blank with nothing but the logo and welcome message, while share does display the authentication dialog but then rejects the default admin credentials. I cannot find anything useful in either the Tomcat or Alfresco logs. The local firewall is completely disabled (I noticed blocked connection attempts from soffice.bin). I have not configured any DB or other repository properties, presuming that the in-built Derby backend would be pre-configured with default options during installation.

By way of background, I'm listing all the steps and issues encountered so far

1. Install complete non-JDK Alfresco bundle using. Note that the install wizard did NOT prompt for JDK location, but env var's JAVA_HOME and JRE_HOME already point to locally installed JDK (ver 1.6). Derby option selected for DB.

2. Server startup reported deployment failure on alfresco WAR due to RMI registration error (partial stack trace below), while share and studio deployment successful.
INFO: Initializing Spring root WebApplicationContext
Jun 20, 2009 10:35:09 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.remoting.rmi.RmiServiceExporter' defined in class path resource [alfresco/emailserver/email-service-context.xml]: Invocation of init method failed; nested exception is java.rmi.server.ExportException: internal error: ObjID already in use


3. Adding firewall rules to allow comm with RMI port and multiple server re-boots later, the alfresco context init failed again but this time with a classloader bootstrap issue caused by JAXB version mismatch (partial stack trace below). studio and share apps still deployed fine.
INFO: Initializing Spring root WebApplicationContext
Jun 21, 2009 9:59:18 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.cxf.wsdl.WSDLManager' defined in class path resource [META-INF/cxf/cxf.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]: Constructor threw exception; nested exception is java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/Alfresco/tomcat/webapps/alfresco/WEB-INF/lib/jaxb-impl-2.1.7.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.cxf.wsdl11.WSDLManagerImpl]: Constructor threw exception; nested exception is java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/Alfresco/tomcat/webapps/alfresco/WEB-INF/lib/jaxb-impl-2.1.7.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)


4. After copying the jaxb-api-2.1.jar to the tomcat\endorsed folder, the alfresco context init failed again but this time with a Hibernate session/connection issue caused by bad transaction state in the Derby database (partial stack trace below). studio and share apps still deployed fine.
INFO: Initializing Spring root WebApplicationContext
Jun 21, 2009 10:23:15 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'luceneIndexBackupComponent' defined in class path resource [alfresco/core-services-context.xml]: Invocation of init method failed; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Cannot open connection
Caused by: org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Cannot open connection
Caused by: org.hibernate.exception.GenericJDBCException: Cannot open connection
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
   …
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Failed to start database 'C:/Alfresco/alf_data/derby_data/alfresco', see the next exception for details.)
   … 48 more
Caused by: java.sql.SQLException: Failed to start database 'C:/Alfresco/alf_data/derby_data/alfresco', see the next exception for details.
   … 51 more
Caused by: java.sql.SQLException: Failed to start database 'C:/Alfresco/alf_data/derby_data/alfresco', see the next exception for details.
   … 65 more
Caused by: java.sql.SQLException: Another instance of Derby may have already booted the database C:\Alfresco\alf_data\derby_data\alfresco.
   … 62 more
Caused by: ERROR XSDB6: Another instance of Derby may have already booted the database C:\Alfresco\alf_data\derby_data\alfresco.


5. A few more re-boots later, the start-up log finally looks clean, all webapps reporting as correctly deployed in Tomcat manager, The Alfresco web client comes up, allows authentication using default admin credentials and displays the My Alfresco dashboard. However, neither share nor studio apps are usable (detailed summary above).

6. The error message trying to login to /share using admin/admin is "Failed to Login\n The remote server may be unavailable or your authentication details have not been recognized."

Any help or suggestions would be appreciated, pls lmk if I can provide any further info for diagnosis.

Regards,
/rsen

rsen

Hi,

The studio default page comes up blank with nothing but the logo and welcome message, while share does display the authentication dialog but then rejects the default admin credentials. I cannot find anything useful in either the Tomcat or Alfresco logs. The local firewall is completely disabled (I noticed blocked connection attempts from soffice.bin). I have not configured any DB or other repository properties, presuming that the in-built Derby backend would be pre-configured with default options during installation.

OK, found the problem: all the redirect URL's had hard-coded port numbers in them.