You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Bruce Perryman <bp...@yahoo.com> on 2007/07/31 23:57:15 UTC

2.0 Build Yields Initialization Error -- Re: Please Verify My Build Environment for Lenya 1.2.5

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)

Initialization ProblemMessage: Failure occured during job recovery.
Description: org.apache.avalon.framework.configuration.ConfigurationException: cannot create a quartz scheduler
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
cause

org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'excalibur:LenyaScheduler': java.sql.SQLException: socket creation error [See nested exception: java.sql.SQLException: socket creation error]]
full exception chain stacktrace

org.apache.avalon.framework.configuration.ConfigurationException: cannot create a quartz scheduler
 at org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:309)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297)
 at org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
 at org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524)
 at org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:583)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.Cocoon.initialize(Cocoon.java:345)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1429)
 at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:499)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
 at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
 at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
 at org.apache.catalina.core.StandardService.start(StandardService.java:448)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
Caused by: org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'excalibur:LenyaScheduler': java.sql.SQLException: socket creation error [See nested exception: java.sql.SQLException: socket creation error]]
 at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493)
 at org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:325)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:269)
 at org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:305)
 ... 36 more

stacktrace

org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'excalibur:LenyaScheduler': java.sql.SQLException: socket creation error [See nested exception: java.sql.SQLException: socket creation error]]
 at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493)
 at org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:325)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:269)
 at org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:305)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297)
 at org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
 at org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524)
 at org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:583)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.Cocoon.initialize(Cocoon.java:345)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1429)
 at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:499)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
 at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
 at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
 at org.apache.catalina.core.StandardService.start(StandardService.java:448)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
* Nested Exception (Underlying Cause) ---------------
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'excalibur:LenyaScheduler': java.sql.SQLException: socket creation error [See nested exception: java.sql.SQLException: socket creation error]
 at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:575)
 at org.quartz.impl.jdbcjobstore.JobStoreTX.cleanVolatileTriggerAndJobs(JobStoreTX.java:109)
 at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:491)
 at org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:325)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:269)
 at org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:305)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297)
 at org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
 at org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524)
 at org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:583)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.Cocoon.initialize(Cocoon.java:345)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1429)
 at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:499)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
 at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
 at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
 at org.apache.catalina.core.StandardService.start(StandardService.java:448)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
* Nested Exception (Underlying Cause) ---------------
java.sql.SQLException: socket creation error
 at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
 at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
 at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
 at org.hsqldb.jdbcDriver.connect(Unknown Source)
 at java.sql.DriverManager.getConnection(DriverManager.java:582)
 at java.sql.DriverManager.getConnection(DriverManager.java:185)
 at org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:182)
 at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.newPoolable(InstrumentedResourceLimitingPool.java:655)
 at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(ValidatedResourceLimitingPool.java:145)
 at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable(ResourceLimitingJdbcConnectionPool.java:91)
 at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.get(InstrumentedResourceLimitingPool.java:371)
 at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:97)
 at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:188)
 at org.apache.cocoon.components.cron.DataSourceComponentConnectionProvider.getConnection(DataSourceComponentConnectionProvider.java:54)
 at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:111)
 at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:553)
 at org.quartz.impl.jdbcjobstore.JobStoreTX.cleanVolatileTriggerAndJobs(JobStoreTX.java:109)
 at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:491)
 at org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:325)
 at org.quartz.impl.DirectSchedulerFactory.createScheduler(DirectSchedulerFactory.java:269)
 at org.apache.cocoon.components.cron.QuartzJobScheduler.initialize(QuartzJobScheduler.java:305)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297)
 at org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
 at org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524)
 at org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:583)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.Cocoon.initialize(Cocoon.java:345)
 at org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
 at org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1429)
 at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:499)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)
 at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
 at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
 at org.apache.catalina.core.StandardService.start(StandardService.java:448)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

request-uri

/lenya/
Apache Cocoon 2.1.11-dev


Bruce Perryman <bp...@yahoo.com> wrote: Date: Sun, 29 Jul 2007 11:04:15 -0700 (PDT)
From: Bruce Perryman <bp...@yahoo.com>
Subject: Re: Please Verify My Build Environment for Lenya 1.2.5
To: user@lenya.apache.org

 Thanks. Will do. 

Should I reply using this same thread or create a new one?


Jörn Nettingsmeier <ne...@apache.org> wrote: Bruce Perryman wrote:
> OK. I'll give 2.0 a try. Thanks! The platform that I'll be using will be 
> both XP and Ubuntu 6.06.
> 
> Thanks again!

you're welcome!

if you compile under XP, please let us know how it worked and which java 
sdk you are using. we recently added a workaround for a jdk oddity under 
windows, and some more data would be appreciated.

thanks for considering lenya, hope you'll enjoy!

jörn



-- 
Jörn Nettingsmeier

Kurt is up in heaven now.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional  commands, e-mail: user-help@lenya.apache.org


        

---------------------------------
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.

       
---------------------------------
Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. 

Re: 2.0 Build Yields Initialization Error -- Re: Please Verify My Build Environment for Lenya 1.2.5

Posted by Bruce Perryman <bp...@yahoo.com>.
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 <ne...@apache.org> 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: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org



       
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.

Re: 2.0 Build Yields Initialization Error -- Re: Please Verify My Build Environment for Lenya 1.2.5

Posted by Jörn Nettingsmeier <ne...@apache.org>.
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.

<blush/>

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: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: 2.0 Build Yields Initialization Error -- Re: Please Verify My Build Environment for Lenya 1.2.5

Posted by Josias Thöny <jo...@wyona.com>.
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.

Josias




---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: 2.0 Build Yields Initialization Error -- Re: Please Verify My Build Environment for Lenya 1.2.5

Posted by Bruce Perryman <bp...@yahoo.com>.
Thanks for responding!

When you mentioned Jetty, it gave me an idea. I don't think the build instructions tell you to change the servlet container from Jetty to Tomcat. It tells you to change the path. So initially when following the instructions Lenya was built for Jetty. I did a clean build, ran configure.bat and Tomcat was properly configured.

I did do a build clean, but it still produced this problem. When you mentioned Jetty, I decided to go into the lenya_home\externals\cocoon_x directory and do a build clean for cocoon, then a build clean for lenya. After doing so and rebuilding, the problem was gone.

Thanks for you help. I'll continue with my beta testing and let you know how it goes!  :-)



Joern Nettingsmeier <ne...@folkwang-hochschule.de> 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?

-- 
jörn nettingsmeier

home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621

Kurt is up in Heaven now.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org



       
---------------------------------
Choose the right car based on your needs.  Check out Yahoo! Autos new Car Finder tool.

Re: 2.0 Build Yields Initialization Error -- Re: Please Verify My Build Environment for Lenya 1.2.5

Posted by Joern Nettingsmeier <ne...@folkwang-hochschule.de>.
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?

-- 
jörn nettingsmeier

home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621

Kurt is up in Heaven now.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org