[JDO] JDO and application server.
Hi, We are developing an application server (a uPortal channel) and we use OJB-JDO in order to implement data persistence. Everything works fine when the application is accessed by one user. But as soon as the application is concurrently accessed by two (or more) users, multiple instances are created and then, it seems that persistent managers (i.e. PersistenceManager instances) are not bound to the correct user. Anybody already encountered this problem? Thanks, Alexandre -- Alexandre BOISSEAU Université de Rennes1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JDO] JDO and application server.
On 04/05/10 9:58, Alexandre BOISSEAU [EMAIL PROTECTED]
wrote:
Hi,
We are developing an application server (a uPortal channel) and we use
OJB-JDO in order to implement data persistence.
Everything works fine when the application is accessed by one user. But
as soon as the application is concurrently accessed by two (or more)
users, multiple instances are created and then, it seems that persistent
managers (i.e. PersistenceManager instances) are not bound to the
correct user.
I think you shouldn't keep an instance of persistence manager for each
user. If you want you may keep a persistence manager factory instead.
I usually create persistence managers, do the job I want with them and
then close them in the end (try - catch - finally {if (pm!= null)
pm.close();}).
Pedro Salgado
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JDO] JDO and application server.
Thanks Pedro,
Yes, Currently, I use a single persistance manager for each user. I
create it in the constructor and close it after the session is done.br
I will try to create a PM for each job. br
Alexandre.
Pedro Salgado wrote:
On 04/05/10 9:58, Alexandre BOISSEAU [EMAIL PROTECTED]
wrote:
Hi,
We are developing an application server (a uPortal channel) and we use
OJB-JDO in order to implement data persistence.
Everything works fine when the application is accessed by one user. But
as soon as the application is concurrently accessed by two (or more)
users, multiple instances are created and then, it seems that persistent
managers (i.e. PersistenceManager instances) are not bound to the
correct user.
I think you shouldn't keep an instance of persistence manager for each
user. If you want you may keep a persistence manager factory instead.
I usually create persistence managers, do the job I want with them and
then close them in the end (try - catch - finally {if (pm!= null)
pm.close();}).
Pedro Salgado
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Alexandre BOISSEAU
Université de Rennes1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
