[Yanel-dev] Yanel out-of-the-box fails to run

[Andreas Wuest]

Hi

On 5.1.2007 15:54 Uhr, Michael Wechner wrote:

> Andreas Wuest wrote:
> 
>> Hi
>>
>> On 5.1.2007 15:31 Uhr, Josias Thöny wrote:
>>
>>> On Fri, 2007-01-05 at 15:21 +0100, Andreas Wuest wrote:
>>>
>>>> Hi
>>>>
>>>> On 5.1.2007 9:52 Uhr, Josias Thöny wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Fri, 2007-01-05 at 09:38 +0100, Michael Wechner wrote:
>>>>>
>>>>>> Andreas Wuest wrote:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> On 5.1.2007 0:15 Uhr, Michael Wechner wrote:
>>>>>>>
>>>>>>>> Andreas Wuest wrote:
>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> I've tried to run a freshly checked out Yanel (revision 21440) 
>>>>>>>>> without manually configuring anything (i.e. out-of-the-box):
>>>>>>>>>
>>>>>>>>>  1) ./build.sh test: several tests fail
>>>>>>>>>  2) accessing http://127.0.0.1:8080/yanel/ results in:
>>>>>>>>>
>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>> <yanel 
>>>>>>>>> servlet-context-real-path="/Users/awuest/Documents/devel/bin/apache-tomcat-5.5.20/webapps/yanel/"><request 
>>>>>>>>> servlet-path="/" uri="/ya
>>>>>>>>> nel/"/><session 
>>>>>>>>> id="40D9D9C02FE3FB6A50A6B2C02D75BC64"><no-attributes/></session><exception>No 
>>>>>>>>> such resource type registered: &lt;{http://ww
>>>>>>>>> w.wyona.org/yanel/resource/1.0}show-realms/&gt;, check 
>>>>>>>>> yanel.properties</exception></yanel>
>>>>>>>>>
>>>>>>>>> IIUC, running Yanel out-of-the-box without any manual tweaking 
>>>>>>>>> should work, and is one of our high-priority goals, no?
>>>>>>>>
>>>>>>>>
>>>>>>>> yes, absolutely. It works for me on Mac OS X (10.4) without any 
>>>>>>>> problems.
>>>>>>>> All tests work. Did you configure before build (since it's a 
>>>>>>>> fresh checkout)?
>>>>>>>
>>>>>>> I've retried afresh with revision 21453. Still the same problem.
>>>>>>>
>>>>>>> Java version:
>>>>>>>
>>>>>>> % java -version
>>>>>>> java version "1.5.0_06"
>>>>>>> Java(TM) 2 Runtime Environment, Standard Edition (build 
>>>>>>> 1.5.0_06-112)
>>>>>>> Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
>>>>>>>
>>>>>>> % javac -version
>>>>>>> javac 1.5.0_06
>>>>>>>
>>>>>> well, it might be a Java 1.5 issue, because I have tested so far 
>>>>>> only on Java 1.4 and I remember Simon saying that
>>>>>> our Java 1.5 cruisecontrol doesn't really seem to work properly.
>>>>>
>>>>> I've tested yanel on Windows XP/Java 1.5.0_06 and on Linux/Java
>>>>> 1.4.2_06, and everything seems to work.
>>>>>
>>>>> Do your logfiles show more information about the problem?
>>>>
>>>> Not really. build/logs/log4j.log says
>>>>
>>>> 0    2007-01-05 02:05:12,391 [http-8080-Processor24] ERROR 
>>>> org.wyona.yanel.servlet.YanelServlet.getContent():205  - No such 
>>>> resource type registered: 
>>>> <{http://www.wyona.org/yanel/resource/1.0}show-realms/>, check 
>>>> yanel.properties
>>>> 13531 2007-01-05 02:05:25,922 [http-8080-Processor24] ERROR 
>>>> org.wyona.yanel.servlet.YanelServlet.getContent():205  - No such 
>>>> resource type registered: 
>>>> <{http://www.wyona.org/yanel/resource/1.0}show-realms/>, check 
>>>> yanel.properties
>>>>
>>>>> Maybe you could check if the show-realms resource is registered in the
>>>>> following three files:
>>>>> $YANEL_HOME/conf/yanel.xml
>>>>> $YANEL_HOME/build/webapps/yanel/WEB-INF/classes/yanel.properties
>>>>> $TOMCAT_HOME/webapps/yanel/WEB-INF/classes/yanel.properties
>>>>
>>>> Yep, it is registered.
>>>>
>>>> BTW: I am using the tomcat which gets installed by Yanel. I could do 
>>>> a test run with my own tomcat as well.
>>>
>>>
>>> In your error message it says:
>>> servlet-context-real-path="/Users/awuest/Documents/devel/bin/apache-tomcat-5.5.20/webapps/yanel/"> 
>>>
>>>
>>> is that really the tomcat which was installed by yanel?
>>> Normally it's located in $YANEL_HOME/local/apache-tomcat-5.5.20/
>>>
>>> Or am I misunderstanding something?
>>
>>
>> Oh, your're right! That's indeed interesting. No, this is actually my 
>> own local tomcat. Nevertheless, I've never supplied that path to the 
>> Yanel configure process, but told it to install its own.
>>
>> Hmm, indeed, my $CATALINA_HOME of course points to my own tomcat.
>>
>> So, just a short recap:
>>
>>  1) User has already installed a tomcat, and has $CATALINA_HOME 
>> pointing to it
>>  2) Nevertheless, the user tell configure to install the tomcat 
>> delivered with Yanel
>>
>>
>> I am not sure how we could handle such a situation. Should configure 
>> check for an existing env variable to see if the user has already 
>> installed a tomcat? Or, should it use its own tomcat if the user told 
>> it to install its own one, despite already having another tomcat on 
>> the machine.
>>
> 
> maybe we have to unset CATALINA_HOME?

Yes, the problem seems to be that a $CATALINA_HOME pointing to a 
different tomcat than the one you pointed to during configure, or the 
one which got installed by Yanel, then it breaks.

I would propose to either

  1) tell the user to unset it before doing yanel.sh start in the docs,
  2) or to make yanel.sh check if the env variable points to a different 
location than what is configured and then warn the user,
  3) or to silently unset the variable in yanel.sh.

-- 
Kind regards,
Andi