Hi Anders!
We are also using the jBoss/Cocoon/Tomcat combination. And we had the same problem as you had and solved it in the same way.
When it comes to performance I have been able to acheive response times of around 1 second.
My configuration is as follows:
* Pentium III 500 Mhz, 256 Meg
* Windows 2000
* Oracle 8.1.6i Personal Edition (This process takes about 50 Meg alone)
* Tomcat 3.2 (Running with separate classloader, but in the same process. The EmbeddedTomcat config should be much faster)
* Cocoon 1.8
* jBoss 2.0 FINAL, with a configured ConnectionPool for Oracle
* Xerces 1.2.1 XML Parser
The transaction I am running goes through the following chain:
-Invokes a Cocoon Producer that,
-invokes an EJB method that retrieves data from Oracle (Using the Connection Pool) and returns a XML DOM Document
- the DOM Document is then transformed by XalanXSL to HTML and returned to the Browser
Please observe that it does not take 1 second on the first invocation (The first invocation is generally MUCH slower, maybe even in the order of what you experienced).
This is due to several things:
- The Connection Pool is extremely important and it seems to need to be initialized
- Cocoon needs to pre-compile the XSL
- All Classes need to be loaded in the VM
I haven't used XSP, but my spontaneous guess is that your slow response time is due to the XSP compiling. Try to invoke
the URL a second time and see what happens.
MVH,
gustav boström
the eon company
www.eoncompany.com
o +46-8-54528800
m +46-70-9575154
e gustav.boströ[EMAIL PROTECTED]
-----Original Message-----
From: Anders Lindh [mailto:[EMAIL PROTECTED]]
Sent: den 8 januari 2001 22:30
To: [EMAIL PROTECTED]
Subject: Re: [jBoss-User] jboss, tomcat and cocoon
Allright, I got it working finally. The problem was conflicting xml parsers, and the fact that jboss apparently adds its lib/ and lib/ext directories to the beginning of the classpath. So, if you're experiencing problems, move lib/parser.jar and lib/ext/xml.jar somewhere else, and add them manually in run.sh (after all cocoon includes).
Oh, yeah, my first impressions of Jboss/Tomcat/Cocoon performance are not too positive (30+ seconds for a cocoon xsp example). Anyone have any tips for performce tuning?
- Anders
On Mon, Jan 08, 2001 at 09:13:15PM +0200, Anders Lindh wrote:
>
> Ok, guys, I need help..xs
>
> I've strugled a couple of days and now have jboss, tomcat (embedded) and apache working together. What I still need, and can't get working, is Cocoon. My configuration is: jboss PRE-2.1 (checked out from cvs yesterday), Tomcat 3.2.1, Apache 1.3.14 and Cocoon 1.8. Both jboss and Tomcat have been slightly hacked to enable apj13 communication with apache.
>
> The problem is Cocoon. It works with plain xml files, but xsp files do not (for those who don't know what I'm talking about: Cocoon processes xml/xslt files and has a xml based scripting language called xsp. It compiles these on-demand to servlets and thus allows creation of xml based web apps). Anyway, the error messages are as follows:
>
> java.lang.NoSuchMethodError
> at org.apache.cocoon.processor.xsp.language.java.XSPJavaPreprocessor.process(XSPJavaPreprocessor.java:116)
> at org.apache.cocoon.processor.xsp.language.java.XSPJavaPreprocessor.process(XSPJavaPreprocessor.java:123)
> at org.apache.cocoon.processor.xsp.language.java.XSPJavaPreprocessor.preprocess(XSPJavaPreprocessor.java:81)
> at org.apache.cocoon.processor.xsp.XSPLogicsheet.apply(XSPLogicsheet.java:99)
> at org.apache.cocoon.processor.xsp.XSPProcessor.process(XSPProcessor.java:423)
> at org.apache.cocoon.Engine.handle(Engine.java:359)
> at org.apache.cocoon.Cocoon.service(Cocoon.java:167)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
> at org.apache.tomcat.core.Handler.service(Handler.java:286)
> at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
> at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
> at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
> at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
> at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
> at java.lang.Thread.run(Thread.java:484)
>
>
> Acording to all FAQ and posting I've read, this has to do with Tomcat's classpath settings. If multiple xml processors are found (or a DOM1 compliant is found before the required DOM2) error reports should look like above. But I can't find a working combination. I've tried tweaking jboss's run.sh to no avail. Has anyone succeeded in getting Cocoon working with Tomcat and jboss? What I'd like to know is what classpath does (embedded) Tomcat have (and thus Cocoon)? Is it really the one specified in run.sh, or does jboss do magic with the classpath before starting tomcat?
>
> Thanks,
>
> - Anders
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
