Resource not found exceptions with seam using mod_jk

[todd.nash]

I am running an application built on Seam using standard Richfaces/Facelets components. Everything works fine when you talk to JBoss directly, however as soon as we hooked up Apache using mod_jk and try to forward to a single JBoss node (not clustered yet or loadbalanced) we get errors on the home page that some of the resources cannot be found:

17:17:32,953 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
org.ajax4jsf.resource.ResourceNotFoundException: Resource not registered : org.ajax4jsf.javascript.AjaxScript.seam ...

It appears that ".seam" is being appended to the javascript resource requests (not just the ajax ones) and some of the image requests (i.e. the page source shows the images for the tabs as images/theImage.gif.seam ) . I don't have access to the server right now to give you the full error message, but it is similar to the one above.

Is there a setup issue I missed in the mod_jk setup or am I missing a context setting on the JBoss server?

Thanks for any help.

[mocha]

I had success using the following guide to get Apache 2 running in front of JBoss 4.2.2.GA/Seam 2.0.0.GA:
http://www.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss

the Seam application I installed included ajax/richfaces usage. No problems were encountered with this.

[shane.bryzak]

There's also a guide on my blog:

http://shane.bryzak.com/blog/articles/installing_apache_httpd_and_jboss

[supernovasoftware.com]

Could you comment on the advantages and disadvantages of Apache HTTPD vs JBoss Native in the context of a Seam/Facelets application that serves very little static content?

[todd.nash]

I discovered my problem was not having the correct filter referenced for RichFaces. This was causing a problem with resolving the javascript references that the Richfaces component was injecting into the JSF page.

All is well now.

[todd.nash]

[Could you comment on the advantages and disadvantages of Apache HTTPD vs JBoss Native in the context of a Seam/Facelets application that serves very little static content?]

I'm no expert on this, but for our application(s), we use Apache to do load balancing in addition to handling virtual servers. We have applications that use Tomcat and applications that use JBoss. Apache with mod_jk allows us to point the request to point to the correct app server based upon the context.

If you have a clustered environment, fronting the cluster with Apache is a cheap way of load balancing across the cluster. I don't know right off hand whether or not JBoss provides a cluster manager server that will load balance for you, like WebLogic does.

[mocha]

Jason, the usual reason for fronting with Apache is to support load balancing/failover and to provide an extra layer of security. The seam performance testing with DELL used this approach. See http://www.dell.com/downloads/global/power/jbossworld_2006_june_jaffe.pdf