You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Stefan Fromm <sf...@inf.tu-dresden.de> on 2004/08/10 11:44:04 UTC
Delistment of services
Hi,
the delistment of services seems to have changed its behaviour from Slide 2.0 to Slide 2.1.
In method ExtendedStore.createObject() a new object is put into objectsCache. After executing delist() this object disappears from this cache in Slide 2.1. In Slide 2.0 it stays. More precisely the object disappears from the cache when transaction.delistResource(ExtendedStore, TMSUSPEND) was called in the delist() method.
Is there a possibility to change this behaviour back to Slide 2.0s by configuring? Has something changed with the transaction manager?
Please give me a hint what to do. I need to create objects with Slide 2.1 which is refused with an ObjectNotFoundException because the new object cannot be found in cache so it's looked up from physical place where it cannot be found, of course. I use the file based stores to store metadata and content.
Kind regards
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Delistment of services
Posted by Stefan Fromm <sf...@inf.tu-dresden.de>.
Really no problem. Took a while but gave me deep insights into Slide :)
Stefan
Am Tue, 10 Aug 2004 16:59:05 +0200 schrieb Oliver Zeigermann <ol...@zeigermann.de>:
> I saw myself forced to change it when I introduced external transactions. Actually, 2.0 had a bug or better to say inaccuracy that did not clear association with threads even after enlistment. I already explained this a bit...
>
> Sorry if this caused any inconvenience...
>
> Oliver
>
> Stefan Fromm wrote:
>> Hello Oliver,
>>
>> I've just found out what my mistake was: in Slide 2.0 one could call Structure.create() without setting SlideToken.setForceStoreEnlistment(true) before. That's why I expected the same behaviour in Slide 2.1 and assumed a bug.
>>
>> Ok, thank you for your quick reply.
>> Regards, Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Delistment of services
Posted by Oliver Zeigermann <ol...@zeigermann.de>.
I saw myself forced to change it when I introduced external
transactions. Actually, 2.0 had a bug or better to say inaccuracy that
did not clear association with threads even after enlistment. I already
explained this a bit...
Sorry if this caused any inconvenience...
Oliver
Stefan Fromm wrote:
> Hello Oliver,
>
> I've just found out what my mistake was: in Slide 2.0 one could call
> Structure.create() without setting
> SlideToken.setForceStoreEnlistment(true) before. That's why I expected
> the same behaviour in Slide 2.1 and assumed a bug.
>
> Ok, thank you for your quick reply.
> Regards, Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Delistment of services
Posted by Stefan Fromm <sf...@inf.tu-dresden.de>.
Hello Oliver,
I've just found out what my mistake was: in Slide 2.0 one could call Structure.create() without setting SlideToken.setForceStoreEnlistment(true) before. That's why I expected the same behaviour in Slide 2.1 and assumed a bug.
Ok, thank you for your quick reply.
Regards, Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Delistment of services
Posted by Oliver Zeigermann <ol...@zeigermann.de>.
Hi Stefan!
Could you explain this in a bit more detail, please? Does the object
really disappear? I'd suspect it is only no longer visisble as the cache
is no longer associated to the current thread. In this case you receive
the global entry. But this is just my suspecion. If it really
disappears, it is of course a bug and I will fix it ASAP.
Could you explain why the object can not be found when it is not in the
cache? I was wondering as all writes go through the cache and read
physical stores in any code.
So, please clarify.
Oliver
Stefan Fromm wrote:
> Hi,
>
> the delistment of services seems to have changed its behaviour from
> Slide 2.0 to Slide 2.1.
>
> In method ExtendedStore.createObject() a new object is put into
> objectsCache. After executing delist() this object disappears from this
> cache in Slide 2.1. In Slide 2.0 it stays. More precisely the object
> disappears from the cache when transaction.delistResource(ExtendedStore,
> TMSUSPEND) was called in the delist() method.
>
> Is there a possibility to change this behaviour back to Slide 2.0s by
> configuring? Has something changed with the transaction manager?
>
> Please give me a hint what to do. I need to create objects with Slide
> 2.1 which is refused with an ObjectNotFoundException because the new
> object cannot be found in cache so it's looked up from physical place
> where it cannot be found, of course. I use the file based stores to
> store metadata and content.
>
> Kind regards
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org