You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Trustin Lee <tr...@gmail.com> on 2005/10/06 18:30:50 UTC
[ApacheDS] Fwd: Re: About JDBM transaction support
Though it is a unfortunate news for us ...
---------- Forwarded message ----------
From: Alex Boisvert <bo...@intalio.com>
Date: 2005. 10. 7 오전 1:23
Subject: Re: [NEWSENDER] - About JDBM transaction support - Message is from
an unknown sender
To: Trustin Lee <tr...@gmail.com>
Cc: JDBM General <jd...@lists.sourceforge.net>
Trustin,
Currently JDBM doesn't support multiple outstanding (concurrent)
transactions. If you need this, you have to either write an additional
layer on top of JDBM or serialize access to the RecordManager for each
of your transactions.
alex
Trustin Lee wrote:
> Hi Alex,
>
> We've developed JDBM backend for Apache Directory Server long ago, and
> now we're trying to support multiple transactions that can be
> committed or rolled back indepdently from each other. But I couldn't
> find any interfaces like 'Transaction' that can be passed to the
> RecordManager yet like I do with BDB JE. Can I know if I can perform
> more than one transactions at once and those transactions can be
> rolled back or committed individually? If I can, can I know how?
>
> Thanks in advance,
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
--
what we call human nature is actually human habit
--
http://gleamynode.net/
Re: [ApacheDS] Fwd: Re: About JDBM transaction support
Posted by Marc Boorshtein <mb...@gmail.com>.
just a thought on JE, what if the partition type was just in a seperate
project site (ie sourceforge), then its not an issue (though a bit harder to
distribute).
marc
On 10/6/05, Alex Karasulu <ao...@bellsouth.net> wrote:
>
> Trustin Lee wrote:
>
> > Though it is a unfortunate news for us ...
>
> Yeah I expected this :(.
>
> > Currently JDBM doesn't support multiple outstanding (concurrent)
> > transactions. If you need this, you have to either write an additional
> > layer on top of JDBM or serialize access to the RecordManager for each
> > of your transactions.
> >
> > alex
> >
> Serializing access to the RecordManager for writes will kill write
> performance. Heh, not that write performance is anything spectacular at
> the moment. Using JE would have made a massive difference here.
>
> We have no choice but to write an additional layer on top of JDBM. If we
> do this I would like the resultant layer around JDBM to appear as much
> as possible like JE WRT transaction handling. This is because I would
> like it to be really easy to implement the JE partition by reusing some
> of the JDBM partition machinery: I already started tinkering. Eventually
> (because of licensing issues) we can offer the better JE partition as a
> separate plugable download from safehaus.org <http://safehaus.org> or
> sourceforge.net <http://sourceforge.net>. We
> still need JDBM though here at Directory.
>
> >
> > Trustin Lee wrote:
> >
> > > Hi Alex,
> > >
> > > We've developed JDBM backend for Apache Directory Server long ago, and
> > > now we're trying to support multiple transactions that can be
> > > committed or rolled back indepdently from each other. But I couldn't
> > > find any interfaces like 'Transaction' that can be passed to the
> > > RecordManager yet like I do with BDB JE. Can I know if I can perform
> > > more than one transactions at once and those transactions can be
> > > rolled back or committed individually? If I can, can I know how?
> > >
> > > Thanks in advance,
> > > Trustin
>
>
>
Re: [ApacheDS] Fwd: Re: About JDBM transaction support
Posted by Alex Karasulu <ao...@bellsouth.net>.
Trustin Lee wrote:
> Though it is a unfortunate news for us ...
Yeah I expected this :(.
> Currently JDBM doesn't support multiple outstanding (concurrent)
> transactions. If you need this, you have to either write an additional
> layer on top of JDBM or serialize access to the RecordManager for each
> of your transactions.
>
> alex
>
Serializing access to the RecordManager for writes will kill write
performance. Heh, not that write performance is anything spectacular at
the moment. Using JE would have made a massive difference here.
We have no choice but to write an additional layer on top of JDBM. If we
do this I would like the resultant layer around JDBM to appear as much
as possible like JE WRT transaction handling. This is because I would
like it to be really easy to implement the JE partition by reusing some
of the JDBM partition machinery: I already started tinkering. Eventually
(because of licensing issues) we can offer the better JE partition as a
separate plugable download from safehaus.org or sourceforge.net. We
still need JDBM though here at Directory.
>
> Trustin Lee wrote:
>
> > Hi Alex,
> >
> > We've developed JDBM backend for Apache Directory Server long ago, and
> > now we're trying to support multiple transactions that can be
> > committed or rolled back indepdently from each other. But I couldn't
> > find any interfaces like 'Transaction' that can be passed to the
> > RecordManager yet like I do with BDB JE. Can I know if I can perform
> > more than one transactions at once and those transactions can be
> > rolled back or committed individually? If I can, can I know how?
> >
> > Thanks in advance,
> > Trustin