Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 66160 invoked from network); 11 Sep 2007 02:22:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Sep 2007 02:22:54 -0000 Received: (qmail 59848 invoked by uid 500); 11 Sep 2007 02:22:46 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 59798 invoked by uid 500); 11 Sep 2007 02:22:46 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 59787 invoked by uid 99); 11 Sep 2007 02:22:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2007 19:22:46 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2007 02:24:24 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DAFC6714208 for ; Mon, 10 Sep 2007 19:22:29 -0700 (PDT) Message-ID: <20285643.1189477349893.JavaMail.jira@brutus> Date: Mon, 10 Sep 2007 19:22:29 -0700 (PDT) From: "Kevan Miller (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6 In-Reply-To: <32441320.1189091071955.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526331 ] Kevan Miller commented on GERONIMO-3457: ---------------------------------------- Whoa... Nice Donald... Bhagwath, definitely worth noting in the Environment section of a Jira, next time... I did see some Jetty startup errors on a Mac OS X 1.6 JRE (https://issues.apache.org/jira/browse/GERONIMO-3454). This is looking like some xalan/xerces library mismatch... Are you on the latest service release of 1.6? > 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.