I don't recall testing this after a reboot. If I knew of this issue, I would
have checked it. I only know that once I built clean in the cocoon directory
the problem went away. When I rebooted in the lenya directory, the problem
remained.
If it happens again, I'll report it and let you know if there is a running
instance and whether or not killing the instance will resolve the problem
Thanks.
Jörn Nettingsmeier <[EMAIL PROTECTED]> wrote: Josias Thöny wrote:
> Joern Nettingsmeier wrote:
>> Bruce Perryman wrote:
>>> I've built lenya 2.0 with j2sdk1.6.0_02, tomcat 5.5.23 on XP.
>>>
>>> The build was successful, but after starting tomcat and accessing
>>> localhost:8080/lenya I receive the following: (Please Advise)
>>
>> i've seen that one a couple of times with jetty as well.
>> is it reproducible?
>> does it go away after a restart?
>> what happens if you do a "build.sh clean" and rebuild?
>
> I have encountered this problem when I had another lenya instance
> running on the same machine, so the HSQL-DB port was not available anymore.
> Shutting down both lenya instances and then starting only one solved the
> problem for me.
> Not sure if it's the same issue here.
indeed. at the hackathon, josias already explained this to me, and it
turned out i was running two instances indeed when i saw that error. i
forgot....
bruce, might this be your problem as well?
--
Jörn Nettingsmeier
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.
