Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Gianny, It was a mutlicast problem. After I turned the firewall off (service iptables stop), the sample app ran as expected. ++Vamsi On Thu, Mar 20, 2008 at 2:24 PM, Gianny Damour < [EMAIL PROTECTED]> wrote: > Hello Vamsi, > > If the applications display distinct numbers, then the nodes do not > see each other. I think this is a problem with multicasting. > > Could you please confirm that you have uncommented the last line of > etc/rc.d/start-server,default.groovy which sets the system property > java.net.preferIPv4Stack? Without this property set to true, > multicasting fails at least on Mac OS X and maybe FC. > > If this property is already set, then I suggest you to check that > multicasting is working ok on your box. > > Thanks, > Gianny > > On 20/03/2008, at 4:08 AM, Vamsavardhana Reddy wrote: > > > Hi Gianny, > > > > I observe that the sample application does not run as expected when > > I try the clustering scenario on FedoraCore. Application running > > on each node displays its own set of numbers starting from 1 with > > the background color of the squares being the node.name set at > > startup. I observed the same behavior with G Jetty 2.1 and G > > Tomcat 2.1 distros. What is to be done differently on Linux? > > > > ++Vamsi > \ >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Gianny, I notice in the Java System Info portlet that java.net.preferIPv4Stack is set to true in both the server instances. I am using bin/geronimo.sh to start the server. It must be something to do with multicast then. ++Vamsi On Thu, Mar 20, 2008 at 2:24 PM, Gianny Damour < [EMAIL PROTECTED]> wrote: > Hello Vamsi, > > If the applications display distinct numbers, then the nodes do not > see each other. I think this is a problem with multicasting. > > Could you please confirm that you have uncommented the last line of > etc/rc.d/start-server,default.groovy which sets the system property > java.net.preferIPv4Stack? Without this property set to true, > multicasting fails at least on Mac OS X and maybe FC. > > If this property is already set, then I suggest you to check that > multicasting is working ok on your box. > > Thanks, > Gianny > > On 20/03/2008, at 4:08 AM, Vamsavardhana Reddy wrote: > > > Hi Gianny, > > > > I observe that the sample application does not run as expected when > > I try the clustering scenario on FedoraCore. Application running > > on each node displays its own set of numbers starting from 1 with > > the background color of the squares being the node.name set at > > startup. I observed the same behavior with G Jetty 2.1 and G > > Tomcat 2.1 distros. What is to be done differently on Linux? > > > > ++Vamsi > \ >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Hello Vamsi, If the applications display distinct numbers, then the nodes do not see each other. I think this is a problem with multicasting. Could you please confirm that you have uncommented the last line of etc/rc.d/start-server,default.groovy which sets the system property java.net.preferIPv4Stack? Without this property set to true, multicasting fails at least on Mac OS X and maybe FC. If this property is already set, then I suggest you to check that multicasting is working ok on your box. Thanks, Gianny On 20/03/2008, at 4:08 AM, Vamsavardhana Reddy wrote: Hi Gianny, I observe that the sample application does not run as expected when I try the clustering scenario on FedoraCore. Application running on each node displays its own set of numbers starting from 1 with the background color of the squares being the node.name set at startup. I observed the same behavior with G Jetty 2.1 and G Tomcat 2.1 distros. What is to be done differently on Linux? ++Vamsi \
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Hi Gianny, I observe that the sample application does not run as expected when I try the clustering scenario on FedoraCore. Application running on each node displays its own set of numbers starting from 1 with the background color of the squares being the node.name set at startup. I observed the same behavior with G Jetty 2.1 and G Tomcat 2.1 distros. What is to be done differently on Linux? ++Vamsi On Wed, Mar 19, 2008 at 4:50 PM, Gianny Damour < [EMAIL PROTECTED]> wrote: > Hello Vamsi, > > I verified on G Jetty 2.1 with Safari... Based on your previous > problem description (black boxes instead of numbered ones), I > inferred that somehow your browser was not propagating a session > cookie to the server. So, I decided to give a shot with FireFox and > interestingly I was able to identify the problem. In the standard DD, > the demo application used to declare this: > > > org.mortbay.jetty.servlet.SessionPath > /wadi > > > This instructs Jetty to set the session cookie path to /wadi. As the > demo application is deployed to /wadi-webapp, your browser or FireFox > do not send to the server the cookies for the path /wadi; hence, the > problem. > > So, I dropped the above xml fragment from the DD, tested with FireFox > and deployed another snapshot: http:// > snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-webapp/2.0- > SNAPSHOT/wadi-webapp-2.0-20080319.110523-12.war > > Thanks for giving it a try and your patience. > > Thanks, > Gianny > > > On 19/03/2008, at 8:55 PM, Vamsavardhana Reddy wrote: > > > Gianny, > > > > I was able to get the sample application deployed and running as > > expected on G Tomcat 2.1. But, it still does not run correctly on > > G Jetty 2.1. Have you verified on G Jetty 2.1? > > > > ++Vamsi > > > > On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy > > <[EMAIL PROTECTED]> wrote: > > Thanks Gianny. I will try with the new DD and get back if there is > > any problem. > > > > ++Vamsi > > > > > > On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour > > <[EMAIL PROTECTED]> wrote: > > Hello, > > > > This is a problem with the deployment descriptor. You name of the > > clustering substitution group element is tomcat-clustering-wadi for > > tomcat and not clustering-wadi. As a matter of fact, I have on my to- > > do list a task to refactor substitution group element builders for > > Tomcat, Jetty and OpenEJB so that all of them offer the same external > > structure to end-users. > > > > Here is an updated DD: > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-1.2"> > > > > > > > > org.codehaus.wadi > > wadi-webapp > > 2.0M3-SNAPSHOT > > war > > > > > > > > <-- this is the correct element name to > > use for tomcat. > > > > > > > > Thanks, > > Gianny > > > > > > On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: > > > > > I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ > > > clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. > > > even though org.apache.geronimo.configs/jetty6-clustering-builder- > > > wadi//car is running, deploying the sample application resulted in > > > an error given below: > > > > > > > > error: cvc-complex-type.2.4a: Expected elements 'context- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > cross- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ > > > web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// > > > java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here > > > > > > > > > >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Gianny, With G Tomcat 2.1 clustering, I sometimes see an error message like the following: 18:25:46,203 ERROR [StandardManager] Could not acquire session [31ECCD48F5DEB00E A4289FBEEC7FDA8A] What is wrong? ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour < [EMAIL PROTECTED]> wrote: > Hello, > > This is a problem with the deployment descriptor. You name of the > clustering substitution group element is tomcat-clustering-wadi for > tomcat and not clustering-wadi. As a matter of fact, I have on my to- > do list a task to refactor substitution group element builders for > Tomcat, Jetty and OpenEJB so that all of them offer the same external > structure to end-users. > > Here is an updated DD: > > > > http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2";> > > > > org.codehaus.wadi > wadi-webapp > 2.0M3-SNAPSHOT > war > > > > <-- this is the correct element name to > use for tomcat. > > > > Thanks, > Gianny > > > On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: > > > I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ > > clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. > > even though org.apache.geronimo.configs/jetty6-clustering-builder- > > wadi//car is running, deploying the sample application resulted in > > an error given below: > > > > > error: cvc-complex-type.2.4a: Expected elements 'context- > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ > > web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// > > java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here > > > > > > > > The deployment plan I am using is: > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-1.2"> > > > > > > > > org.codehaus.wadi > > wadi-webapp > > 2.0M3-SNAPSHOT > > war > > > > > > > > > > > > > > > >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Thanks Gianny. The sample works now. ++Vamsi On Wed, Mar 19, 2008 at 4:50 PM, Gianny Damour < [EMAIL PROTECTED]> wrote: > Hello Vamsi, > > I verified on G Jetty 2.1 with Safari... Based on your previous > problem description (black boxes instead of numbered ones), I > inferred that somehow your browser was not propagating a session > cookie to the server. So, I decided to give a shot with FireFox and > interestingly I was able to identify the problem. In the standard DD, > the demo application used to declare this: > > > org.mortbay.jetty.servlet.SessionPath > /wadi > > > This instructs Jetty to set the session cookie path to /wadi. As the > demo application is deployed to /wadi-webapp, your browser or FireFox > do not send to the server the cookies for the path /wadi; hence, the > problem. > > So, I dropped the above xml fragment from the DD, tested with FireFox > and deployed another snapshot: http:// > snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-webapp/2.0- > SNAPSHOT/wadi-webapp-2.0-20080319.110523-12.war > > Thanks for giving it a try and your patience. > > Thanks, > Gianny > > > On 19/03/2008, at 8:55 PM, Vamsavardhana Reddy wrote: > > > Gianny, > > > > I was able to get the sample application deployed and running as > > expected on G Tomcat 2.1. But, it still does not run correctly on > > G Jetty 2.1. Have you verified on G Jetty 2.1? > > > > ++Vamsi > > > > On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy > > <[EMAIL PROTECTED]> wrote: > > Thanks Gianny. I will try with the new DD and get back if there is > > any problem. > > > > ++Vamsi > > > > > > On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour > > <[EMAIL PROTECTED]> wrote: > > Hello, > > > > This is a problem with the deployment descriptor. You name of the > > clustering substitution group element is tomcat-clustering-wadi for > > tomcat and not clustering-wadi. As a matter of fact, I have on my to- > > do list a task to refactor substitution group element builders for > > Tomcat, Jetty and OpenEJB so that all of them offer the same external > > structure to end-users. > > > > Here is an updated DD: > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-1.2"> > > > > > > > > org.codehaus.wadi > > wadi-webapp > > 2.0M3-SNAPSHOT > > war > > > > > > > > <-- this is the correct element name to > > use for tomcat. > > > > > > > > Thanks, > > Gianny > > > > > > On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: > > > > > I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ > > > clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. > > > even though org.apache.geronimo.configs/jetty6-clustering-builder- > > > wadi//car is running, deploying the sample application resulted in > > > an error given below: > > > > > > > > error: cvc-complex-type.2.4a: Expected elements 'context- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > cross- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ > > > web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// > > > java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here > > > > > > > > > > > > > The deployment plan I am using is: > > > > > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-1.2"> > > > > > > > > > > > > org.codehaus.wadi > > > wadi-webapp > > > 2.0M3-SNAPSHOT > > > war > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Hello Vamsi, I verified on G Jetty 2.1 with Safari... Based on your previous problem description (black boxes instead of numbered ones), I inferred that somehow your browser was not propagating a session cookie to the server. So, I decided to give a shot with FireFox and interestingly I was able to identify the problem. In the standard DD, the demo application used to declare this: org.mortbay.jetty.servlet.SessionPath /wadi This instructs Jetty to set the session cookie path to /wadi. As the demo application is deployed to /wadi-webapp, your browser or FireFox do not send to the server the cookies for the path /wadi; hence, the problem. So, I dropped the above xml fragment from the DD, tested with FireFox and deployed another snapshot: http:// snapshots.repository.codehaus.org/org/codehaus/wadi/wadi-webapp/2.0- SNAPSHOT/wadi-webapp-2.0-20080319.110523-12.war Thanks for giving it a try and your patience. Thanks, Gianny On 19/03/2008, at 8:55 PM, Vamsavardhana Reddy wrote: Gianny, I was able to get the sample application deployed and running as expected on G Tomcat 2.1. But, it still does not run correctly on G Jetty 2.1. Have you verified on G Jetty 2.1? ++Vamsi On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote: Thanks Gianny. I will try with the new DD and get back if there is any problem. ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour <[EMAIL PROTECTED]> wrote: Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2"> org.codehaus.wadi wadi-webapp 2.0M3-SNAPSHOT war <-- this is the correct element name to use for tomcat. Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: > I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ > clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. > even though org.apache.geronimo.configs/jetty6-clustering-builder- > wadi//car is running, deploying the sample application resulted in > an error given below: > > error: cvc-complex-type.2.4a: Expected elements 'context- > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ > web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// > java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here > > > The deployment plan I am using is: > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > tomcat-1.2"> > > > > org.codehaus.wadi > wadi-webapp > 2.0M3-SNAPSHOT > war > > > > > > >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Gianny, I was able to get the sample application deployed and running as expected on G Tomcat 2.1. But, it still does not run correctly on G Jetty 2.1. Have you verified on G Jetty 2.1? ++Vamsi On Tue, Mar 18, 2008 at 9:13 PM, Vamsavardhana Reddy <[EMAIL PROTECTED]> wrote: > Thanks Gianny. I will try with the new DD and get back if there is any > problem. > > ++Vamsi > > > On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour < > [EMAIL PROTECTED]> wrote: > > > Hello, > > > > This is a problem with the deployment descriptor. You name of the > > clustering substitution group element is tomcat-clustering-wadi for > > tomcat and not clustering-wadi. As a matter of fact, I have on my to- > > do list a task to refactor substitution group element builders for > > Tomcat, Jetty and OpenEJB so that all of them offer the same external > > structure to end-users. > > > > Here is an updated DD: > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2";> > > > > > > > > org.codehaus.wadi > > wadi-webapp > > 2.0M3-SNAPSHOT > > war > > > > > > > > <-- this is the correct element name to > > use for tomcat. > > > > > > > > Thanks, > > Gianny > > > > > > On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: > > > > > I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ > > > clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. > > > even though org.apache.geronimo.configs/jetty6-clustering-builder- > > > wadi//car is running, deploying the sample application resulted in > > > an error given below: > > > > > > > > error: cvc-complex-type.2.4a: Expected elements 'context- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > cross- > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ > > > web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// > > > java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// > > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here > > > > > > > > > > > > > The deployment plan I am using is: > > > > > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > > > tomcat-1.2"> > > > > > > > > > > > > org.codehaus.wadi > > > wadi-webapp > > > 2.0M3-SNAPSHOT > > > war > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Thanks Gianny. I will try with the new DD and get back if there is any problem. ++Vamsi On Tue, Mar 18, 2008 at 6:11 PM, Gianny Damour < [EMAIL PROTECTED]> wrote: > Hello, > > This is a problem with the deployment descriptor. You name of the > clustering substitution group element is tomcat-clustering-wadi for > tomcat and not clustering-wadi. As a matter of fact, I have on my to- > do list a task to refactor substitution group element builders for > Tomcat, Jetty and OpenEJB so that all of them offer the same external > structure to end-users. > > Here is an updated DD: > > > > http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2";> > > > > org.codehaus.wadi > wadi-webapp > 2.0M3-SNAPSHOT > war > > > > <-- this is the correct element name to > use for tomcat. > > > > Thanks, > Gianny > > > On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: > > > I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ > > clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. > > even though org.apache.geronimo.configs/jetty6-clustering-builder- > > wadi//car is running, deploying the sample application resulted in > > an error given below: > > > > > error: cvc-complex-type.2.4a: Expected elements 'context- > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 > > [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ > > web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ > > j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// > > java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// > > geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here > > > > > > > > The deployment plan I am using is: > > > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web/ > > tomcat-1.2"> > > > > > > > > org.codehaus.wadi > > wadi-webapp > > 2.0M3-SNAPSHOT > > war > > > > > > > > > > > > > > > >
Re: Geronimo Tomcat 2.1 clustering - application deployment problems
Hello, This is a problem with the deployment descriptor. You name of the clustering substitution group element is tomcat-clustering-wadi for tomcat and not clustering-wadi. As a matter of fact, I have on my to- do list a task to refactor substitution group element builders for Tomcat, Jetty and OpenEJB so that all of them offer the same external structure to end-users. Here is an updated DD: http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.2";> org.codehaus.wadi wadi-webapp 2.0M3-SNAPSHOT war <-- this is the correct element name to use for tomcat. Thanks, Gianny On 18/03/2008, at 9:57 PM, Vamsavardhana Reddy wrote: I have attempted the steps from http://cwiki.apache.org/GMOxDEV/ clustering-configuration-for-jetty.html with Geronimo Tomcat 2.1. even though org.apache.geronimo.configs/jetty6-clustering-builder- wadi//car is running, deploying the sample application resulted in an error given below: error: cvc-complex-type.2.4a: Expected elements 'context- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/application-2.0 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross- [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/j2ee/ web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]://geronimo.apache.org/xml/ns/ j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/naming-1.2 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 [EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/deployment-1.2 [EMAIL PROTECTED]:// java.sun.com/xml/ns/persistence' instead of '[EMAIL PROTECTED]:// geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here The deployment plan I am using is: http://geronimo.apache.org/xml/ns/j2ee/web/ tomcat-1.2"> org.codehaus.wadi wadi-webapp 2.0M3-SNAPSHOT war
