[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534158 ] Bhagwath Vadyala commented on GERONIMO-3457: I donot know whether Geronimo or jetty which is causing this error. Yes we are using G 2.0.1 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.
[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526459 ] Bhagwath Vadyala commented on GERONIMO-3457: we are using jdk1.6.0_01. 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.
[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526236 ] Bhagwath Vadyala commented on GERONIMO-3457: Here is the exception I am getting now with drools 4.0.1 brms war file deployed on geronimo 2.0.1-jetty6 I didnot make any changes to geronimo server or drools-brms war file after downloading.I directly deployed it without any changes and i see this exception. please let me know how i can fix this error. Geronimo Application Server started Setting up the repository, registering node types etc. 15:25:28,607 ERROR [log] Failed startup of context org.mortbay.jetty.webapp.WebA [EMAIL PROTECTED]/drools-jbrms,file:/C:/geronimo-jetty6-jee5-2.0.1/repository/d efault/drools-jbrms/1189452176492/drools-jbrms-1189452176492.war/} java.lang.RuntimeException: exception invoking: create at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:131) at org.jboss.seam.Component.callComponentMethod(Component.java:1802) at org.jboss.seam.Component.callCreateMethod(Component.java:1725) at org.jboss.seam.Component.newInstance(Component.java:1714) at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:165) at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:13 7) at org.jboss.seam.init.Initialization.init(Initialization.java:479) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.j ava:33) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler. java:530) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.jav a:1218) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java: 500) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448 ) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java: 40) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.doStart(A bstractImmutableHandler.java:38) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java: 40) at org.apache.geronimo.jetty6.JettyWebAppContext$StartCommand.lifecycleM ethod(JettyWebAppContext.java:361) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycle Command(AbstractImmutableHandler.java:54) at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.lifecycle Command(ThreadClassloaderHandler.java:57) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycle Command(AbstractImmutableHandler.java:52) at org.apache.geronimo.jetty6.handler.InstanceContextHandler.lifecycleCo mmand(InstanceContextHandler.java:81) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycle Command(AbstractImmutableHandler.java:52) at org.apache.geronimo.jetty6.handler.UserTransactionHandler.lifecycleCo mmand(UserTransactionHandler.java:63) at org.apache.geronimo.jetty6.handler.AbstractImmutableHandler.lifecycle Command(AbstractImmutableHandler.java:52) at org.apache.geronimo.jetty6.handler.ComponentContextHandler.lifecycleC ommand(ComponentContextHandler.java:57) at org.apache.geronimo.jetty6.JettyWebAppContext.doStart(JettyWebAppCont ext.java:330) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:996) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.j ava:539) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GB eanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDepe ndency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDepe ndency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEve nt(BasicLifecycleMonitor.java:176) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(Bas icLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBr oadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:294) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:553) at
[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526273 ] Bhagwath Vadyala commented on GERONIMO-3457: works fine with 1.5 jdk... But can we make it work with jdk 1.6? because we are using java script engine functionality of 1.6 in our application. 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.
[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525793 ] Bhagwath Vadyala commented on GERONIMO-3457: We downloaded Drools 4.01 from the following site.I think It is just released on 30-August-2007. http://labs.jboss.com/drools/downloads.html Can you please check and see this Drools 4.0.1 BRMS war file works fine for you.If it works fine, can you please let me know if you are directly deploying the war file to geronimo-jetty or making any changes to this war file before deploying. Meanwhile I will try to see whether i can make it run on linux environment using geronimo-jetty. 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.
[jira] Created: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
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 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.
[jira] Updated: (GERONIMO-3457) Drools BRMS issue using geronimo 2.0.1-jetty6
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhagwath Vadyala updated GERONIMO-3457: --- Attachment: geronimo-jetty-server-log.txt drools-error-screenshot.doc error screenshot and server logs 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.
