You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Bhagwath Vadyala (JIRA)" <ji...@apache.org> on 2007/09/06 17:04:31 UTC
[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] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo
2.0.1-jetty6
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525524 ]
Kevan Miller commented on GERONIMO-3457:
----------------------------------------
Hmm. Drools 4.0.0 (I didn't see a 4.0.1) works fine for me on Mac OS X.
Could you run a test with 4.0.0 and also try a run on a non-Windows system (e.g. Linux)? Trying to rule out some possibilities...
> 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
Posted by "Kevan Miller (JIRA)" <ji...@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.
[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo
2.0.1-jetty6
Posted by "Bhagwath Vadyala (JIRA)" <ji...@apache.org>.
[ 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
Posted by "Bhagwath Vadyala (JIRA)" <ji...@apache.org>.
[ 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
ppContext@1dee2cd{/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 org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:379)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:448)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
rnelConfigurationManager.java:187)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:530)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:511)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
ssByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java:38)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:830)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
7)
at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java:35)
at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java:96)
at org.apache.geronimo.gbean.GBeanLifecycle$$EnhancerByCGLIB$$2e9b3feb.s
tartConfiguration(<generated>)
at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCom
mand.java:67)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:121)
... 55 more
Caused by: java.lang.AbstractMethodError
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.setDocumentInfo(D
OM2TO.java:373)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java
:127)
at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DOM2TO.java
:94)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transfor
mIdentity(TransformerImpl.java:663)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transfor
m(TransformerImpl.java:709)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transfor
m(TransformerImpl.java:313)
at org.apache.jackrabbit.core.util.DOMBuilder.write(DOMBuilder.java:80)
at org.apache.jackrabbit.core.nodetype.xml.NodeTypeWriter.write(NodeType
Writer.java:278)
at org.apache.jackrabbit.core.nodetype.xml.NodeTypeWriter.write(NodeType
Writer.java:65)
at org.apache.jackrabbit.core.nodetype.NodeTypeDefStore.store(NodeTypeDe
fStore.java:71)
at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.persistCustomNod
eTypeDefs(NodeTypeRegistry.java:806)
at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.registerNodeType
(NodeTypeRegistry.java:177)
at org.drools.repository.JackrabbitRepositoryConfigurator.registerNodeTy
pesFromCndFile(JackrabbitRepositoryConfigurator.java:130)
at org.drools.repository.JackrabbitRepositoryConfigurator.setupRulesRepo
sitory(JackrabbitRepositoryConfigurator.java:64)
at org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(
BRMSRepositoryConfiguration.java:64)
at org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(
BRMSRepositoryConfiguration.java:56)
at org.drools.brms.server.repository.BRMSRepositoryConfiguration$$FastCl
assByCGLIB$$8078a474.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocation
Context.java:45)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
Context.java:57)
at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke(Rollback
Interceptor.java:34)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
Context.java:69)
at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(Met
hodContextInterceptor.java:27)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
Context.java:69)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:
103)
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(Java
BeanInterceptor.java:154)
at org.jboss.seam.intercept.JavaBeanInterceptor.intercept(JavaBeanInterc
eptor.java:89)
at org.drools.brms.server.repository.BRMSRepositoryConfiguration$$Enhanc
erByCGLIB$$afe0a349.create(<generated>)
... 61 more
> 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
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo
2.0.1-jetty6
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532366 ]
Kevan Miller commented on GERONIMO-3457:
----------------------------------------
I don't see how Geronimo could be causing this error. I may be proven wrong, but I don't think we inclde a w3c dom implementation in our Geronimo 2.0 distributions. So, not sure how we could be responsible for an xslt and w3c mismatch in the the JRE.
How are you setting up your java environment for java service wrapper? Are you sure you're 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
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526261 ]
Donald Woods commented on GERONIMO-3457:
----------------------------------------
What happens if you use a Sun 1.5.0 JDK instead???
> 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
Posted by "Bhagwath Vadyala (JIRA)" <ji...@apache.org>.
[ 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] Commented: (GERONIMO-3457) Drools BRMS issue using geronimo
2.0.1-jetty6
Posted by "Bhagwath Vadyala (JIRA)" <ji...@apache.org>.
[ 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
Posted by "Bhagwath Vadyala (JIRA)" <ji...@apache.org>.
[ 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] Updated: (GERONIMO-3457) Drools BRMS issue using geronimo
2.0.1-jetty6
Posted by "Bhagwath Vadyala (JIRA)" <ji...@apache.org>.
[ 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.