geronimo-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525920
] 

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:

org.mortbay.jetty.EofException
	at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:760)
	at org.mortbay.jetty.HttpGenerator.complete(HttpGenerator.java:646)
	at org.mortbay.jetty.HttpConnection.commitResponse(HttpConnection.java:584)
	at org.mortbay.jetty.HttpConnection$Output.sendContent(HttpConnection.java:965)
	at org.mortbay.jetty.servlet.DefaultServlet.sendData(DefaultServlet.java:655)
	at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:416)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:65)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
	at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:56)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46)
	at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58)
	at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
	at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
	at org.mortbay.jetty.Server.handle(Server.java:313)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
	at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201)
	at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:613)
Caused by: java.io.IOException: Broken pipe
	at sun.nio.ch.FileDispatcher.write0(Native Method)
	at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
	at sun.nio.ch.IOUtil.write(IOUtil.java:60)
	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
	at org.mortbay.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:166)
	at org.mortbay.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:208)
	at org.mortbay.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:271)
	at org.mortbay.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:198)
	at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:685)
	... 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: https://issues.apache.org/jira/browse/GERONIMO-3457
>             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.


Mime
View raw message