Did anything ever come of this...we seem to lose data from our visit
occasionally for no apparent reason.
----- Forwarded by Christian Hall/Technology/Equifax on 09/11/2002 11:00 AM
-----
|--------+---------------------------------------------->
| | "Howard M. Lewis Ship" |
| | <[EMAIL PROTECTED]> |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | eforge.net |
| | |
| | |
| | 09/04/2002 08:26 PM |
| | |
|--------+---------------------------------------------->
>-------------------------------------------------------------------------------------------------|
|
|
| To: "Jason Owens" <[EMAIL PROTECTED]>,
|
| <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: Re: [Tapestry-developer] Component problem...
|
|
|
>-------------------------------------------------------------------------------------------------|
This sounds fishy to me. You are correct, two near-simultaneous requests
will occur in two seperate threads and operate on two different instances
of
the page -- anything short of this is a bug. There could concievably be
contention on the page recorders (those are shared between any number of
requests).
A page doesn't go back into the pool until after detach(), which is after
are PageDetachListeners have been notified.
What exception are you getting? It could be quite illuminating.
----- Original Message -----
From: "Jason Owens" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 04, 2002 7:34 PM
Subject: [Tapestry-developer] Component problem...
> Hello all,
>
> One of my components has a problem with state. The component, a
> TreeList, implements PageDetachListener to reset it's state. The parent
> page also resets its state in its own detach method. However, when two
> requests come in simultaneously (or close to it), the second one always
> ends up with an exception: a particular data member is null.
>
> It seems like the first request is modifying the component (resetting
> it) while the second one is still running through a Foreach loop on the
> same component (that is where the error occurs). This doesn't seem like
> the proper behavior. It's rather complicated, but I wondered if anyone
> had any pointers.
>
> There is only one page in the pool when the exception occurs (which
> means the requests weren't exactly at the same time), and I assume only
> one component then as well. But the two request seem to keep bumping
> into each other... I seem to remember there was some way to turn off
> the pooling to test this sort of thing, but I forgot the actual method.
>
> Any pointers appreciated, thanks.
> -Jason
>
> BTW - I'm still using Tapestry 2.0. I seriously hope I don't have to go
> through the upgrade process at this point...
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
FREE 30-DAY TRIAL! Sign up for Equifax Credit Watch(TM) today and receive
unlimited credit reports and scores, as well as protection against identity
theft with daily credit monitoring -- FREE for 30 days -- all from Equifax
-- your market leader in information management. Visit
http://www.creditalert.equifax.com today!
This message contains information from Equifax, Inc. which may be
confidential and privileged. If you are not an intended recipient, please
refrain from any disclosure, copying, distribution or use of this
information and note that such actions are prohibited. If you have
received this transmission in error, please notify by e:mail
[EMAIL PROTECTED]
-------------------------------------------------------
In remembrance
www.osdn.com/911/
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
