Fórum
Using liferay from trunk
Kolja Köster, modificado 14 Anos atrás.
Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
After the fantasic preview on version 5.3 on the symposium, I was very courious and wanted to get my hands on that version. So I checkt out the trunk from the public svn. I installed an new tomcat, becaus I do not want 5.3 to interfere with my existing liferay installation. I created personal verison of build.properties and release.properties. Some manual stated to change app.server.properties but I did not do so in my existing liferay installation, so my app.server.$username.properties is just empty. I changed CATALINA_HOME system variable to point on my new tomcat dir. I did ant build in my liferay trunk dir and i did ant deploy. Now what? Tomcat is running, several files from my trunk dir have been copied to the tomcat root, but I can not access the portal. What did I miss? Is there a documentation on this? Any help would be realle apreciated.
[Edit: Seems like a bunce of files are deployed to a wron directory. Might someone point me to a COMPLETE liste of property files, that have to be edited?]
[Another Edit: After changing some directory name values, tomcat now fails wiht an IllegalArgumentException: webapps/host-manager does not exist....a single readme on this would be so awsome....]
[And another one: I found a host-manager in work/catalina/localhost. Why does tomcat seach for it in webapps? What does the host-manager do? How to configure this? Anyone, please help. This is so frustrating. Half a page of text could easily solve this. I can not beleave to be the only one, who tries to checkout from trunk. Or do all of you know how to do this by heart?]
Regards
Kolja
[Edit: Seems like a bunce of files are deployed to a wron directory. Might someone point me to a COMPLETE liste of property files, that have to be edited?]
[Another Edit: After changing some directory name values, tomcat now fails wiht an IllegalArgumentException: webapps/host-manager does not exist....a single readme on this would be so awsome....]
[And another one: I found a host-manager in work/catalina/localhost. Why does tomcat seach for it in webapps? What does the host-manager do? How to configure this? Anyone, please help. This is so frustrating. Half a page of text could easily solve this. I can not beleave to be the only one, who tries to checkout from trunk. Or do all of you know how to do this by heart?]
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Ok, I am sorry to say, that I am giving up on this. I changed all propertie files. I had my tomcat dir in several different places. Propertie files define variables based on other variablenames, which are not given in that file. It ist impossible for me to set up Liferay without the bundled tomcat. Noone has written a single line on this. ant deploy is not helping AT ALL, because I have no clue, how to edit the propertie files. I am stuck on this, very hard.
This really needs a documentation, or if it exists, it needs a link!! I am unable to solve this for about 5 hours now! Can anybody PLEASE STATE ANY DIRECTION how to USE LIFERAY FROM TRUNK?
Regards
Kolja
This really needs a documentation, or if it exists, it needs a link!! I am unable to solve this for about 5 hours now! Can anybody PLEASE STATE ANY DIRECTION how to USE LIFERAY FROM TRUNK?
Regards
Kolja
Mika Koivisto, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Legend Postagens: 1519 Data de Entrada: 07/08/06 Postagens Recentes
There are a bunch of articles about setting up your development environment in the Wiki.
Here's a not so detailed easy way of getting started with trunk:
Here's a not so detailed easy way of getting started with trunk:
- Download latest Liferay bundle (tomcat 6 recommended)
- Checkout source code from svn
- Copy app.server.properties to app.server.YOURUSERNAME.properties
- Set app.server.type to your app server (i.e. tomcat)
- Adjust your tomcat bundle location in app.server.YOURUSERNAME.properties
- run> ant clean start deploy for the trunk source.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesMika Koivisto:
Download latest Liferay bundle (tomcat 6 recommended)
Done...
Mika Koivisto:
Checkout source code from svn
Done...
Source resides in c:\liferaytrunk, tomcat in c:\liferaytrunk\tomcat
Mika Koivisto:
Copy app.server.properties to app.server.YOURUSERNAME.properties Set app.server.type to your app server (i.e. tomcat) Adjust your tomcat bundle location in app.server.YOURUSERNAME.properties
Well, that ist not as easy as you describe it here. This seem to be the relevant lines:
app.server.tomcat.version=6.0
app.server.tomcat.dir=${app.server.parent.dir}/tomcat-6.0.16
app.server.tomcat.classes.global.dir=${app.server.tomcat.dir}/lib
app.server.tomcat.lib.endorsed.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.lib.global.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.lib.support.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.support.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.zip.name=liferay-portal-tomcat-6.0-${downloads.version}.zip
Where does app.server.parent.dir have to point to? Where is this defined? Same for downloads.version. In the app.server.properties from the svn there are even more such variables like e.g. app.server.tomcat.portal.dir, which are used in a variable definition, but are itself never defined in the context of app.server.properties.
Another question: Am I done after deploying this with ant deploy? The liferay-admin-guide states to remove some sample content from the tomcat/ROOT dir, and tells me to change some xml files. Is this all handled by ant?
Regards
Kolja
Mika Koivisto, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Legend Postagens: 1519 Data de Entrada: 07/08/06 Postagens Recentes
Okey I see what your issue is. I would recommend using following kind of directory structure:
Now you point app.server.parent.dir to C:/SomeBaseDir/bundles. You portal trunk sources reside in C:/SomeBaseDir/portal and if you use ext or plugins sdk they reside next to the portal directory. Once the ant clean start deploy has run you are done and can then startup your tomcat.
C:/SomeBaseDir
/bundles
/tomcat-6.0.18
/portal
/ext
/pluginsNow you point app.server.parent.dir to C:/SomeBaseDir/bundles. You portal trunk sources reside in C:/SomeBaseDir/portal and if you use ext or plugins sdk they reside next to the portal directory. Once the ant clean start deploy has run you are done and can then startup your tomcat.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesMika Koivisto:
Okey I see what your issue is. I would recommend using following kind of directory structure:
Still not working. Now I have a directory called liferaytrunk. Within it, I have a tomcat dir, called tomcat and my checked out sources dir called portal. These are the changes I made to my property files:
c:\liferaytrunk\portal\build.username.properties:
app.server.dir=C:/liferaytrunk/tomcat
app.server.portal.dir=${app.server.dir}/webapps/ROOT
app.server.classes.portal.dir=${app.server.portal.dir}/WEB-INF/classes
app.server.lib.global.dir=${app.server.dir}/common/lib/ext
app.server.lip.portal.dir=${app.server.portal.dir}/WEB-INF/libc:\liferaytrunk\portal\app.server.username.properties:
app.server.type=tomcat
app.server.parent.dir=c:/liferaytrunk
app.server.tomcat.version=6.0
app.server.tomcat.dir=${app.server.parent.dir}/tomcat
app.server.tomcat.bin.dir=${app.server.tomcat.dir}/bin
app.server.tomcat.classes.global.dir=${app.server.tomcat.dir}/lib
app.server.tomcat.classes.portal.dir=${app.server.tomcat.portal.dir}/WEB-INF/classes
app.server.tomcat.deploy.dir=${app.server.tomcat.dir}/webapps
app.server.tomcat.lib.endorsed.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.lib.global.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.lib.portal.dir=${app.server.tomcat.portal.dir}/WEB-INF/lib
app.server.tomcat.lib.support.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.portal.context=ROOT
app.server.tomcat.portal.dir=${app.server.tomcat.deploy.dir}/${app.server.tomcat.portal.context}
app.server.tomcat.log.dir=${app.server.tomcat.dir}/logs
app.server.tomcat.temp.dir=${app.server.tomcat.dir}/temp
app.server.tomcat.work.dir=${app.server.tomcat.dir}/work
app.server.tomcat.zip.name=liferay-portal-tomcat-6.0-${downloads.version}.zip
app.server.tomcat.zip.url=${sourceforge.mirror}/${app.server.tomcat.zip.name}
downloads.dir=${project.dir}/downloads
downloads.version=@lp.version@
sourceforge.mirror=http://heanet.dl.sourceforge.net/sourceforge/lportalant deploys about 5000 files to tomcat, which still does not start and fails to run the portal with an IllegalArgumentException.
[Edit: corrected typos]
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Tried the same procedure again, this time also creating an ext environment. Same error. Tomcat starts, console tells me about IllegalArgumentException. All that comes up is the demo page. THIS IS DONE EXACTLY AS DESCIBED IN THE GUIDE, THAT WAS LINKED HERE! At least to my humble skills. I have posted my configuration, please state if there still is a simple typo or somthing that I did not get.
I see that this is complex. I see that this requires some skill. I do not see people telling me 'oh come on, that' sooooo easy.' It is not! Wasted a whole workday on this. Depressing, I am sorry to say.
Regards
Kolja
I see that this is complex. I see that this requires some skill. I do not see people telling me 'oh come on, that' sooooo easy.' It is not! Wasted a whole workday on this. Depressing, I am sorry to say.
Regards
Kolja
Mika Koivisto, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Legend Postagens: 1519 Data de Entrada: 07/08/06 Postagens Recentes
It is possible that trunk is unstable at times since it is under development and no QA has been do to it yet. Can you post what get's printed to the tomcat console? I didn't notice any errors in your properties.
Using trunk is really only recommended for experienced developers that want an early access to the upcoming version and possibly contribute features and or bug fixes.
I know that it can be quite depressing when you do everything right but it still does not work. When I develop against trunk I sometimes have to rollback to an earlier version that has been stable for me to be able to continue developing the feature I was doing.
Using trunk is really only recommended for experienced developers that want an early access to the upcoming version and possibly contribute features and or bug fixes.
I know that it can be quite depressing when you do everything right but it still does not work. When I develop against trunk I sometimes have to rollback to an earlier version that has been stable for me to be able to continue developing the feature I was doing.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesMika Koivisto:
It is possible that trunk is unstable at times since it is under development and no QA has been do to it yet. Can you post what get's printed to the tomcat console? I didn't notice any errors in your properties.
This is, whats in catalina.log:
01.10.2009 16:31:22 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Programme\Java\jdk1.6.0_14\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\liferaytrunk\tomcat\bin;C:\Programme\Java\jdk1.6.0_14\bin;C:\Programme\apache-ant\bin;C:\Programme\jikes\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Intel\WiFi\bin\;C:\Programme\WinSCP\;C:\Programme\MySQL\MySQL Server 5.1\bin;C:\Programme\Subversion\bin;C:\Programme\BDV\Uniarchiv\Bin\Lead14
01.10.2009 16:31:22 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
01.10.2009 16:31:22 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 442 ms
01.10.2009 16:31:22 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
01.10.2009 16:31:22 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext resourcesStart
SCHWERWIEGEND: Error starting static Resources
java.lang.IllegalArgumentException: Document base C:\liferaytrunk\tomcat\webapps\host-manager does not exist or is not a readable directory
at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:142)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4048)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4217)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error in resourceStart()
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error getConfigured
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/host-manager] startup failed due to previous errors
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager] has not been started
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext resourcesStart
SCHWERWIEGEND: Error starting static Resources
java.lang.IllegalArgumentException: Document base C:\liferaytrunk\tomcat\webapps\manager does not exist or is not a readable directory
at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:142)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4048)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4217)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error in resourceStart()
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error getConfigured
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/manager] startup failed due to previous errors
01.10.2009 16:31:22 org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager] has not been started
01.10.2009 16:33:03 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
01.10.2009 16:33:03 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [] startup failed due to previous errors
01.10.2009 16:33:04 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
01.10.2009 16:33:04 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
01.10.2009 16:33:04 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=null
01.10.2009 16:33:04 org.apache.catalina.startup.Catalina start
INFO: Server startup in 102307 ms
01.10.2009 16:33:52 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
01.10.2009 16:33:53 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
01.10.2009 16:33:53 org.apache.catalina.startup.HostConfig undeployApps
WARNUNG: Error while removing context [/tunnel-web]
java.lang.NullPointerException
at com.liferay.portal.kernel.servlet.PortalClassLoaderFilter.destroy(PortalClassLoaderFilter.java:57)
at org.apache.catalina.core.ApplicationFilterConfig.release(ApplicationFilterConfig.java:332)
at org.apache.catalina.core.StandardContext.filterStop(StandardContext.java:3835)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4567)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:924)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1248)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1219)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:316)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1086)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
at org.apache.catalina.core.StandardService.stop(StandardService.java:584)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:633)
at org.apache.catalina.startup.Catalina.start(Catalina.java:608)
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:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
01.10.2009 16:33:53 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
01.10.2009 16:39:10 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Programme\Java\jdk1.6.0_14\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\liferaytrunk\tomcat\bin;C:\Programme\Java\jdk1.6.0_14\bin;C:\Programme\apache-ant\bin;C:\Programme\jikes\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Intel\WiFi\bin\;C:\Programme\WinSCP\;C:\Programme\MySQL\MySQL Server 5.1\bin;C:\Programme\Subversion\bin;C:\Programme\BDV\Uniarchiv\Bin\Lead14
01.10.2009 16:39:10 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
01.10.2009 16:39:10 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 468 ms
01.10.2009 16:39:10 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
01.10.2009 16:39:10 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext resourcesStart
SCHWERWIEGEND: Error starting static Resources
java.lang.IllegalArgumentException: Document base C:\liferaytrunk\tomcat\webapps\host-manager does not exist or is not a readable directory
at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:142)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4048)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4217)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error in resourceStart()
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error getConfigured
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/host-manager] startup failed due to previous errors
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager] has not been started
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext resourcesStart
SCHWERWIEGEND: Error starting static Resources
java.lang.IllegalArgumentException: Document base C:\liferaytrunk\tomcat\webapps\manager does not exist or is not a readable directory
at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:142)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4048)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4217)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
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:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error in resourceStart()
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error getConfigured
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/manager] startup failed due to previous errors
01.10.2009 16:39:10 org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager] has not been started
01.10.2009 16:39:31 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
01.10.2009 16:39:31 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [] startup failed due to previous errors
01.10.2009 16:39:33 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
01.10.2009 16:39:33 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
01.10.2009 16:39:33 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/15 config=null
01.10.2009 16:39:33 org.apache.catalina.startup.Catalina start
INFO: Server startup in 22318 ms
01.10.2009 16:41:34 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
01.10.2009 16:41:35 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
01.10.2009 16:41:35 org.apache.catalina.startup.HostConfig undeployApps
WARNUNG: Error while removing context [/tunnel-web]
java.lang.NullPointerException
at com.liferay.portal.kernel.servlet.PortalClassLoaderFilter.destroy(PortalClassLoaderFilter.java:57)
at org.apache.catalina.core.ApplicationFilterConfig.release(ApplicationFilterConfig.java:332)
at org.apache.catalina.core.StandardContext.filterStop(StandardContext.java:3835)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4567)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:924)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1248)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1219)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:316)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1086)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
at org.apache.catalina.core.StandardService.stop(StandardService.java:584)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:633)
at org.apache.catalina.startup.Catalina.start(Catalina.java:608)
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:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
01.10.2009 16:41:36 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Mika Koivisto:
I know that it can be quite depressing when you do everything right but it still does not work. When I develop against trunk I sometimes have to rollback to an earlier version that has been stable for me to be able to continue developing the feature I was doing.
Is there a chance to tell, if this is due to a broken trunk version or to a misconfiguration on my side?
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
I gave it another try this morning. It is still not working, but the errors in the catalina.log have changed. This is what I did:
-created dir 'c:\liferaytrunk'
-created dir 'c:\liferaytrunk\portal'
-created dir 'c:\liferaytrunk\tomcat'
-cecked out 'svn.liferay.com/repos/public/portal/tunk' to 'portal'
-unpacked apache-tomcat 6.0.2 to 'tomcat'
-since my username ist 'kkoester' I created 'release.kkoester.properties' in portal,
this is what goes in the file:
-cd to 'portal', did 'ant clean start build-ext'
-cd to 'ext' (I am not sure, if this is right)
-checked that app.server.properties in 'ext' contains these lines (since it did, I did not edit this file):
-created 'app.server.kkoester.properties' in 'ext', this is what go into that file:
-in 'ext' I did 'ant clean deploy'
-cd to 'tomcat/bin'
-startup.bat
-tomcat start only with demopage, this is whats in catalina.log
If this is due to a broken trunk version, it's fine, I will try again later. But I to not know if this is the case. I anyone could enlighten me in this, I would be very thankfull.
Regards
Kolja
-created dir 'c:\liferaytrunk'
-created dir 'c:\liferaytrunk\portal'
-created dir 'c:\liferaytrunk\tomcat'
-cecked out 'svn.liferay.com/repos/public/portal/tunk' to 'portal'
-unpacked apache-tomcat 6.0.2 to 'tomcat'
-since my username ist 'kkoester' I created 'release.kkoester.properties' in portal,
this is what goes in the file:
lp.ext.dir=C:/liferaytrunk/ext-cd to 'portal', did 'ant clean start build-ext'
-cd to 'ext' (I am not sure, if this is right)
-checked that app.server.properties in 'ext' contains these lines (since it did, I did not edit this file):
app.server.tomcat.version=6.0
app.server.tomcat.dir=${app.server.parent.dir}/tomcat-6.0.16
app.server.tomcat.classes.global.dir=${app.server.tomcat.dir}/lib
app.server.tomcat.lib.endorsed.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.lib.global.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.lib.support.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.support.dir=${app.server.tomcat.dir}/lib/ext
app.server.tomcat.zip.name=liferay-portal-tomcat-6.0-${downloads.version}.zip
-created 'app.server.kkoester.properties' in 'ext', this is what go into that file:
app.server.type=tomcat
app.server.tomcat.dir=C:/liferaytrunk/tomcat-in 'ext' I did 'ant clean deploy'
-cd to 'tomcat/bin'
-startup.bat
-tomcat start only with demopage, this is whats in catalina.log
02.10.2009 09:05:57 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Programme\Java\jdk1.6.0_14\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\liferaytrunk\tomcat\bin;C:\Programme\Java\jdk1.6.0_14\bin;C:\Programme\apache-ant\bin;C:\Programme\jikes\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Intel\WiFi\bin\;C:\Programme\WinSCP\;C:\Programme\MySQL\MySQL Server 5.1\bin;C:\Programme\Subversion\bin;C:\Programme\BDV\Uniarchiv\Bin\Lead14
02.10.2009 09:05:57 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
02.10.2009 09:05:57 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 545 ms
02.10.2009 09:05:57 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
02.10.2009 09:05:57 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
02.10.2009 09:05:58 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
02.10.2009 09:05:58 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [] startup failed due to previous errors
02.10.2009 09:05:58 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error filterStart
02.10.2009 09:05:58 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/tunnel-web] startup failed due to previous errors
02.10.2009 09:05:58 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
02.10.2009 09:05:59 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
02.10.2009 09:05:59 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/15 config=null
02.10.2009 09:05:59 org.apache.catalina.startup.Catalina start
INFO: Server startup in 1668 ms
If this is due to a broken trunk version, it's fine, I will try again later. But I to not know if this is the case. I anyone could enlighten me in this, I would be very thankfull.
Regards
Kolja
Oliver Bayer, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 894 Data de Entrada: 18/02/09 Postagens Recentes
Hi Kolja,
I'm not sure but maybe you're missing some of the dependencies (downloadable via Liferay download page). Your steps to create liferay trunk seems to be right. The easiest way to build liferay from trunk is you download the liferay 5.2.3 bundle (contains all dependencies already) extract it to your tomcat folder and re-run "ant clean deploy" from ext.
HTH
I'm not sure but maybe you're missing some of the dependencies (downloadable via Liferay download page). Your steps to create liferay trunk seems to be right. The easiest way to build liferay from trunk is you download the liferay 5.2.3 bundle (contains all dependencies already) extract it to your tomcat folder and re-run "ant clean deploy" from ext.
HTH
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Thanks for replying.
What are those? Could you explain or link me to somewhere, I can read about those?
Regards
Kolja
Oliver Bayer:
I'm not sure but maybe you're missing some of the dependencies (downloadable via Liferay download page).
What are those? Could you explain or link me to somewhere, I can read about those?
Regards
Kolja
Mika Koivisto, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Legend Postagens: 1519 Data de Entrada: 07/08/06 Postagens Recentes
I see you took a plain tomcat 6 and not one of our tomcat 6 bundles. There are additional steps you need to do to install Liferay on a plain tomcat. You can find those from the Liferay administrators guide. Basically you modify conf/catalina.properties and add lib/ext/*.jar to common.loader property. It is much easier for you to take the 5.2.3 SE tomcat 6 bundle.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesMika Koivisto:
I see you took a plain tomcat 6 and not one of our tomcat 6 bundles. There are additional steps you need to do to install Liferay on a plain tomcat. You can find those from the Liferay administrators guide. Basically you modify conf/catalina.properties and add lib/ext/*.jar to common.loader property. It is much easier for you to take the 5.2.3 SE tomcat 6 bundle.
This explains, why the admin guide states things, the development guide does not. I will remove my tomcat folder and put the tomcat liveray bundle in there and then deploy my ext into it. Thank you for pointing this out. I will post the outcome, but this sounds very helpfull.
Regards
Kolja
Brian Kim, modificado 14 Anos atrás.
RE: Using liferay from trunk
Expert Postagens: 311 Data de Entrada: 17/08/04 Postagens RecentesKolja Köster:
Tried the same procedure again, this time also creating an ext environment. Same error. Tomcat starts, console tells me about IllegalArgumentException. All that comes up is the demo page. THIS IS DONE EXACTLY AS DESCIBED IN THE GUIDE, THAT WAS LINKED HERE! At least to my humble skills. I have posted my configuration, please state if there still is a simple typo or somthing that I did not get.
I see that this is complex. I see that this requires some skill. I do not see people telling me 'oh come on, that' sooooo easy.' It is not! Wasted a whole workday on this. Depressing, I am sorry to say.
Regards
Kolja
Kolja,
Thanks for coming out to our Symposium - we're glad that you could make it. However, as Mika stated, we don't guarantee that our trunk is stable nor that our guides are up-to-date for it. Our developers are constantly checking in code and new features to improve our product, and then our documentation comes later when we provide a stable EE release.
Regarding your issue, is there a reason your building an Ext environment? If you're just interested in checking out the 5.3 features, you can just deploy our core source directly to tomcat without the Ext.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesBrian Kim:
Our developers are constantly checking in code and new features to improve our product, and then our documentation comes later when we provide a stable EE release.
I completly understand this. But it would still be great if someone could point out if this ist due to somthing in trunk or due to a misconfiguration on my side. Since several people seem to use the trunk version, my guess was, that some of them might give a hint on this.
Regards
Kolja
Alexander Chow, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 518 Data de Entrada: 20/07/05 Postagens Recentes
Hi Kolja,
So, out of curiosity, are you able to get trunk to run without ext? That runs perfectly fine on my end.
So, out of curiosity, are you able to get trunk to run without ext? That runs perfectly fine on my end.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Still not running. Lifray tomcat6 bundle is still downloading. I am not quite sure, if it is even the right file. I tried to install liferay dependencies according to the admin guide. Basically I created 'common/lib/ext' in my tomcat folder put the dependency files in there and added the dir to 'conf/catalina.properties'. Catalina spits out diffenrent errors and the example page is gone. It is very confusing, that there are so many different guides, which are contrary to each other or not pointing out, that they are written for different scenarios. Beats me right now. Will give the bundle tomcat a try, once it is downloaded.
Regards
Kolja
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Ok, I am not sure, if I got that right. I still have my liferaytrunk dir, with the trunk sources in a subfolder 'portal' and the via ant created 'ext' folder. I remove the tomcat folder. Than I took the tomcat6 folder from the liferay-tomcat bundel and unziped its content into an fresh and empty folder C:\liferaytrunk\tomcat.
I did 'ant clean deploy' in ext, now tomcat dies with an error message about 'Contex initiation failed'. Since it is not written in the log and the stupid Windows Tomcat Shell does not allow copy&paste, I am unable to post all of those errormessages here.
Thought I could give my company a preview on the new features, but I can not spend more time on this. Not seeing how to approach this, I am sorry. This really beats me, and there are not many thing regarding computers that do.
How are the people who use the trunk version do this? Is there any best practice? Or a CONSISTENT document how to install this from scratch, from the trunk sources, into a standrad tomcat?
I have added a screenshot of the tomcat shell. It is not showing all errors but starting at the first one.
Regards
Kolja
I did 'ant clean deploy' in ext, now tomcat dies with an error message about 'Contex initiation failed'. Since it is not written in the log and the stupid Windows Tomcat Shell does not allow copy&paste, I am unable to post all of those errormessages here.
Thought I could give my company a preview on the new features, but I can not spend more time on this. Not seeing how to approach this, I am sorry. This really beats me, and there are not many thing regarding computers that do.
How are the people who use the trunk version do this? Is there any best practice? Or a CONSISTENT document how to install this from scratch, from the trunk sources, into a standrad tomcat?
I have added a screenshot of the tomcat shell. It is not showing all errors but starting at the first one.
Regards
Kolja
Anexos:
Brian Kim, modificado 14 Anos atrás.
RE: Using liferay from trunk
Expert Postagens: 311 Data de Entrada: 17/08/04 Postagens RecentesKolja Köster:
Since it is not written in the log and the stupid Windows Tomcat Shell does not allow copy&paste, I am unable to post all of those errormessages here.
As an FYI, you _can_ copy and paste from the tomcat shell. Hit Alt-Space. Then choose Edit->Select All (or Mark).
Oliver Bayer, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 894 Data de Entrada: 18/02/09 Postagens Recentes
Hi Kolja,
take a look at my thread Missing bean in trunk. Now you're getting the same error as me. I was told that it should be fixed in the new trunk revision (I've hadn't the time to check), so do a svn update. If this doesn't work you can put the missing baseVelocityService in ext-spring.xml as described in my thread as a workaround so that liferay portal is starting.
And yes you can copy from windows shell ;-): right click in the window title from the tomcat shell -> manage -> mark.
Greets
take a look at my thread Missing bean in trunk. Now you're getting the same error as me. I was told that it should be fixed in the new trunk revision (I've hadn't the time to check), so do a svn update. If this doesn't work you can put the missing baseVelocityService in ext-spring.xml as described in my thread as a workaround so that liferay portal is starting.
And yes you can copy from windows shell ;-): right click in the window title from the tomcat shell -> manage -> mark.
Greets
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Thanks to both of you to point out, how to solve my copy issue. I am stuck to a Windows machine at work due to different tings like e.g. Lotus notes.....
Anyway, I had a look at your thead Oliver, but I obviousliy failed to see, that I have the same error message as you, I am sorry. So from the perspectiv of setting liferay up i am done right? So, when the next trunk build is aviable, I update my portal dir via svn, rebuild svn and redeploy it to tomcat right?
Regard
Kolja
Anyway, I had a look at your thead Oliver, but I obviousliy failed to see, that I have the same error message as you, I am sorry. So from the perspectiv of setting liferay up i am done right? So, when the next trunk build is aviable, I update my portal dir via svn, rebuild svn and redeploy it to tomcat right?
Regard
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Hmmmm, I checkt out revision 38472, as stated in the other thread. I did 'ant clean start build-ext' in the source dir and then 'ant clean deploy' in the ext folder. Still no luck:
Regards
Kolja
02.10.2009 13:47:20 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performanc
e in production environments was not found on the java.library.path: C:\liferayt
runk\tomcat\jre1.5.0_17\win\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\liferaytrunk
\tomcat\bin;C:\Programme\Java\jdk1.6.0_14\bin;C:\Programme\apache-ant\bin;C:\Pro
gramme\jikes\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Prog
ramme\Intel\WiFi\bin\;C:\Programme\WinSCP\;C:\Programme\MySQL\MySQL Server 5.1\b
in;C:\Programme\Subversion\bin;C:\Programme\BDV\Uniarchiv\Bin\Lead14
02.10.2009 13:47:20 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
02.10.2009 13:47:20 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 560 ms
02.10.2009 13:47:20 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
02.10.2009 13:47:20 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Loading jar:file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/lib/portal-impl.ja
r!/system.properties
Loading file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/classes/system-ext.pro
perties
Loading jar:file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/lib/portal-impl.ja
r!/portal.properties
Loading file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.pro
perties
13:47:28,640 INFO [DialectDetector:75] Determining dialect for HSQL Database En
gine 1
13:47:28,656 WARN [DialectDetector:90] Liferay is configured to use Hypersonic
as its database. Do NOT use Hypersonic in production. Hypersonic is an embedded
database useful for development and demo'ing purposes. The database settings can
be changed in portal.properties.
13:47:28,703 INFO [DialectDetector:55] Using dialect org.hibernate.dialect.HSQL
Dialect
Loading jar:file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/lib/portal-impl.ja
r!/captcha.properties
13:47:31,937 INFO [PortalImpl:263] Portal lib directory /C:/liferaytrunk/tomcat
/webapps/ROOT/WEB-INF/lib/
13:47:47,750 ERROR [ContextLoader:215] Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean def
inition with name 'com.ext.portlet.reports.service.ReportsEntryService.velocity'
defined in class path resource [META-INF/ext-spring.xml]: Could not resolve par
ent bean definition 'baseVelocityService'; nested exception is org.springframewo
rk.beans.factory.NoSuchBeanDefinitionException: No bean named 'baseVelocityServi
ce' is defined
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:1035)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:985)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edLocalBeanDefinition(AbstractBeanFactory.java:971)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
preInstantiateSingletons(DefaultListableBeanFactory.java:420)
at org.springframework.context.support.AbstractApplicationContext.finish
BeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refres
h(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationCon
text(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationConte
xt(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitiali
zed(ContextLoaderListener.java:45)
at com.liferay.portal.spring.context.PortalContextLoaderListener.context
Initialized(PortalContextLoaderListener.java:48)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
t.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:77
1)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.ja
va:627)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.j
ava:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488
)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443
)
at org.apache.catalina.core.StandardService.start(StandardService.java:5
16)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710
)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No b
ean named 'baseVelocityService' is defined
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
getBeanDefinition(DefaultListableBeanFactory.java:387)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edLocalBeanDefinition(AbstractBeanFactory.java:971)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:741)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:1021)
... 33 more
02.10.2009 13:47:47 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
02.10.2009 13:47:47 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [] startup failed due to previous errors
02.10.2009 13:47:47 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
02.10.2009 13:47:47 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
02.10.2009 13:47:47 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=null
02.10.2009 13:47:47 org.apache.catalina.startup.Catalina start
INFO: Server startup in 27366 ms
Regards
Kolja
Oliver Bayer, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 894 Data de Entrada: 18/02/09 Postagens Recentes
look at the error-code snippet:
There you see No bean named 'baseVelocityService' is defined. It's the same message I get.
So go to "ext-dir \ ext-impl src \ ext-spring.xml" and add the following at the top of the xml after the opening <beans>-tag:
Now (after ant clean deploy from ext-dir) your tomcat should start up without any errors.
HTH Oli
13:47:47,750 ERROR [ContextLoader:215] Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean def
inition with name 'com.ext.portlet.reports.service.ReportsEntryService.velocity'
defined in class path resource [META-INF/ext-spring.xml]: Could not resolve par
ent bean definition 'baseVelocityService'; nested exception is org.springframewo
rk.beans.factory.NoSuchBeanDefinitionException: No bean named 'baseVelocityServi
e' is definedThere you see No bean named 'baseVelocityService' is defined. It's the same message I get.
So go to "ext-dir \ ext-impl src \ ext-spring.xml" and add the following at the top of the xml after the opening <beans>-tag:
<bean id="baseVelocityService" abstract="true">
<property name="interceptorNames">
<list>
<value>velocityServiceInterceptor</value>
</list>
</property>
</bean>Now (after ant clean deploy from ext-dir) your tomcat should start up without any errors.
HTH Oli
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
I thought the current snv build would fix that....anyway, the build from 16:45 central euopean time does not compile on my machine. I will wait what svn version will be aviable on monday.
Regards
Kolja
Regards
Kolja
Alexander Chow, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 518 Data de Entrada: 20/07/05 Postagens Recentes
Update your SVN again. You need at least rev 38484.
Alexander Chow, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 518 Data de Entrada: 20/07/05 Postagens RecentesAlexander Chow:
Update your SVN again. You need at least rev 38484.
Scratch that last one. Somebody just broke the build in trunk (as I said earlier, trunk is developmental!
) . Sorry about that. It is being fixed as we speak... if you try again Monday, it should be fixed.
Alexander Chow, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 518 Data de Entrada: 20/07/05 Postagens Recentes
Okay, I just tested against 38493 and the ext builds and tomcat starts up. Please try again. Sorry about all the confusion.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesAlexander Chow:
Alexander Chow:Update your SVN again. You need at least rev 38484.
Scratch that last one. Somebody just broke the build in trunk (as I said earlier, trunk is developmental!
As I said: No problem, I fully understand that the trunk version is not stable. I have no setup at home, so I can check this on monday. But the important point is, that my setup at work looks correct now. Thanks to everybody, for your help.
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
I am still getting the same ContextLoaderError... Checked out trunk about 20 minutes ago. I there somthing else to be done? Strange thing, this error persists, regadless of updating from svn.... Can this be some configurations issue on my side?
Regards
Kolja
Regards
Kolja
Alexander Chow, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 518 Data de Entrada: 20/07/05 Postagens Recentes
Like Oliver mentioned in his related post, do you have this change: http://svn.liferay.com/browse/portal/trunk/tools/ext_tmpl/ext-impl/src/META-INF/ext-spring.xml?r1=30797&r2=38484&?
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Now you have lost me. I have updated to a trunk revision, that should have fixed this issue. When I have a look at portal/tools/ext_tmpl/src/META-INF/ext-spring.xml it looks like this:
This looks like the diff in mentiond in the workaround has already been applied. What am I supposed to do?
Regards
Kolja
<!--?xml version="1.0" encoding="UTF-8"?-->
<beans>
<bean id="com.ext.portlet.reports.service.ReportsEntryService.impl" class="com.ext.portlet.reports.service.impl.ReportsEntryServiceImpl" />
<bean id="com.ext.portlet.reports.service.ReportsEntryService.velocity" class="com.ext.portlet.reports.service.impl.ReportsEntryServiceImpl" />
<bean id="com.ext.portlet.reports.service.ReportsEntryServiceUtil" class="com.ext.portlet.reports.service.ReportsEntryServiceUtil">
<property name="service" ref="com.ext.portlet.reports.service.ReportsEntryService.impl" />
</bean>
<bean id="com.ext.portlet.reports.service.persistence.ReportsEntryPersistence.impl" class="com.ext.portlet.reports.service.persistence.ReportsEntryPersistenceImpl" parent="basePersistence" />
<bean id="com.ext.portlet.reports.service.persistence.ReportsEntryUtil" class="com.ext.portlet.reports.service.persistence.ReportsEntryUtil">
<property name="persistence" ref="com.ext.portlet.reports.service.persistence.ReportsEntryPersistence.impl" />
</bean>
</beans>This looks like the diff in mentiond in the workaround has already been applied. What am I supposed to do?
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
Ok, I have tried several trunk revision, 3 of those have been reportet working in this forum. Errormessage is not changing, so my guess is, I am missing somthing. I still have my sources checkt out to the subfolder portal, have ext build to the subfolder ext and have the bundled tomcat6 in the subfolder tomcat. I update sources in portal via tortoiseSVN, cd into that dir and do 'ant clean start build-ext'. Then I cd into ext and do 'ant clean deploy'.
Is there somthing I am missing?
Regards
Kolja
Is there somthing I am missing?
Regards
Kolja
Oliver Bayer, modificado 14 Anos atrás.
RE: Using liferay from trunk
Liferay Master Postagens: 894 Data de Entrada: 18/02/09 Postagens Recentes
Hi,
try deleting the contents from ext-dir (previously save modified files to another dir) and re-run "build-ext" from src-dir. It seems to solve the issue. I don't know why but it looks as if the build script isn't copying all new files to ext (only if you delete contents from ext-dir) e.g. some of the new xml files aren't copied to "ext-impl src \ META-INF" as expected.
try deleting the contents from ext-dir (previously save modified files to another dir) and re-run "build-ext" from src-dir. It seems to solve the issue. I don't know why but it looks as if the build script isn't copying all new files to ext (only if you delete contents from ext-dir) e.g. some of the new xml files aren't copied to "ext-impl src \ META-INF" as expected.
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens RecentesOliver Bayer:
try deleting the contents from ext-dir (previously save modified files to another dir) and re-run "build-ext" from src-dir. It seems to solve the issue. I don't know why but it looks as if the build script isn't copying all new files to ext (only if you delete contents from ext-dir) e.g. some of the new xml files aren't copied to "ext-impl src \ META-INF" as expected.
Removed ext, checkt for latest trunk version, did 'ant clean start build-ext' in source dir. In my newly created ext dir I did 'ant clean deploy'. Error persists:
06.10.2009 07:06:31 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performanc
e in production environments was not found on the java.library.path: C:\liferayt
runk\tomcat\jre1.5.0_17\win\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\liferaytrunk
\tomcat\bin;C:\Programme\Java\jdk1.6.0_14\bin;C:\Programme\apache-ant\bin;C:\Pro
gramme\jikes\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Prog
ramme\Intel\WiFi\bin\;C:\Programme\WinSCP\;C:\Programme\MySQL\MySQL Server 5.1\b
in;C:\Programme\Subversion\bin;C:\Programme\BDV\Uniarchiv\Bin\Lead14
06.10.2009 07:06:31 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
06.10.2009 07:06:31 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 932 ms
06.10.2009 07:06:31 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
06.10.2009 07:06:31 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
Loading jar:file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/lib/portal-impl.ja
r!/system.properties
Loading file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/classes/system-ext.pro
perties
Loading jar:file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/lib/portal-impl.ja
r!/portal.properties
Loading file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/classes/portal-ext.pro
perties
07:07:19,768 INFO [DialectDetector:75] Determining dialect for HSQL Database En
gine 1
07:07:19,768 WARN [DialectDetector:90] Liferay is configured to use Hypersonic
as its database. Do NOT use Hypersonic in production. Hypersonic is an embedded
database useful for development and demo'ing purposes. The database settings can
be changed in portal.properties.
07:07:19,877 INFO [DialectDetector:55] Using dialect org.hibernate.dialect.HSQL
Dialect
Loading jar:file:/C:/liferaytrunk/tomcat/webapps/ROOT/WEB-INF/lib/portal-impl.ja
r!/captcha.properties
07:07:23,533 INFO [PortalImpl:263] Portal lib directory /C:/liferaytrunk/tomcat
/webapps/ROOT/WEB-INF/lib/
07:07:40,329 ERROR [ContextLoader:215] Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean def
inition with name 'com.ext.portlet.reports.service.ReportsEntryService.velocity'
defined in class path resource [META-INF/ext-spring.xml]: Could not resolve par
ent bean definition 'baseVelocityService'; nested exception is org.springframewo
rk.beans.factory.NoSuchBeanDefinitionException: No bean named 'baseVelocityServi
ce' is defined
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:1035)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:985)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edLocalBeanDefinition(AbstractBeanFactory.java:971)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
preInstantiateSingletons(DefaultListableBeanFactory.java:420)
at org.springframework.context.support.AbstractApplicationContext.finish
BeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refres
h(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationCon
text(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationConte
xt(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitiali
zed(ContextLoaderListener.java:45)
at com.liferay.portal.spring.context.PortalContextLoaderListener.context
Initialized(PortalContextLoaderListener.java:48)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
t.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:77
1)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.ja
va:627)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.j
ava:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488
)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443
)
at org.apache.catalina.core.StandardService.start(StandardService.java:5
16)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710
)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No b
ean named 'baseVelocityService' is defined
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
getBeanDefinition(DefaultListableBeanFactory.java:387)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edLocalBeanDefinition(AbstractBeanFactory.java:971)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:741)
at org.springframework.beans.factory.support.AbstractBeanFactory.getMerg
edBeanDefinition(AbstractBeanFactory.java:1021)
... 33 more
06.10.2009 07:07:40 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
06.10.2009 07:07:40 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [] startup failed due to previous errors
06.10.2009 07:07:40 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
06.10.2009 07:07:41 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
06.10.2009 07:07:41 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/15 config=null
06.10.2009 07:07:41 org.apache.catalina.startup.Catalina start
INFO: Server startup in 69188 ms
Regards
Kolja
Kolja Köster, modificado 14 Anos atrás.
RE: Using liferay from trunk
Regular Member Postagens: 164 Data de Entrada: 11/05/09 Postagens Recentes
I have rebuilded EVERYTING from scratch, removed all directories, recreated the source dir vom svn, recreated the tomcat dir from the tomcat6 bundle, recreated ext from the ant script and redeployed it from the ant script. THIS solved the issue. However, someone, with mor experience on ant, should perhaps have a look at those. But I am still puzzled that other people can rebuild from ant, and I can not.
Regards
Kolja
Regards
Kolja