Liferay, Alfresco, LDAP, CAS and me bundle - Alfresco dies on startup

[Myles Penlington]

Hi,
Using the 1st sept bundle and provided instructions causes Alfesco to
die on startup with many errors. I have 2 different scenarios that
have quite different failure paths. Note that I have previously
installed other Alfresco/Liferay bundles, but all to different folders
etc. This is on a windows XP machine.

Case 1.
Use provided bundle with no mods. Fails as seen below. Complaining
about db schema upgrades and missing beans related to this. Conclusion
- very sick install.

Case 2.
Using another ApacheDS install running as a windows service on port
10389, with the dc=intalio,dc=com partition setup and populated with
the test data, still fails but seems to be much happier (far less
exceptions thrown).

Anybody got any ideas of what is wrong?
Thanks
Myles.


Logs from case 1 (Partial - no point posting another 4000 lines of
stack traces).
Starting Liferay Portal 5.1.0 (Calvin / Build 5100 / July 17, 2008)
23:24:07,262 INFO [ServerDetector:76] Detected server tomcat
23:24:07,309 INFO [HotDeployUtil:76] Initializing hot deploy manager
24675665
23:24:07,403 INFO [AutoDeployDir:76] Auto deploy scanner started for
C:\Documents and Settings\mylesp\liferay\deploy
23:24:15,774 WARN [CacheManager] Creating a new instance of
CacheManager using the diskStorePath "C:\LiferayAll\temp" which is
already used by an existing Cach
eManager.
The source of the configuration was URL of file:/C:/LiferayAll/webapps/
alfresco/WEB-INF/classes/alfresco/ehcache-transactional.xml.
The diskStore path for this CacheManager will be set to C:\LiferayAll
\temp\ehcache_auto_created_1220441055774.
To avoid this warning consider using the CacheManager factory methods
to create a singleton CacheManager or specifying a separate ehcache
configuration (ehcache
.xml) for each CacheManager instance.
23:24:30,455 ERROR [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'schemaBootstrap' defined in class path
resource [alfresco/bootstrap-cont
ext.xml]: Cannot resolve reference to bean 'patch.schemaUpdateScript-
V1.4-1' while setting bean property 'preUpdateScriptPatches' with key
[0]; nested exception
is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'patch.schemaUpdateScript-V1.4-1' defined in
file [C:\LiferayAll\weba
pps\alfresco\WEB-INF\classes\alfresco\patch\patch-services-
context.xml]: Cannot resolve reference to bean 'patchComponent' while
setting bean property 'patchSer
vice'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'patchComponent' defined in file [C:\LiferayAl
l\webapps\alfresco\WEB-INF\classes\alfresco\patch\patch-services-
context.xml]: Cannot resolve reference to bean 'descriptorComponent'
while setting bean propert
y 'descriptorService'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'descriptorComponent' defined
in class path resource [alfresco/bootstrap-context.xml]: Cannot
resolve reference to bean 'systemBootstrap' while setting bean
property 'systemBootstrap'; neste
d exception is
org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'systemBootstrap' defined in class path
resource [alfresco
/bootstrap-context.xml]: Cannot resolve reference to bean


Logs from Case 2
Starting Liferay Portal 5.1.0 (Calvin / Build 5100 / July 17, 2008)
23:26:57,811 INFO [ServerDetector:76] Detected server tomcat
23:26:57,873 INFO [HotDeployUtil:76] Initializing hot deploy manager
24493807
23:26:57,951 INFO [AutoDeployDir:76] Auto deploy scanner started for
C:\Documents and Settings\mylesp\liferay\deploy
23:27:05,557 WARN [CacheManager] Creating a new instance of
CacheManager using the diskStorePath "C:\LiferayAll\temp" which is
already used by an existing Cach
eManager.
The source of the configuration was URL of file:/C:/LiferayAll/webapps/
alfresco/WEB-INF/classes/alfresco/ehcache-transactional.xml.
The diskStore path for this CacheManager will be set to C:\LiferayAll
\temp\ehcache_auto_created_1220441225542.
To avoid this warning consider using the CacheManager factory methods
to create a singleton CacheManager or specifying a separate ehcache
configuration (ehcache
.xml) for each CacheManager instance.
23:27:06,307 WARN [LDAPInitialDirContextFactoryImpl] LDAP server
supports anonymous bind ldap://localhost:10389
23:27:07,838 WARN [RmiRegistryFactoryBean] Could not detect RMI
registry - creating new one
23:27:08,775 WARN [AbstractTriggerBean] Job ehCacheTracerJob is not
active
23:27:09,743 WARN [OpenOfficeConnectionTester] A connection to
OpenOffice could not be established.
23:27:12,648 WARN [ConfigurationFactory] No configuration found.
Configuring ehcache from ehcache-failsafe.xml found in the classpath:
jar:file:/C:/LiferayAll
/webapps/alfresco/WEB-INF/lib/ehcache-1.3.0.jar!/ehcache-failsafe.xml
23:27:12,648 WARN [CacheManager] Creating a new instance of
CacheManager using the diskStorePath "C:\LiferayAll\temp" which is
already used by an existing Cach
eManager.
The source of the configuration was classpath.
The diskStore path for this CacheManager will be set to C:\LiferayAll
\temp\ehcache_auto_created_1220441232648.
To avoid this warning consider using the CacheManager factory methods
to create a singleton CacheManager or specifying a separate ehcache
configuration (ehcache
.xml) for each CacheManager instance.
23:27:14,178 ERROR [ConfigurationChecker] CONTENT INTEGRITY ERROR:
System content not found in content store.
23:27:14,178 ERROR [ConfigurationChecker] Ensure that the 'dir.root'
property is pointing to the correct data location.
23:27:14,178 ERROR [ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Ensure that the
'dir.root' property is pointing to the correct data location.
at
org.alfresco.repo.admin.ConfigurationChecker.check(ConfigurationChecker.java:
312)
at org.alfresco.repo.admin.ConfigurationChecker.access
$000(ConfigurationChecker.java:72)
at org.alfresco.repo.admin.ConfigurationChecker
$1.execute(ConfigurationChecker.java:178)
at
org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:
225)
at
org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:
155)
at
org.alfresco.repo.admin.ConfigurationChecker.onBootstrap(ConfigurationChecker.java:
182)
at
org.alfresco.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:
62)
... still more entries

[Nicolas Modrzyk]

Hi Myles,

I will test extensively tomorrow (midnight here in Japan ..) on a
windows machine.

For the second error you're getting, it's because the content
repository failed the first time. You can delete the content
repository at var/alfresco to restart from scratch (also maybe re-init
the bpms database containing the alfresco tables).

Been suffering quite a lot already to get Alfresco running seamlessly
on *nix machines, looks like I need more sweat on windows.
Hope to help you on this really quickly.

Niko,

[Myles Penlington]

Hi Niko,

Have managed to Alfresco to sort of start up clean on Windows -
useable at least I think for testing.

1. Have to have ApacheDS running intially - else still throws those
errors mentioned intially in case 1.
2. Had to add the Win32NetBios.dll to the bin folder (from the right
Alfresco war version).
3. Edited the bpms script to remove all the alfresco tables (jpbm* and
alf*) and then recreated the bpms database.
4. Deleted the var/alfresco folders.
5. Then starts up okay, and recreates all the alfresco tables etc.

Have to agree that it does not seem to be plain sailing getting
alfresco running in combination with Liferay/Intalio etc.

Any reason you used Alfreso 2.1 rather than 2.2 and same for Liferay
ie. 5.1.0 vs 5.1.1?

Is still giving a warning on startup of

09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'AddTranslationWithoutContentDialog' - only keeping the
last

for every alfresco bean defined?

Thanks very much
It's been a huge help.
Myles.


PS: Still gives the following unexpected warnings on startup.

09:06:38,854 INFO [PortletHotDeployListener:203] Registering portlets
for alfresco
09:06:38,869 INFO [PortletHotDeployListener:210] 6 portlets for
alfresco are ready for registration
09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'MakeMultilingualDialog' - only keeping the last
09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'EditMLContainerDialog' - only keeping the last
09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'AddTranslationWithoutContentDialog' - only keeping the
last
09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'AddTranslationDialog' - only keeping the last
09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'LoginBean' - only keeping the last
09:06:39,213 WARN [FacesConfigurator] More than one managed bean w/
the name of 'NavigationBean' - only keeping the last

.... And about 50 more entries just the same for every alfresco bean?

09:06:39,260 WARN [FacesConfigurator] More than one managed bean w/
the name of 'FilePickerBean' - only keeping the last
09:06:39,260 WARN [FacesConfigurator] More than one managed bean w/
the name of 'DeploymentProgressBean' - only keeping the last
09:06:39,260 WARN [FacesConfigurator] More than one managed bean w/
the name of 'LinkValidationProgressBean' - only keeping the last
09:06:39,275 INFO [PortletHotDeployListener:292] 6 portlets for
alfresco registered successfully
09:06:45,679 WARN [TempoUsernamePasswordAuthenticationHandler]
org.intalio.tempo.cas.TempoUsernamePasswordAuthenticationHandler is
only to be used in a testing
environment. NEVER enable this in a production environment.
09:06:46,804 INFO [ThemeHotDeployListener:92] Registering themes for
liferay-jedi-theme
09:06:46,804 INFO [ThemeHotDeployListener:104] Themes for liferay-
jedi-theme registered successfully
09:06:51,552 INFO [[/tunnel-web]:647] Initializing Spring
FrameworkServlet 'SpringServlet'
09:07:07,359 INFO [PortletHotDeployListener:203] Registering portlets
for Intalio|BPMS User Interface Framework - Portlet
09:07:07,515 INFO [PortletHotDeployListener:210] 1 portlets for
Intalio|BPMS User Interface Framework - Portlet are ready for
registration
09:07:07,687 INFO [PortletHotDeployListener:292] 1 portlets for
Intalio|BPMS User Interface Framework - Portlet registered
successfully
09:07:08,859 INFO [PluginPackageUtil:76] Reloading repositories

[Nicolas Modrzyk]

Hi Myles,

This is very previous information you got us here. Thanks a lot.

1. I will include the sql scripts to include the drop tables next time.
2. Will add the dll to the bin folder
3. Not much I can do about deleting the var/alfresco folder. It's just
the way alfresco works.

We will probably update the two version of alfresco and liferay in the
next few days, but yes, It won't fixed the FacesConfigurator problem ;
If only we could just turn it off ... (> <)

Will keep you posted.

Niko,