geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
Date Sat, 08 Sep 2007 14:52:29 GMT


Kevan Miller commented on GERONIMO-3457:

K. I'm not seeing a redirect problem on 4.0.1, either. 

I'm deploying the WAR as is on an unaltered 2.0.1 Jetty server.

I have seen an intermittent error logged on the server. Seems to only occur w/ Safari. All
seems to work even when I see the error:

	at org.mortbay.jetty.HttpGenerator.flush(
	at org.mortbay.jetty.HttpGenerator.complete(
	at org.mortbay.jetty.HttpConnection.commitResponse(
	at org.mortbay.jetty.HttpConnection$Output.sendContent(
	at org.mortbay.jetty.servlet.DefaultServlet.sendData(
	at org.mortbay.jetty.servlet.DefaultServlet.doGet(
	at javax.servlet.http.HttpServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.mortbay.jetty.servlet.ServletHolder.handle(
	at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
	at org.jboss.seam.web.ContextFilter.doFilter(
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
	at org.mortbay.jetty.servlet.ServletHandler.handle(
	at org.mortbay.jetty.servlet.SessionHandler.handle(
	at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(
	at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(
	at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(
	at org.mortbay.jetty.handler.ContextHandler.handle(
	at org.mortbay.jetty.webapp.WebAppContext.handle(
	at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
	at org.mortbay.jetty.handler.HandlerCollection.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.apache.geronimo.pool.ThreadPool$
	at org.apache.geronimo.pool.ThreadPool$
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$
Caused by: Broken pipe
	at Method)
	at org.mortbay.jetty.HttpGenerator.flush(
	... 36 more
10:16:44,869 WARN  [log] /drools-jbrms/org.drools.brms.JBRMS/welcome.html: org.mortbay.jetty.EofException

> Drools BRMS issue using geronimo 2.0.1-jetty6
> ---------------------------------------------
>                 Key: GERONIMO-3457
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 2.0.1
>         Environment: geronimo 2.0.1-jetty6
> windows
> drools-jbrms 4.0.1
>            Reporter: Bhagwath Vadyala
>         Attachments: drools-error-screenshot.doc, geronimo-jetty-server-log.txt
> We are having an issuing testing drools BRMS 4.0.1 on geronimo 2.0.1 jetty 6 version.
> It deploys fine but when we open the url http://localhost:8080/drools-jbrms, its not
redirecting to correct page.
> We use the same drools-jbrms war file and deploy on jboss-tomcat it works fine and redirects
to the correct page.
> We posted the issue to JBOSS and here is the response from them.
> Michael Neale commented on JBRULES-1150:
> ----------------------------------------
> ok the URL in the browser it wrong.
> Ideally you will put in:
> http://localhost:8080/drools-jbrms
> and it *should* redirect to :
> http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/JBRMS.html
> if it doesn't - then it is a bug with how geronimo is redirecting.
> The index.jsp, which is default, has:
>    <%
>        String redirectURL = "org.drools.brms.JBRMS/JBRMS.html";
>        response.sendRedirect(redirectURL);
>    %>
> which should work as it does on every other app server tried so far.
> unfortunately we don't have resources to support every purmutation of app servers/web
containers so this will require some experimentation. please let me know how you go.
> ..................................................................................
> Please let me know how to fix this issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message