RE: Session Connection pooling in Axis2 WS
Hi Paul, If my web-service is in Request/ Session scope, which means one instance for every single request. Then if my web service on its process involves creating a singleton object (e.g.: DBConnection Pooling, etc.), will it break the singleton concept, as it will create one singleton for each single request/ service object? What will be the correct way to design this? Separate them as a separate web-services, one set in 'request' session and the singleton one set in 'application' session? Thanks in advance, wen -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: January 26, 2007 7:55 AM To: axis-user@ws.apache.org Subject: Re: Session Connection pooling in Axis2 WS Session scope is simply the lifecycle of the objects and state that Axis2 manages. So if you define request, then each new request will instantiate a new service object. If you define transportsession, then Axis2 will use HTTP cookies. Each client will re-use the same service object. If you define soapsession, it will do the same thing, except using SOAP headers instead of cookies. If you define application, then you will have a single service object for all requests. It is up to you to make sure that youre object can support the right threading model for application. For request you need not worry about thread safety because each request has its own service object. Paul On 1/26/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote: > Sanjiva > > What is session scope? > > you have to define one of > scope=request > scope=transportsession > scope=soapsession > scope=application > > which one do you mean? > Josef > > -Ursprüngliche Nachricht- > Von: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 25. Januar 2007 06:29 > An: axis-user@ws.apache.org > Betreff: RE: Session Connection pooling in Axis2 WS > > > It depends on the "scope" of the service .. if its deployed in > application scope then only one instance is created. If its in session > scope then its one instance per session and so on. > > See: http://wso2.org/library/231 > > Sanjiva. > > On Wed, 2007-01-24 at 11:45 -0500, Ho, Wen Yue wrote: > > Hi, > > > > I think my question is not clear and confusing. > > Sorry, a newbie here :-) > > > > Please allow me to re-phrase my question. > > How does Axis2 handle multiple request to the webservices? > > AFAIK, Axis2 is a servlet and by default, a (single) servlet should > > be able to handle multiple HTTP requests. > > For each incoming request session, will axis (servlet) instantiate > > just one instance of the websrvice class for multiple requests? > > Or it will instantiate one webservice object for each request? > > > > Your assistance will be highly appreciated. > > Thank you. > > > > > > > > > > > > __ > > From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] > > Sent: January 23, 2007 2:26 PM > > To: axis-user@ws.apache.org > > Subject: Session Connection pooling in Axis2 WS > > > > > > > > Hi, > > > > I have a legacy system that provides an API to access the system > > thru their own Session object. > > I need to pool this session objects within my web services developed > > using Axis2. > > > > Correct me if I'm wrong. > > AFAIK, Axis2 by default will make one thread per request to the web > > service. > > I think this means singleton class won't work, since one thread will > > instantiate one singleton. > > Any advice on how to do this? > > > > Thanks in advance. > > > > > > > > NOTICE OF CONFIDENTIALITY > > This communication including any information transmitted with it is > > intended only for the use of the addressees and is confidential. > > If you are not an intended recipient or responsible for delivering > > the message to an intended recipient, any review, disclosure, > > conversion to hard copy, dissemination, reproduction or other use of > > any part of this communication is strictly prohibited, as is the > > taking or omitting of any action in reliance upon this communication. > > If you receive this communication in error or without authorization > > please notify us immediately by return e-mail or otherwise and > > permanently delete the entire communication from any computer, disk > > drive, or other storage medium. > > > > If the above disclaimer is not properly readable, it can be found at > > www.td.com/legal > > > > AVERTISSEMENT DE CONFIDENTIALITE
Re: Session Connection pooling in Axis2 WS
Josef have you set your client options to setManageSession(true); ? Paul On 1/29/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote: Hi Paul, thank you, but what are the various threading models one needs to care about, among selecting one of the scope's below. i.e. I have a missbehaving scope=sopasession. I have reported several times that in scope=soapsession client#2 overrides the ServiceGroupContextID which was given to client#1 on it's first request. This overriede makes the already running, not-timed-out client#1 fail with "unknownServiceGroupContextID" I assumed that it has to do with threadsafety. So what threading model shall I use in scope=soapsession to avoid the override of the ServiceGroupContextID? And how do I manage that in my clinet and/or server code or one of the many configuration xml files to achive that? Josef -Ursprüngliche Nachricht- Von: Paul Fremantle [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 26. Januar 2007 13:55 An: axis-user@ws.apache.org Betreff: Re: Session Connection pooling in Axis2 WS Session scope is simply the lifecycle of the objects and state that Axis2 manages. So if you define request, then each new request will instantiate a new service object. If you define transportsession, then Axis2 will use HTTP cookies. Each client will re-use the same service object. If you define soapsession, it will do the same thing, except using SOAP headers instead of cookies. If you define application, then you will have a single service object for all requests. It is up to you to make sure that youre object can support the right threading model for application. For request you need not worry about thread safety because each request has its own service object. Paul On 1/26/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote: > Sanjiva > > What is session scope? > > you have to define one of > scope=request > scope=transportsession > scope=soapsession > scope=application > > which one do you mean? > Josef > > -Ursprüngliche Nachricht- > Von: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 25. Januar 2007 06:29 > An: axis-user@ws.apache.org > Betreff: RE: Session Connection pooling in Axis2 WS > > > It depends on the "scope" of the service .. if its deployed in > application scope then only one instance is created. If its in session > scope then its one instance per session and so on. > > See: http://wso2.org/library/231 > > Sanjiva. > > On Wed, 2007-01-24 at 11:45 -0500, Ho, Wen Yue wrote: > > Hi, > > > > I think my question is not clear and confusing. > > Sorry, a newbie here :-) > > > > Please allow me to re-phrase my question. > > How does Axis2 handle multiple request to the webservices? > > AFAIK, Axis2 is a servlet and by default, a (single) servlet should be > > able to handle multiple HTTP requests. > > For each incoming request session, will axis (servlet) instantiate > > just one instance of the websrvice class for multiple requests? > > Or it will instantiate one webservice object for each request? > > > > Your assistance will be highly appreciated. > > Thank you. > > > > > > > > > > __ > > From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] > > Sent: January 23, 2007 2:26 PM > > To: axis-user@ws.apache.org > > Subject: Session Connection pooling in Axis2 WS > > > > > > > > Hi, > > > > I have a legacy system that provides an API to access the system thru > > their own Session object. > > I need to pool this session objects within my web services developed > > using Axis2. > > > > Correct me if I'm wrong. > > AFAIK, Axis2 by default will make one thread per request to the web > > service. > > I think this means singleton class won't work, since one thread will > > instantiate one singleton. > > Any advice on how to do this? > > > > Thanks in advance. > > > > > > > > NOTICE OF CONFIDENTIALITY > > This communication including any information transmitted with it is > > intended only for the use of the addressees and is confidential. > > If you are not an intended recipient or responsible for delivering > > the message to an intended recipient, any review, disclosure, > > conversion to hard copy, dissemination, reproduction or other use > > of any part of this communication is strictly prohibited, as is the > > taking or omitting of any action in reliance upon this communication. > > If you receive this communication in error or without authorization > > please notify us immediately b
Re: Session Connection pooling in Axis2 WS
Session scope is simply the lifecycle of the objects and state that Axis2 manages. So if you define request, then each new request will instantiate a new service object. If you define transportsession, then Axis2 will use HTTP cookies. Each client will re-use the same service object. If you define soapsession, it will do the same thing, except using SOAP headers instead of cookies. If you define application, then you will have a single service object for all requests. It is up to you to make sure that youre object can support the right threading model for application. For request you need not worry about thread safety because each request has its own service object. Paul On 1/26/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote: Sanjiva What is session scope? you have to define one of scope=request scope=transportsession scope=soapsession scope=application which one do you mean? Josef -Ursprüngliche Nachricht- Von: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 25. Januar 2007 06:29 An: axis-user@ws.apache.org Betreff: RE: Session Connection pooling in Axis2 WS It depends on the "scope" of the service .. if its deployed in application scope then only one instance is created. If its in session scope then its one instance per session and so on. See: http://wso2.org/library/231 Sanjiva. On Wed, 2007-01-24 at 11:45 -0500, Ho, Wen Yue wrote: > Hi, > > I think my question is not clear and confusing. > Sorry, a newbie here :-) > > Please allow me to re-phrase my question. > How does Axis2 handle multiple request to the webservices? > AFAIK, Axis2 is a servlet and by default, a (single) servlet should be > able to handle multiple HTTP requests. > For each incoming request session, will axis (servlet) instantiate > just one instance of the websrvice class for multiple requests? > Or it will instantiate one webservice object for each request? > > Your assistance will be highly appreciated. > Thank you. > > > > > __ > From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] > Sent: January 23, 2007 2:26 PM > To: axis-user@ws.apache.org > Subject: Session Connection pooling in Axis2 WS > > > > Hi, > > I have a legacy system that provides an API to access the system thru > their own Session object. > I need to pool this session objects within my web services developed > using Axis2. > > Correct me if I'm wrong. > AFAIK, Axis2 by default will make one thread per request to the web > service. > I think this means singleton class won't work, since one thread will > instantiate one singleton. > Any advice on how to do this? > > Thanks in advance. > > > > NOTICE OF CONFIDENTIALITY > This communication including any information transmitted with it is > intended only for the use of the addressees and is confidential. > If you are not an intended recipient or responsible for delivering > the message to an intended recipient, any review, disclosure, > conversion to hard copy, dissemination, reproduction or other use > of any part of this communication is strictly prohibited, as is the > taking or omitting of any action in reliance upon this communication. > If you receive this communication in error or without authorization > please notify us immediately by return e-mail or otherwise and > permanently delete the entire communication from any computer, > disk drive, or other storage medium. > > If the above disclaimer is not properly readable, it can be found at > www.td.com/legal > > AVERTISSEMENT DE CONFIDENTIALITE > Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement > aux destinataires susmentionnés, est confidentiel. Si vous > n'êtes pas le destinataire prévu ou un agent responsable de la > livraison de ce courriel, tout examen, divulgation, copie, impression, > reproduction, distribution, ou autre utilisation d'une partie de ce > courriel est strictement interdit de même que toute intervention ou > abstraction à cet égard. Si vous avez reçu ce message par erreur ou > sans autorisation, veuillez en aviser immédiatement l'expéditeur par > retour de courriel ou par un autre moyen et supprimer immédiatement > cette communication entière de tout système électronique. > > Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous > pouvez le consulter à www.td.com/francais/legale -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http
RE: Session Connection pooling in Axis2 WS
It depends on the "scope" of the service .. if its deployed in application scope then only one instance is created. If its in session scope then its one instance per session and so on. See: http://wso2.org/library/231 Sanjiva. On Wed, 2007-01-24 at 11:45 -0500, Ho, Wen Yue wrote: > Hi, > > I think my question is not clear and confusing. > Sorry, a newbie here :-) > > Please allow me to re-phrase my question. > How does Axis2 handle multiple request to the webservices? > AFAIK, Axis2 is a servlet and by default, a (single) servlet should be > able to handle multiple HTTP requests. > For each incoming request session, will axis (servlet) instantiate > just one instance of the websrvice class for multiple requests? > Or it will instantiate one webservice object for each request? > > Your assistance will be highly appreciated. > Thank you. > > > > > __ > From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] > Sent: January 23, 2007 2:26 PM > To: axis-user@ws.apache.org > Subject: Session Connection pooling in Axis2 WS > > > > Hi, > > I have a legacy system that provides an API to access the system thru > their own Session object. > I need to pool this session objects within my web services developed > using Axis2. > > Correct me if I'm wrong. > AFAIK, Axis2 by default will make one thread per request to the web > service. > I think this means singleton class won't work, since one thread will > instantiate one singleton. > Any advice on how to do this? > > Thanks in advance. > > > > NOTICE OF CONFIDENTIALITY > This communication including any information transmitted with it is > intended only for the use of the addressees and is confidential. > If you are not an intended recipient or responsible for delivering > the message to an intended recipient, any review, disclosure, > conversion to hard copy, dissemination, reproduction or other use > of any part of this communication is strictly prohibited, as is the > taking or omitting of any action in reliance upon this communication. > If you receive this communication in error or without authorization > please notify us immediately by return e-mail or otherwise and > permanently delete the entire communication from any computer, > disk drive, or other storage medium. > > If the above disclaimer is not properly readable, it can be found at > www.td.com/legal > > AVERTISSEMENT DE CONFIDENTIALITE > Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement > aux destinataires susmentionnés, est confidentiel. Si vous > n’êtes pas le destinataire prévu ou un agent responsable de la > livraison de ce courriel, tout examen, divulgation, copie, impression, > reproduction, distribution, ou autre utilisation d’une partie de ce > courriel est strictement interdit de même que toute intervention ou > abstraction à cet égard. Si vous avez reçu ce message par erreur ou > sans autorisation, veuillez en aviser immédiatement l’expéditeur par > retour de courriel ou par un autre moyen et supprimer immédiatement > cette communication entière de tout système électronique. > > Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous > pouvez le consulter à www.td.com/francais/legale -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Session Connection pooling in Axis2 WS
Hi, I think my question is not clear and confusing. Sorry, a newbie here :-) Please allow me to re-phrase my question. How does Axis2 handle multiple request to the webservices? AFAIK, Axis2 is a servlet and by default, a (single) servlet should be able to handle multiple HTTP requests. For each incoming request session, will axis (servlet) instantiate just one instance of the websrvice class for multiple requests? Or it will instantiate one webservice object for each request? Your assistance will be highly appreciated. Thank you. From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] Sent: January 23, 2007 2:26 PM To: axis-user@ws.apache.org Subject: Session Connection pooling in Axis2 WS Hi, I have a legacy system that provides an API to access the system thru their own Session object. I need to pool this session objects within my web services developed using Axis2. Correct me if I'm wrong. AFAIK, Axis2 by default will make one thread per request to the web service. I think this means singleton class won't work, since one thread will instantiate one singleton. Any advice on how to do this? Thanks in advance. NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous n'êtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation d'une partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement l'expéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
Re: Session Connection pooling in Axis2 WS
Hi Ho, Wen Yue ; You can solve the problem by deploying the service in application scope. Then there will be only one instance of the serviceimpl class. Thanks Deepal > Hi, > I have a legacy system that provides an API to access the system thru > their own Session object. > I need to pool this session objects within my web services developed > using Axis2. > Correct me if I'm wrong. > AFAIK, Axis2 by default will make one thread per request to the web > service. > I think this means singleton class won't work, since one thread will > instantiate one singleton. > Any advice on how to do this? > Thanks in advance. > > >NOTICE OF CONFIDENTIALITY >This communication including any information transmitted with it is >intended only for the use of the addressees and is confidential. >If you are not an intended recipient or responsible for delivering >the message to an intended recipient, any review, disclosure, >conversion to hard copy, dissemination, reproduction or other use >of any part of this communication is strictly prohibited, as is the >taking or omitting of any action in reliance upon this communication. >If you receive this communication in error or without authorization >please notify us immediately by return e-mail or otherwise and >permanently delete the entire communication from any computer, >disk drive, or other storage medium. > >If the above disclaimer is not properly readable, it can be found at >www.td.com/legal > >AVERTISSEMENT DE CONFIDENTIALITE >Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement >aux destinataires susmentionnés, est confidentiel. Si vous >n’êtes pas le destinataire prévu ou un agent responsable de la >livraison de ce courriel, tout examen, divulgation, copie, impression, >reproduction, distribution, ou autre utilisation d’une partie de ce >courriel est strictement interdit de même que toute intervention ou >abstraction à cet égard. Si vous avez reçu ce message par erreur ou >sans autorisation, veuillez en aviser immédiatement l’expéditeur par >retour de courriel ou par un autre moyen et supprimer immédiatement >cette communication entière de tout système électronique. > >Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous >pouvez le consulter à www.td.com/francais/legale > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
