Re: orion not replicating session state - relatively urgent
Yes, all the objects implement Serializable. We have a test application that simply updates a single counter (an Integer object). We don't have serialVersionUID, however. Is this required? Michael N. Christoff Developer, Eldan Software, Ltd. Toronto, Canada www.eldan.com - Original Message - From: "Duffey, Kevin" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Thursday, April 26, 2001 5:35 PM Subject: RE: orion not replicating session state - relatively urgent > Did you make sure all objects that are stored in HttpSession, including any > object fields of objects all implement Serializable as well as provide the > static long serailVersionUID = ; in every class file? > > > > -Original Message- > > From: Mike N. Christoff [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, April 26, 2001 1:25 PM > > To: Orion-Interest > > Subject: Re: orion not replicating session state - relatively urgent > > > > > > Thanks for the advice, however after adding this our session > > data is still > > being lost when the server we initially connected to goes > > down. We are > > currently testing with two servers, both of which belong to > > the same cluster > > island. What still boggles us here is that the sample > > applications (like > > servlets/SessionServlet) work perfectly. We even moved our > > web application > > into the orion\default-web-app directory and in this > > directory they also > > work. > > > > In summary: only the default web application is replicating > > state properly. > > Our other applications must be missing a setting somewhere > > that specifies > > that their session data should be shared with servers in the > > cluster island > > as is the case with the default application. > > > > > > > > Michael N. Christoff > > Developer, Eldan Software, Ltd. > > Toronto, Canada > > www.eldan.com > > > > - Original Message - > > From: "Rafael Alvarez" <[EMAIL PROTECTED]> > > To: "Orion-Interest" <[EMAIL PROTECTED]> > > Sent: Thursday, April 26, 2001 2:55 PM > > Subject: Re: orion not replicating session state - relatively urgent > > > > > > > Hello Mike, > > > > > > Try using this orion-web.xml. > > > The persistence-path is not specified by default, so you need to > > > declare it. This is the place where sessions are persisted across > > > server restarts. > > > > > > > > deployment-version="1.4.5" > > > persistence-path="session" > > > > > > > > > > > > > Thursday, April 26, 2001, 12:20:39 PM, you wrote: > > > > > > >
Re: orion not replicating session state - relatively urgent
And all the stuff you shove up the session are Serializable? Doublecheck that. If they are Serializable, your problem sounds like a bug. Johan - Original Message - From: "Mike N. Christoff" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Thursday, April 26, 2001 10:25 PM Subject: Re: orion not replicating session state - relatively urgent > Thanks for the advice, however after adding this our session data is still > being lost when the server we initially connected to goes down. We are > currently testing with two servers, both of which belong to the same cluster > island. What still boggles us here is that the sample applications (like > servlets/SessionServlet) work perfectly. We even moved our web application > into the orion\default-web-app directory and in this directory they also > work. > > In summary: only the default web application is replicating state properly. > Our other applications must be missing a setting somewhere that specifies > that their session data should be shared with servers in the cluster island > as is the case with the default application. > > > > Michael N. Christoff > Developer, Eldan Software, Ltd. > Toronto, Canada > www.eldan.com > > - Original Message - > From: "Rafael Alvarez" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Thursday, April 26, 2001 2:55 PM > Subject: Re: orion not replicating session state - relatively urgent > > > > Hello Mike, > > > > Try using this orion-web.xml. > > The persistence-path is not specified by default, so you need to > > declare it. This is the place where sessions are persisted across > > server restarts. > > > > > deployment-version="1.4.5" > > persistence-path="session" > > > > > > > > > Thursday, April 26, 2001, 12:20:39 PM, you wrote: > > > >
Re[2]: orion not replicating session state - relatively urgent
Hello Mike, Did you follow the instructions in the http-clustering how to document? And, as far as I can understant (haven't tried clustering yet) you need to explicity pass the jsessionid in the url. -- Best regards, Rafaelmailto:[EMAIL PROTECTED]
Re: orion not replicating session state - relatively urgent
Thanks for the advice, however after adding this our session data is still being lost when the server we initially connected to goes down. We are currently testing with two servers, both of which belong to the same cluster island. What still boggles us here is that the sample applications (like servlets/SessionServlet) work perfectly. We even moved our web application into the orion\default-web-app directory and in this directory they also work. In summary: only the default web application is replicating state properly. Our other applications must be missing a setting somewhere that specifies that their session data should be shared with servers in the cluster island as is the case with the default application. Michael N. Christoff Developer, Eldan Software, Ltd. Toronto, Canada www.eldan.com - Original Message - From: "Rafael Alvarez" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Thursday, April 26, 2001 2:55 PM Subject: Re: orion not replicating session state - relatively urgent > Hello Mike, > > Try using this orion-web.xml. > The persistence-path is not specified by default, so you need to > declare it. This is the place where sessions are persisted across > server restarts. > > deployment-version="1.4.5" > persistence-path="session" > > > > > Thursday, April 26, 2001, 12:20:39 PM, you wrote: >
RE: orion not replicating session state - relatively urgent
Did you make sure all objects that are stored in HttpSession, including any object fields of objects all implement Serializable as well as provide the static long serailVersionUID = ; in every class file? > -Original Message- > From: Mike N. Christoff [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 26, 2001 1:25 PM > To: Orion-Interest > Subject: Re: orion not replicating session state - relatively urgent > > > Thanks for the advice, however after adding this our session > data is still > being lost when the server we initially connected to goes > down. We are > currently testing with two servers, both of which belong to > the same cluster > island. What still boggles us here is that the sample > applications (like > servlets/SessionServlet) work perfectly. We even moved our > web application > into the orion\default-web-app directory and in this > directory they also > work. > > In summary: only the default web application is replicating > state properly. > Our other applications must be missing a setting somewhere > that specifies > that their session data should be shared with servers in the > cluster island > as is the case with the default application. > > > > Michael N. Christoff > Developer, Eldan Software, Ltd. > Toronto, Canada > www.eldan.com > > - Original Message - > From: "Rafael Alvarez" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Thursday, April 26, 2001 2:55 PM > Subject: Re: orion not replicating session state - relatively urgent > > > > Hello Mike, > > > > Try using this orion-web.xml. > > The persistence-path is not specified by default, so you need to > > declare it. This is the place where sessions are persisted across > > server restarts. > > > > > deployment-version="1.4.5" > > persistence-path="session" > > > > > > > > > Thursday, April 26, 2001, 12:20:39 PM, you wrote: > > > >
Re: orion not replicating session state - relatively urgent
Thanks for the advice, however after adding this our session data is still being lost when the server we initially connected to goes down. We are currently testing with two servers, both of which belong to the same cluster island. What still boggles us here is that the sample applications (like servlets/SessionServlet) work perfectly. We even moved our web application into the orion\default-web-app directory and in this directory they also work. In summary: only the default web application is replicating state properly. Our other applications must be missing a setting somewhere that specifies that their session data should be shared with servers in the cluster island as is the case with the default application. Michael N. Christoff Developer, Eldan Software, Ltd. Toronto, Canada www.eldan.com - Original Message - From: "Rafael Alvarez" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Thursday, April 26, 2001 2:55 PM Subject: Re: orion not replicating session state - relatively urgent > Hello Mike, > > Try using this orion-web.xml. > The persistence-path is not specified by default, so you need to > declare it. This is the place where sessions are persisted across > server restarts. > > deployment-version="1.4.5" > persistence-path="session" > > > > > Thursday, April 26, 2001, 12:20:39 PM, you wrote: >
Re: orion not replicating session state - relatively urgent
Hello Mike, Try using this orion-web.xml. The persistence-path is not specified by default, so you need to declare it. This is the place where sessions are persisted across server restarts. Thursday, April 26, 2001, 12:20:39 PM, you wrote: MNC> subject: orion not replicating session information MNC> Hello. We have been experimenting with clustering orion servers and were initially successful. We started the load balancer, got our servers registered with it, and tested it using the MNC> servlet/SessionServlet program. Everything worked as it should. We modified the SessionServlet app to print the ip of the server it was running from. We had it count to 5, then we shut down MNC> the server, clicked refresh and the servlet went up to 6 on a different server. Perfect. MNC> The problem is that when we moved the session servlet to one of our other application directories, it no longer updated to 6, it started at 1 again. Why does orion replicate state only for MNC> applications in the default-web-app directory and not anywhere else? We tried adding to the orion-web.xml file (in the application-deployment directory) of our other apps and MNC> it still doesn't work. Here is a snip of our default-web-site.xml file: MNC> MNC> MNC> MNC> MNC> MNC> MNC> MNC> MNC> We have installed orion at a client site and need to get clustering working correctly within the next week. Anyone else successfully set up clustering. Any tips? See anything we're missing? MNC> We will provide any info you require. MNC> Thanks for your time. MNC> Michael N. Christoff MNC> Developer, Eldan Software, Ltd. MNC> Toronto, Canada -- Best regards, Rafaelmailto:[EMAIL PROTECTED]
orion not replicating session state - relatively urgent
subject: orion not replicating session information Hello. We have been experimenting with clustering orion servers and were initially successful. We started the load balancer, got our servers registered with it, and tested it using the servlet/SessionServlet program. Everything worked as it should. We modified the SessionServlet app to print the ip of the server it was running from. We had it count to 5, then we shut down the server, clicked refresh and the servlet went up to 6 on a different server. Perfect. The problem is that when we moved the session servlet to one of our other application directories, it no longer updated to 6, it started at 1 again. Why does orion replicate state only for applications in the default-web-app directory and not anywhere else? We tried adding to the orion-web.xml file (in the application-deployment directory) of our other apps and it still doesn't work. Here is a snip of our default-web-site.xml file: We have installed orion at a client site and need to get clustering working correctly within the next week. Anyone else successfully set up clustering. Any tips? See anything we're missing? We will provide any info you require. Thanks for your time. Michael N. ChristoffDeveloper, Eldan Software, Ltd.Toronto, Canada
