problems with Cocoon 2.1.7 on Tomcat 5.5.9

[breidle3]

Hello,

I want to deploy Cocoon 2.1.7. on Tomcat 5.5.9 (using JDK 1.5.0_03) on SuSE Linux 8.1.
I did the standard installation as described in the documentation.
The Tomcat installation worked fine, also starting the Tomcat server is no problem. When deploying the cocoon.war file (building the .WAR file was successful!), the startup process of Tomcat is paused after the Cocoon scheduler is started. Btw, nothing can be found in the log-files. When starting Tomcat, the following lines are output on the console (environment variables JAVA_HOME and JRE_HOME are set to /home/cnc/jdk1.5.0_03) :

[blue]
cnc@u021:home/cnc/Tomcat/jakarta-tomcat-5.5.9/bin> ./catalina.sh run
Using CATALINA_BASE: /home/cnc/Tomcat/jakarta-tomcat-5.5.9
Using CATALINA_HOME: /home/cnc/Tomcat/jakarta-tomcat-5.5.9
Using CATALINA_TMPDIR: /home/cnc/Tomcat/jakarta-tomcat-5.5.9/temp
Using JRE_HOME: /home/cnc/jdk1.5.0_03
27-Jun-2005 11:51:57 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
27-Jun-2005 11:51:57 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3059 ms
27-Jun-2005 11:51:57 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
27-Jun-2005 11:51:57 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.9
27-Jun-2005 11:51:58 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
27-Jun-2005 11:52:01 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive cocoon.war
- Reading standard config net/sourceforge/myfaces/resource/standard-faces-config.xml
- Reading config jar:file:/home/cnc/Tomcat/jakarta-tomcat-5.5.9/temp/myfaces40767.jar!/META-INF/faces-config.xml
- Reading config jar:file:/home/cnc/Tomcat/jakarta-tomcat-5.5.9/temp/myfaces40768.jar!/META-INF/faces-config.xml
- Reading config /WEB-INF/faces-config.xml
- Ignored element 'display-name' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'display-name' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- Ignored element 'display-name' as child of 'servlet'.
- Ignored element 'init-param' as child of 'servlet'.
- ServletContext '/home/cnc/Tomcat/jakarta-tomcat-5.5.9/webapps/cocoon/' initialized.
- The database 'db' root directory has been set to /home/cnc/Tomcat/jakarta-tomcat-5.5.9/webapps/cocoon/WEB-INF/db. Keep in mind that if a war upgrade will take place the database will be lost.
- Database points to /home/cnc/Tomcat/jakarta-tomcat-5.5.9/webapps/cocoon/WEB-INF/db
- [main] '/db/system/SysSymbols' Set object system_SysConfig
- [main] '/db/system/SysConfig' Set document database.xml
- [main] '/db/system/SysSymbols' Set object meta_Metas
- [main] '/db/system/SysSymbols' Set object meta_Metas_system_SysConfig
- Database 'db' successfully opened
- Xindice server successfully started
trying to register database
trying to register database
- RAMJobStore initialized.
- Quartz scheduler 'Cocoon
- Quartz scheduler version: 1.4.5
- Scheduler Cocoon_$_Mon_Jun_27_11:52:35_CEST_2005 started.
[/blue]

Here the startup process on Linux platforms stops.
On Windows platforms, the startup process continues (same preceding lines !) with the following lines:

[blue]
WARN! *** JMS block is installed but jms client library not found. ***
- For the jms block to work you must install and start a JMS server and place th
e client jar in WEB-INF/lib.
- The default server, OpenJMS is configured in cocoon.xconf but is not bundled w
ith Cocoon.
27.06.2005 12:06:55 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
27.06.2005 12:06:55 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
27.06.2005 12:06:55 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/62 config=null
27.06.2005 12:06:55 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
27.06.2005 12:06:55 org.apache.catalina.startup.Catalina start
INFO: Server startup in 160657 ms
[/blue]

Obviously, some final steps of the Tomcat startup are missing on the Linux platform. As a result, it is not possible to call the start pages of Tomcat and Cocoon.

The strange thing is that on a Windows system the standard installation of Cocoon and Tomcat worked fine.

I tried also the same configuration described above with JDK 1.4.2_08 as well as Tomcat 5.5.4 with Cocoon 2.1.6. on
Linux 8.1 and 9.0 - and I got the same (negative) results.

Do you have an idea why this strange behaviour occurs ?
Thanks a lot in advance for your help !
Klaus

 

[primitiveorigin]

Hi,

I recently went through the same process and came to the conclusion that Tomcat 5.x.x just does not work with Cocoon 2.x

Other combinations of versions seemed to work except that one, even with Java 1.5 installed.

In the end, I reverted to Tomcat 4.x, Cocoon 2.x and Java 1.4.2_08 with success.

Not a solution for you, but just wanted to share my time and trouble.

Cheers, Jared.

 

[breidle3]

Hi Jared,

thank you very much for your valuable help !!

I had experienced that when using the standard installation (just unzipping and un-tar-ing), I did not succeed using Tomcat 4.x (I tested 4.1.27) in combination with Cocoon 2.1.x.

But I succeeded using Tomcat 4.x in combination with Cocoon 2.0.x (I tested 2.0.4). A stable behaviour could be
recognized using JDK 1.5.0_03. When using JDK 1.4.2_08, I got an error when clicking on a link on the Cocoon start page: [blue]The output format must have a '{

http://xml.apache.org/xalan}content-handler'

property![/blue]. Maybe some Xalan settings have to be changed when using JDK 1.4.2_08 ?!

Cheers,
Klaus