File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JForum and the fly likes Running under Jetty 6.1.3 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JForum
Bookmark "Running under Jetty 6.1.3" Watch "Running under Jetty 6.1.3" New topic

Running under Jetty 6.1.3

Migrated From
Ranch Hand

Joined: Apr 22, 2012
Posts: 17424
Hi. I'm testing JForum using Jetty 6.1.3 as my container. It starts up fine. I seem to be getting the following error I believe during the posting process. Has anyone seen this before? I wonder if it is a library conflict, as a previous post hinted at this with a version 5 of Jetty. Thanks for any assistance with this.

117031 [btpool0-1] INFO - Logging using commons-logging.
117109 [btpool0-1] INFO - retrieved system configuration file:$JarURLInputStream@34cdfc
117156 [btpool0-1] INFO - Missing class for creator 'pageflow'. Failed to load Cause: Beehive/Weblogic Creator not available.
117156 [btpool0-1] INFO - Missing classdef for creator 'spring'. Failed to load Cause: org/springframework/beans/factory/BeanFactory
117172 [btpool0-1] INFO - Missing classdef for creator 'script'. Failed to load Cause: org/apache/bsf/BSFException
117266 [btpool0-1] INFO - Missing class for converter 'hibernate'. Failed to load Cause: Failed to find either org.hibernate.Hibernate or net.sf.hibernate.Hibernate.
117281 [btpool0-1] ERROR - Missing config file: WEB-INF/dwr-jforum.xml
117281 [btpool0-1] WARN - Names of known classes are:
117281 [btpool0-1] ERROR org.mortbay.log - /dwr/interface/AjaxUtils.js
java.lang.SecurityException: No class by name: AjaxUtils
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.mortbay.jetty.servlet.ServletHolder.handle(
at org.mortbay.jetty.servlet.ServletHandler.handle(
at org.mortbay.jetty.servlet.SessionHandler.handle(
at org.mortbay.jetty.handler.ContextHandler.handle(
at org.mortbay.jetty.webapp.WebAppContext.handle(
at org.mortbay.jetty.handler.HandlerWrapper.handle(
at org.mortbay.jetty.Server.handle(
at org.mortbay.jetty.HttpConnection.handleRequest(
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
at org.mortbay.jetty.HttpParser.parseNext(
at org.mortbay.jetty.HttpParser.parseAvailable(
at org.mortbay.jetty.HttpConnection.handle(
at org.mortbay.thread.BoundedThreadPool$
[originally posted on by cszamudio]
Migrated From
Ranch Hand

Joined: Apr 22, 2012
Posts: 17424
Don't know Jetty, but this looks like a class loader security issue due to having two jar's of different versions. One (or more) are probably in the WEB-INF/lib directory and the other is in a "container" level lib (e.g., Tomcat uses Shared/lib, Common/lib, and System/lib).

The security rules on most webapp containers don't let classes loaded by a "shared" loader load classes from an application level jar. This would allow a web app (like jForum) a way to access system stuff they shouldn't have access to / or accidentally crash all webapps.

So, what may be happening is that the Jetty container is loading DWR as a shared level class, then jForum is using this already loaded class when it is being initialized and it's application level classes are not being found by the class loader.

Most likely the fix is to remove the jar's that exist at the "shared" level from the WEB-INF/lib directory.
[originally posted on by monroe]
I agree. Here's the link:
subject: Running under Jetty 6.1.3
It's not a secret anymore!