Yes!
I have a simple example that shows my problem.
It is linked to my previous deseperation (remember?) as well.
It is one client, one session bean, two entity beans, two detail objects.
Client calls SB to add EB 1
Client calls SB to add EB 2
Client calls SB to modify("old") EB 2
Client calls SB to read EB 2 (*)
Client calls SB to modify("new") EB 2
Client calls SB to read EB 2 (*) ==> "old" data is shown but "new" is in the
DB
Why ?
Because EB 2 access(fbpk + remote-method) EB 1 in (*). The cache of EB 1
touch the one of EB 2 somewhere.
With min-capacity and max-capacity set to 1 everything is OK. The
Passivation clean the cache.
What do I do next ?
I could add it to jbosstest so you can have a look (please, it's driving me
mad for 2 months now)
TIA.
Vincent.
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de marc
> fleury
> Envoy� : mercredi 4 juillet 2001 21:09
> � : [EMAIL PROTECTED]
> Objet : RE: [JBoss-dev] container-cache-conf 1/1
>
>
> honestly this doesn't really help, too complex a business scenario, bean a
> calls b calls c calls d calls e calls f then something goes wrong...
>
> can you minimize the repro case? like something simpler?
>
> marcf
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of
> |Vincent Harcq
> |Sent: Wednesday, July 04, 2001 1:01 PM
> |To: [EMAIL PROTECTED]
> |Subject: RE: [JBoss-dev] container-cache-conf 1/1
> |
> |
> |Hi,
> |
> |Test1:
> |
> |I have a servlet calling a sfsb calling a slsb calling a entity bean A on
> |which I run a setX(). This setX() runs himself another setY()
> on another
> |entity bean B.
> |>From my web page I change the value on the attribute. I can see
> |it is saved
> |in the db.
> |But the getX() of my entity bean always return the old value.
> |
> |Now I start another web browser, I access the same entity bean.
> I see the
> |new value.
> |
> |Now I come back to the first browser, I access the same entity
> |bean. Bingo.
> |It is the good value.
> |
> |Test 2:
> |Now I set the cache to 1/1. Everything works OK.
> |
> |Test 3:
> |If I remove the link with the other entity bean everything is OK.
> |
> |Vincent.
> |PS: I can post a ejb jar and a client. . . In fact I will have to
> |write the
> |client, give some time.
> |
> |
> |> Hey Vincent,
> |>
> |> > A simple question,
> |> > In JBOSS config file on <container-cache-conf>, I define
> |> > <min-capacity>1</min-capacity> and
> |> > <max-capacity>1</max-capacity>, instead
> |> > of 10 / 100 (for example).
> |> > And if 1/1 solve a problem that appear on 10/100, do I have
> |> > found a problem
> |> > in the cache ?
> |>
> |> Maybe, and maybe not :) Can you expand on this ?
> |>
> |> > I have seen a lot of discussion on the cache these last
> |> > weeks, I did a clean
> |> > check out to test some problems I have, they did not disappear.
> |> > If I could help by providing some examples, I will be please
> to do so.
> |>
> |> Please do. Just post them on the dev-list, I guess it supports
> |attachments
> |>
> |> Simon
> |>
> |
> |
> |_______________________________________________
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
