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 Tue, 11 Sep 2007 02:22:29 GMT


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 (

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:
>             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