« Return to Thread: Merb app. deployed to Websphere 6.1 fails on both AIX and Windows

Re: Merb app. deployed to Websphere 6.1 fails on both AIX and Windows

by Nick Sieger-2 :: Rate this Message:

Reply to Author | View in Thread

On Wed, Aug 6, 2008 at 12:54 PM, Wes Gamble <weyus@...> wrote:

> All,
>
> Any Websphere - heads in the house?.
>
> I've generated a WAR file around a small Merb. (0.9.3) app. using Warbler
> (0.9.10).  Although I can get it to work fine in Websphere's Community
> Edition (which is basically Apache Geronimo/Tomcat), I cannot get it to work
> on Websphere 6.1 (on either AIX or Windows XP).  "Get it to work" means
> successfully retrieve the request for "/" which is mapped to my "users"
> controller, index action.
>
> I know that the Web app. deployment has worked in Websphere because I can
> retrieve all of the static resources (images, stylesheets) with no problem.
>
> Behavior in Websphere 6.1 on Windows XP:
>
> 1A) If I request "/", I see the following error:
>
> [8/6/08 20:22:02:301 BST] 0000002d WebApp        E   [Servlet
> Error]-[com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor
> incompatible with com.ibm.wsspi.webcontainer.servlet.IServletWrapper]:
> java.lang.ClassCastException:
> com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor incompatible
> with com.ibm.wsspi.webcontainer.servlet.IServletWrapper
>   at
> com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:499)
>   at
> com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:111)
>   at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3107)
>   at
> com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)
>   ....
>
> This makes me think that the container is unable to handle just using the
> RackFilter (org.jruby.rack.RackFilter) for some reason.
>
> 1B) If I request "/users/index" directly, I see the following errors:
>
> [8/6/08 20:41:12:697 BST] 0000002d SRTServletRes W   WARNING: Cannot set
> status. Response already committed.
> [8/6/08 20:41:12:713 BST] 0000002d SRTServletRes W   WARNING: Cannot set
> header. Response already committed.
>
> Behavior in Websphere 6.1 on AIX:
>
> 2) If I request "/" or "/users/index", I see no errors in the out or err
> logs, just "Error 404: SRVE0190E: File not found: {0} " on the screen.
>
> Clearly the servlet filter isn't being picked up at all here.
>
> My next step will be to insert a standard index.jsp file into the Web app.
> and see if I can get a default "/" request to work that way.
>
> Any insight that anyone can provide would be most appreciated.

I have no websphere experience, but I can suggest a couple of things to try:

- If you want to still use the filter, try playing around with the
filter prefix in web.xml. (Maybe try '/' instead of '/*' and so on.)
- You can also try the servlet version, which would use config like
this in web.xml. Comment out or remove the filter/filter-mapping bits
and use this instead:
  <servlet>
    <servlet-name>RackServlet</servlet-name>
    <servlet-class>org.jruby.rack.RackServlet</servlet-class>
  </servlet>
  <servlet-mapping>
    <servlet-name>RackServlet</servlet-name>
    <url-pattern>/*</url-pattern>
  </servlet-mapping>

Cheers,
/Nick

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


 « Return to Thread: Merb app. deployed to Websphere 6.1 fails on both AIX and Windows