Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
Just an update on this for whoever is interested: I've been in discussions with Vikrant, and both of us have been able to get the M1 snapshot of Guvnor working with WebSphere 6.1. The latest snapshots however fail as described in the Guvnor bug I mentioned in an earlier email. If anyone has any success, or is working on this, please join in and let us know your results. - SteveN On 23/09/08 3:49 PM, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it is not that serious a problem as I initially thought. As I mentioned the URL(adding the index.jsp) works, so there is an easy work-around available. The main bug seems to be that if a URL is sent to WebSphere which does not have a physical file in it the filter which should kick in and re-direct does not do so. (http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK27620) This has nothing to do with the BRMS of course and is a problem for all Web-Apps in this version of Websphere(We are using 6.1.0.0). Adding the index.jsp to the URL seems to work fine for now. I am working on the BRMS to see if there are any other side-effects of this. Maybe, we should update a Wiki or troubleshooting doc on this so that it is known to the community. Digging around IBM Support after my post, I have found quite a few bugs mentioned in version 6.1 regarding how Servlet Filters work and of some on JSF(Especially JBOSS Seam) problems with the particular version. (http://www-01.ibm.com/support/docview.wss?uid=swg1PK47367) IBM has however provided patches for all of them and I am going to give another shot at seeing the behavior after upgrading to a higher release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Neale Sent: Tuesday, September 23, 2008 5:25 AM To: Rules Users List Subject: Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1 Hi Vikrant. well the drools-guvnor/ doesn't use a filter so much as it is default web.xml behaviour - you can specify a welcome page, which it goes to when the root path is supplied. If Websphere 6.1 can't even do that - I would say something is seriously wrong (may be a bad install?) - you could try it with a really simple war that just has 1 jsp and a web.xml and see if it happens with it? although I think: As for servlet filters - as we use Seam, it uses servlet filters to manage lifecycles, so yes, that could be it (if its not the above). It isn't possible to replace the filters, as they do a very different job from servlets (although the difference is subtle). What would be better would be to work out what the problem is with websphere and filters I think. On Mon, Sep 22, 2008 at 9:34 PM, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it clearly is a problem with filters as the following works in WebSphere: http://localhost:9080/drools-guvnor/index.jsp However just typing http://localhost:9080/drools-guvnor does not and gives you the Ugly 500. Cheers, Vikrant From: Vikrant Yagnick Sent: Monday, September 22, 2008 4:38 PM To: Rules Users List Subject: Deploying the BRMS on Web-Sphere 6.1 Hi All, Has anyone been able to deploy the BRMS War file on Websphere 6.1. The BRMS deploys without problems , but I get the following error when I try to access the BRMS: Error 500: com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor incompatible with com.ibm.wsspi.webcontainer.servlet.IServletWrapper. However, the WebDAV servlet still works. I dug around a little, and have found that this problem has occurred for other web-applications as well who have provided a workaround: http://wiki.merbivore.com/pages/deploying-a-merb-application-to-a-jee-contain er-us (Read Step 7) The problem seems to be related to Servlet-Filters. These do not seem to work correctly with Websphere 6.1. In the site mentioned they have replaced the servlet-filter with a normal server. (The BRMS seems to use a servlet filter for /* url mapping). I have seen posts on other forums regarding the BRMS deployment on Websphere 6.1 but no answers as to how to make this work. Any, help would be appreciated. Cheers, Vikrant MASTEK LTD. Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~ ~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any
Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
Great work Vikram. We use seam to help insulate us from container specifics. Please do update the wiki with your findings. As a worst case, perhaps a client side redirect to index could help (so URL has a file in it). But it does sound like a websphere bug. Sent from my iPhone On 23/09/2008, at 15:49, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it is not that serious a problem as I initially thought. As I mentioned the URL(adding the index.jsp) works, so there is an easy work-around available. The main bug seems to be that if a URL is sent to WebSphere which does not have a physical file in it the filter which should kick in and re-direct does not do so. (http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK27620 ) This has nothing to do with the BRMS of course and is a problem for all Web-Apps in this version of Websphere(We are using 6.1.0.0). Adding the index.jsp to the URL seems to work fine for now. I am working on the BRMS to see if there are any other side-effects of this. Maybe, we should update a Wiki or troubleshooting doc on this so that it is known to the community. Digging around IBM Support after my post, I have found quite a few bugs mentioned in version 6.1 regarding how Servlet Filters work and of some on JSF(Especially JBOSS Seam) problems with the particular version. (http://www-01.ibm.com/support/docview.wss?uid=swg1PK47367) IBM has however provided patches for all of them and I am going to give another shot at seeing the behavior after upgrading to a higher release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Michael Neale Sent: Tuesday, September 23, 2008 5:25 AM To: Rules Users List Subject: Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1 Hi Vikrant. well the drools-guvnor/ doesn't use a filter so much as it is default web.xml behaviour - you can specify a welcome page, which it goes to when the root path is supplied. If Websphere 6.1 can't even do that - I would say something is seriously wrong (may be a bad install?) - you could try it with a really simple war that just has 1 jsp and a web.xml and see if it happens with it? although I think: As for servlet filters - as we use Seam, it uses servlet filters to manage lifecycles, so yes, that could be it (if its not the above). It isn't possible to replace the filters, as they do a very different job from servlets (although the difference is subtle). What would be better would be to work out what the problem is with websphere and filters I think. On Mon, Sep 22, 2008 at 9:34 PM, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it clearly is a problem with filters as the following works in WebSphere: http://localhost:9080/drools-guvnor/index.jsp However just typing http://localhost:9080/drools-guvnor does not and gives you the Ugly 500. Cheers, Vikrant From: Vikrant Yagnick Sent: Monday, September 22, 2008 4:38 PM To: Rules Users List Subject: Deploying the BRMS on Web-Sphere 6.1 Hi All, Has anyone been able to deploy the BRMS War file on Websphere 6.1. The BRMS deploys without problems , but I get the following error when I try to access the BRMS: Error 500: com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor incompatible with com.ibm.wsspi.webcontainer.servlet.IServletWrapper. However, the WebDAV servlet still works. I dug around a little, and have found that this problem has occurred for other web-applications as well who have provided a workaround: http://wiki.merbivore.com/pages/deploying-a-merb-application-to-a-jee-container-us (Read Step 7) The problem seems to be related to Servlet-Filters. These do not seem to work correctly with Websphere 6.1. In the site mentioned they have replaced the servlet-filter with a normal server. (The BRMS seems to use a servlet filter for /* url mapping). I have seen posts on other forums regarding the BRMS deployment on Websphere 6.1 but no answers as to how to make this work. Any, help would be appreciated. Cheers, Vikrant MASTEK LTD. Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ ~~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its
RE: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
I never use the 0.0 versions of IBM products, avoid the headaches and wait for at least the first fixpacks. Our existing apps moved fine from 6.0 to 6.1.0.9, did not try Drools BRMS though. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikrant Yagnick Sent: 23 September 2008 07:50 To: Rules Users List Subject: RE: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1 Well it is not that serious a problem as I initially thought. As I mentioned the URL(adding the index.jsp) works, so there is an easy work-around available. The main bug seems to be that if a URL is sent to WebSphere which does not have a physical file in it the filter which should kick in and re-direct does not do so. (http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK27620) This has nothing to do with the BRMS of course and is a problem for all Web-Apps in this version of Websphere(We are using 6.1.0.0). Adding the index.jsp to the URL seems to work fine for now. I am working on the BRMS to see if there are any other side-effects of this. Maybe, we should update a Wiki or troubleshooting doc on this so that it is known to the community. Digging around IBM Support after my post, I have found quite a few bugs mentioned in version 6.1 regarding how Servlet Filters work and of some on JSF(Especially JBOSS Seam) problems with the particular version. (http://www-01.ibm.com/support/docview.wss?uid=swg1PK47367) IBM has however provided patches for all of them and I am going to give another shot at seeing the behavior after upgrading to a higher release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Neale Sent: Tuesday, September 23, 2008 5:25 AM To: Rules Users List Subject: Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1 Hi Vikrant. well the drools-guvnor/ doesn't use a filter so much as it is default web.xml behaviour - you can specify a welcome page, which it goes to when the root path is supplied. If Websphere 6.1 can't even do that - I would say something is seriously wrong (may be a bad install?) - you could try it with a really simple war that just has 1 jsp and a web.xml and see if it happens with it? although I think: As for servlet filters - as we use Seam, it uses servlet filters to manage lifecycles, so yes, that could be it (if its not the above). It isn't possible to replace the filters, as they do a very different job from servlets (although the difference is subtle). What would be better would be to work out what the problem is with websphere and filters I think. On Mon, Sep 22, 2008 at 9:34 PM, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it clearly is a problem with filters as the following works in WebSphere: http://localhost:9080/drools-guvnor/index.jsp However just typing http://localhost:9080/drools-guvnor does not and gives you the Ugly 500. Cheers, Vikrant From: Vikrant Yagnick Sent: Monday, September 22, 2008 4:38 PM To: Rules Users List Subject: Deploying the BRMS on Web-Sphere 6.1 Hi All, Has anyone been able to deploy the BRMS War file on Websphere 6.1. The BRMS deploys without problems , but I get the following error when I try to access the BRMS: Error 500: com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor incompatible with com.ibm.wsspi.webcontainer.servlet.IServletWrapper. However, the WebDAV servlet still works. I dug around a little, and have found that this problem has occurred for other web-applications as well who have provided a workaround: http://wiki.merbivore.com/pages/deploying-a-merb-application-to-a-jee- container-us (Read Step 7) The problem seems to be related to Servlet-Filters. These do not seem to work correctly with Websphere 6.1. In the site mentioned they have replaced the servlet-filter with a normal server. (The BRMS seems to use a servlet filter for /* url mapping). I have seen posts on other forums regarding the BRMS deployment on Websphere 6.1 but no answers as to how to make this work. Any, help would be appreciated. Cheers, Vikrant MASTEK LTD. Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its
Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
Hi Vikrant. well the drools-guvnor/ doesn't use a filter so much as it is default web.xml behaviour - you can specify a welcome page, which it goes to when the root path is supplied. If Websphere 6.1 can't even do that - I would say something is seriously wrong (may be a bad install?) - you could try it with a really simple war that just has 1 jsp and a web.xml and see if it happens with it? although I think: As for servlet filters - as we use Seam, it uses servlet filters to manage lifecycles, so yes, that could be it (if its not the above). It isn't possible to replace the filters, as they do a very different job from servlets (although the difference is subtle). What would be better would be to work out what the problem is with websphere and filters I think. On Mon, Sep 22, 2008 at 9:34 PM, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it clearly is a problem with filters as the following works in WebSphere: http://localhost:9080/drools-guvnor/index.jsp However just typing http://localhost:9080/drools-guvnor does not and gives you the Ugly 500. Cheers, Vikrant From: Vikrant Yagnick Sent: Monday, September 22, 2008 4:38 PM To: Rules Users List Subject: Deploying the BRMS on Web-Sphere 6.1 Hi All, Has anyone been able to deploy the BRMS War file on Websphere 6.1. The BRMS deploys without problems , but I get the following error when I try to access the BRMS: Error 500: com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor incompatible with com.ibm.wsspi.webcontainer.servlet.IServletWrapper. However, the WebDAV servlet still works. I dug around a little, and have found that this problem has occurred for other web-applications as well who have provided a workaround: http://wiki.merbivore.com/pages/deploying-a-merb-application-to-a-jee-container-us (Read Step 7) The problem seems to be related to Servlet-Filters. These do not seem to work correctly with Websphere 6.1. In the site mentioned they have replaced the servlet-filter with a normal server. (The BRMS seems to use a servlet filter for /* url mapping). I have seen posts on other forums regarding the BRMS deployment on Websphere 6.1 but no answers as to how to make this work. Any, help would be appreciated. Cheers, Vikrant MASTEK LTD. Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server. ~~ ___ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users -- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com ___ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
RE: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
Well it is not that serious a problem as I initially thought. As I mentioned the URL(adding the index.jsp) works, so there is an easy work-around available. The main bug seems to be that if a URL is sent to WebSphere which does not have a physical file in it the filter which should kick in and re-direct does not do so. (http://www-01.ibm.com/support/docview.wss?rs=180uid=swg1PK27620) This has nothing to do with the BRMS of course and is a problem for all Web-Apps in this version of Websphere(We are using 6.1.0.0). Adding the index.jsp to the URL seems to work fine for now. I am working on the BRMS to see if there are any other side-effects of this. Maybe, we should update a Wiki or troubleshooting doc on this so that it is known to the community. Digging around IBM Support after my post, I have found quite a few bugs mentioned in version 6.1 regarding how Servlet Filters work and of some on JSF(Especially JBOSS Seam) problems with the particular version. (http://www-01.ibm.com/support/docview.wss?uid=swg1PK47367) IBM has however provided patches for all of them and I am going to give another shot at seeing the behavior after upgrading to a higher release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Neale Sent: Tuesday, September 23, 2008 5:25 AM To: Rules Users List Subject: Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1 Hi Vikrant. well the drools-guvnor/ doesn't use a filter so much as it is default web.xml behaviour - you can specify a welcome page, which it goes to when the root path is supplied. If Websphere 6.1 can't even do that - I would say something is seriously wrong (may be a bad install?) - you could try it with a really simple war that just has 1 jsp and a web.xml and see if it happens with it? although I think: As for servlet filters - as we use Seam, it uses servlet filters to manage lifecycles, so yes, that could be it (if its not the above). It isn't possible to replace the filters, as they do a very different job from servlets (although the difference is subtle). What would be better would be to work out what the problem is with websphere and filters I think. On Mon, Sep 22, 2008 at 9:34 PM, Vikrant Yagnick [EMAIL PROTECTED] wrote: Well it clearly is a problem with filters as the following works in WebSphere: http://localhost:9080/drools-guvnor/index.jsp However just typing http://localhost:9080/drools-guvnor does not and gives you the Ugly 500. Cheers, Vikrant From: Vikrant Yagnick Sent: Monday, September 22, 2008 4:38 PM To: Rules Users List Subject: Deploying the BRMS on Web-Sphere 6.1 Hi All, Has anyone been able to deploy the BRMS War file on Websphere 6.1. The BRMS deploys without problems , but I get the following error when I try to access the BRMS: Error 500: com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor incompatible with com.ibm.wsspi.webcontainer.servlet.IServletWrapper. However, the WebDAV servlet still works. I dug around a little, and have found that this problem has occurred for other web-applications as well who have provided a workaround: http://wiki.merbivore.com/pages/deploying-a-merb-application-to-a-jee-container-us (Read Step 7) The problem seems to be related to Servlet-Filters. These do not seem to work correctly with Websphere 6.1. In the site mentioned they have replaced the servlet-filter with a normal server. (The BRMS seems to use a servlet filter for /* url mapping). I have seen posts on other forums regarding the BRMS deployment on Websphere 6.1 but no answers as to how to make this work. Any, help would be appreciated. Cheers, Vikrant MASTEK LTD. Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server
