Print  
Gray star Gray star Gray star Gray star Gray star --Not rated--
1180 Visits 10 Comments
Created
f pernet f pernet
Jul 14, 2009 11:54 PM
Kablink Component
  • Teaming

Hi all,

problemes running teaming for the first time. SLES10SP2 with jdk1.5.0_19.

a) Please update install script to change catalina.sh with correct timezone (i did it myself otherwise the catalina.out has incorrect timestamps (GMT) ).

b) When starting teaming, catalina out pointed some errors. In order to go further (i am not a java developper ), i put remarks on the relevant part of the file:
/teaming/teaming2/config/apache-tomcat-6.0.18/webapps/ssf/WEB-INF/context/applicationContext.xml

here are the sections i was obliged to put in rem (mainly because of zoneModule and Proxy directives):

<!-- FPE Change
<bean id="defaultEmailFormatter" parent="dependOnCommonServicesTemplate" class="org.kablink.teaming.module.mail.impl.Defaul tEmailFormatter" depends-on="notifyBuilderUtil">
...
</bean>
-->

<!-- FPE change
<bean id="dashboardHelper" class="org.kablink.teaming.web.util.DashboardHelpe r" parent="dependOnAllModulesTemplate"/>
-->

<!-- FPE change
<bean id="ssfs" class="org.springframework.aop.framework.ProxyFact oryBean" depends-on="sPropsUtil">
...
</bean>
-->

<bean id="smtpService" parent="dependOnCommonServicesTemplate" class="org.kablink.teaming.smtp.impl.SMTPManagerIm pl"
depends-on="zoneConfig, springContextUtil">
<property name="enabled"><value>${smtp.service.enable}</value></property>
<property name="bindAddress"><value>${smtp.service.bindAddre ss}</value></property>
<property name="port"><value>${smtp.service.port}</value></property>
<property name="tls"><value>${smtp.service.tls}</value></property>
<!-- FPE change <property name="zoneModule"><ref bean="zoneModule"/></property> -->
<property name="binderModule"><ref bean="binderModule"/></property>
</bean>

<bean id="accessTokenValidationInterceptor" class="org.kablink.teaming.remoting.ws.interceptor .AccessTokenValidationInterceptor">
<property name="accessTokenManager"><ref local="accessTokenManager"/></property>
<!-- FPE change <property name="zoneModule"><ref bean="zoneModule"/></property> -->
</bean>

<!-- FPE change
<bean id="templateService" parent="wsProxyTemplate">
<property name="target">
...
</bean>
+ all beans with parent="wsProxyTemplate"
<bean id="searchService" parent="wsProxyTemplate">
...
</bean>

<bean id="definitionService" parent="wsProxyTemplate">

</bean>

<bean id="folderService" parent="wsProxyTemplate">
...
</bean>

<bean id="migrationService" parent="wsProxyTemplate">
...
</bean>

<bean id="binderService" parent="wsProxyTemplate">
...
</bean>

<bean id="icalService" parent="wsProxyTemplate">
...
</bean>

<bean id="ldapService" parent="wsProxyTemplate">
...
</bean>

<bean id="licenseService" parent="wsProxyTemplate">
...
</bean>

<bean id="profileService" parent="wsProxyTemplate">
...
</bean>

<bean id="zoneService" parent="wsProxyTemplate">
...
</bean>

<bean id="adminService" parent="wsProxyTemplate">
...
</bean>
-->

Unfortunatly, even with these lines avoided, i still have an error ... here is it in catalina.out.

PATH=/usr/java/jdk1.5.0_19/bin:/usr/java/jdk1.5.0_19/bin:/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin}
2009-07-14 14:59:22,099 WARN [main] [org.hibernate.impl.SessionFactoryObjectFactory] - InitialContext did not implement EventContext
2009-07-14 14:59:23,084 INFO [main] [org.kablink.teaming.license.LicenseManager] - Loading license
2009-07-14 14:59:23,960 INFO [main] [com.novell.teaming.docconverter.impl.TextStellentC onverter] - DOCCONVERTER: Loading config/docconverter.cfg
2009-07-14 14:59:24,228 INFO [main] [com.novell.teaming.docconverter.impl.HtmlStellentC onverter] - HTMLCONVERTER: Loading config/htmlconverter.cfg
2009-07-14 14:59:28,212 ERROR [main] [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'zoneModule' defined in ServletContext resource [/WEB-INF/context/additionalContext.xml]: Cannot create inner bean 'com.novell.teaming.module.zone.impl.StandaloneZon eModule#18d7ace' of type [com.novell.teaming.module.zone.impl.StandaloneZone Module] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name 'com.novell.teaming.module.zone.impl.StandaloneZon eModule#18d7ace' defined in ServletContext resource [/WEB-INF/context/additionalContext.xml]: Invocation of init method failed; nested exception is org.kablink.teaming.search.LuceneException: Could not open writer on the index [/teaming/teaming2/lucene/lucene/liferay.com_1] / java.io.FileNotFoundException: no segments* file found: files:
at org.springframework.beans.factory.support.BeanDefi nitionValueResolver.resolveInnerBean(BeanDefinitio nValueResolver.java:230)
at org.springframework.beans.factory.support.BeanDefi nitionValueResolver.resolveValueIfNecessary(BeanDe finitionValueResolver.java:117)
at org.springframework.beans.factory.support.Abstract AutowireCapableBeanFactory.applyPropertyValues(Abs tractAutowireCapableBeanFactory.java:1245)
at ...etc...etc


Does anybody has an idea ?

thx

Workflow
Process State Action
Discussion workflow Active
This entry is currently active
Attachments(0)
Entry History
Tags
  
Replies
Thumbnail Image
Marcel Dekker Marcel Dekker
Jul 16, 2009 8:56 AM

In order to help you out you need to remove the rem for the lines you mention, startup Tomcat and send us the catalina.out file. You shouldn't remove anything in the file.
Thumbnail Image
f pernet f pernet
Jul 17, 2009 2:00 AM

OK you are right. I put back GMT in catalina.sh and remove all remarks in the other file. So I am back to regular situation.

The first error in catalina.out is:

PYTHONSTARTUP=/etc/pythonstart
PATH=/usr/java/jdk1.5.0_19/bin:/opt/gnome/sbin:/root/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin}
2009-07-14 08:50:24,777 WARN  [main] [org.hibernate.impl.SessionFactoryObjectFactory] - InitialContext did not implement EventContext
2009-07-14 08:50:26,073 INFO  [main] [org.kablink.teaming.license.LicenseManager] - Loading license
2009-07-14 08:50:26,956 INFO  [main] [com.novell.teaming.docconverter.impl.TextStellentConverter] - DOCCONVERTER: Loading config/docconverter.cfg
2009-07-14 08:50:31,348 ERROR [main] [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultEmailFormatter' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Cannot resolve ref
erence to bean 'zoneModule' while setting bean property 'zoneModule'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'zoneModule' defined in Servle
tContext resource [/WEB-INF/context/additionalContext.xml]: Cannot create inner bean 'com.novell.teaming.module.zone.impl.StandaloneZoneModule#1142196' of type [com.novell.teaming.module.zone.impl.Standalone
ZoneModule] while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.novell.teaming.module.zone.impl.StandaloneZon
eModule#1142196' defined in ServletContext resource [/WEB-INF/context/additionalContext.xml]: Invocation of init method failed; nested exception is org.kablink.teaming.search.LuceneException: Could not open
writer on the index [/teaming/teaming2/lucene/lucene/liferay.com_1] / java.io.FileNotFoundException: no segments* file found: files:
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)

The error is related to zoneModule Bean in this error and in quiet all the others...

DO you have any details on what this bean is for and why it appears to be missing ?

Many thanks for your help...

 

F.
Thumbnail Image
Nathan B Jensen Nathan B Jensen
Jul 20, 2009 4:32 PM

I would highly recommend installing the 2.0.0 release.  The issue in your catalina.out suggests that the lucene index can not be written.  This is typically due to file rights or ownership issues.
Thumbnail Image
f pernet f pernet
Aug 25, 2009 2:51 AM

Hi nathan,

It has nothing to do with permissions or ownership. I installed the Teaming2 and it still exactly the same. I tried to chmod 777 everything and run as root also, to test. Same thing.

It has something with the lucene server unable to retreive files or segment or write into the dir for an unknown reason...

thx anyhow

 
Thumbnail Image
Jong Kim Jong Kim
Aug 25, 2009 11:33 AM

The fact that the system is trying to locate the Lucene files in ".../liferay.com_1" directory indicates that there is some configuration problem. It shows that the system is using "liferay.com" as the zone name but somehow does not know that it is the default zone.

Did you install Teaming 2.0 from scratch, or did you upgrade it from earlier Teaming 1.0.* system?

Do you have zone-ext.cfg.xml file in your <teaming tomcat>/webapps/ssf/WEB-INF/classes/config directory? If so, what does the <defaultZone ...> element look like? If you don't have this file, how about zone.cfg.xml in the same directory?

Also, what is the value of zoneName column in the ss_zoneinfo table in your sitescape database?
Thumbnail Image
f pernet f pernet
Aug 26, 2009 1:47 AM

Hi Jong,

I think you are right. When i installed teaming 2 beta 3, Teaming 1 was running on the same machine (but not at the same time). When i tried with teaming 2.0, i see exactly the same behaviour but only when i perform an upgrade. For a New installation, it works and i can see that teaming is storing lucene stuff in a sub-directory called "Kablink". So it appears clearly that the error is only here when updating.

So, during the update, the temaing 1.0.3 is using .../liferay.com for lucene, and the Teaming 2 after upgrade (upgrade itself went without any error in any logs) tries to use .../liferay.com_1 as you said (which is empty). If i try to copy content from .../liferay.com to .../liferay.com_1 the error is "Problem with database integrity"...

For the zone, i checked, for teaming 1.0.3, the file:liferay-portal-tomcat-5.5-jdk5-4.3.0/webapps/ssf/WEB-INF/classes/config/zone.cfg.xml

content is : <defaultZone name="liferay.com"/>

For teaming 2, the name of the Zone in the same file in apache... directory is : kablink.

It appears that, for an update and even with final version 2, this Zone induces the problem with lucene...

I don't think i am doing something wrong ( i never played with the Zone). Is it a bug with the upgrade or i am supposed to do something special with the Zone ?

Thx
Thumbnail Image
Jong Kim Jong Kim
Aug 26, 2009 8:54 AM

When you upgraded your system from 1.0 to 2.0, did you begin the process by copying the installer.xml from the 1.0 system into the directory in which you placed the 2.0 installation software? Just double checking.

After successful upgrade, you should have zone-ext.cfg.xml file in <tomcat>/webapps/ssf/WEB-INF/classes/config directory, with the following content:

 

<?xml version="1.0" encoding="UTF-8" ?>

<zoneConfiguration>

<defaultZone name="liferay.com"/>

</zoneConfiguration>

 

If you don't see this file, I am suspicious that the upgrade went ok. In any event, if you don't have the file, create one manually (make sure that it has the same file permissions as zone.cfg.xml), re-start Teaming and see if it goes further.
Thumbnail Image
Nathan B Jensen Nathan B Jensen
Aug 26, 2009 11:55 AM
Modified by
Nathan B Jensen Nathan B Jensen
Aug 26, 2009 11:56 AM

In addition to Jong's comments:

 

A brand new install will set the default zone name to kablink, while an upgrade will try to maintain liferay.com and if by chance one of the betas didn't catch this for you, you can do the following:
You can move forward with kablink as the zone name by doing the following:
The zone.cfg.xml and zone-ext.cfg.xml should have the new default zone name of kablink like Jong described above.
1.  Update two database tables with the new zone name (use the below commands)
a.  update SS_ZoneInfo set zoneName='kablink' where zoneName='liferay.com';
b.  update SS_Forums set name='kablink' where name='liferay.com';
2.  Rename all liferay.com directories where your data directories are located, there are several.
Or you can edit stay with the old zone name gby doing the followin:
1. Edit the zone-ext.cfg.xml which overrides the default zone.cfg.xml and change the name back to liferay.com
2. Edit the installer.xml and change the zoneName back to liferay.com,  this will prevent problems if you do a reconfigure in the future.
<Install type="1" version="0.0" product="OpenSource" zoneName="liferay.com" />
Thumbnail Image
f pernet f pernet
Aug 27, 2009 4:40 AM

Thx, Jong and Nathan...

everything worked correctly this time and the upgrade went smooth...

I restored Teaming 1.0.3 (files and db) then I modified the installer.xml in teaming2 (jong, i *think* you were right and i didn't copy the installer.xml from teaming 1.0.3, but start to modify directly the temaing2 installer.xml). I am speaking about the basic installer.xml from teaming 2. I didn't touch the version, installed type or product but only the zoneName. I put liferay.com instead of kablink...

Thx a lot for your efforts and your knowledge...

btw, do you if, in the case of an upgrade, we can change the directory paths for the stuff ? In teaming 1, i let the system put everything in the same dir, but in temaing 2 i would love to put everything (stellent, lucene, archive, etc..) in different directories. Does the system able to upgrade + move at the same time OR i really need to precise exactly the same directories than for temaing 1.0.3 ?

Cheers
Thumbnail Image
Jong Kim Jong Kim
Aug 27, 2009 9:20 AM

The installer does not present the UI for selecting various data locations unless it is for new installation. Currently, there is no data management utility that allows you to move or re-arrange data on disk.

 
Skip Footer Toolbar
Permalink