That's an approach I thought about, and am considering.

Do you have any concerns about read/write to the db being overwhelming? (We're using the status as a percentage of process completion.)

On Sep 4, 2008, at 8:24 PM, Guido Neitzer wrote:

What I normally do in these cases is store the status information in a table in the database - as I really don't want to touch my session from a DA that
is called from a thread parallel to the RR loop.

I only have to make sure to always get fresh information from the DB, that's
about it.

cug


On 04.09.08 21:17, "Josh Paul" <[EMAIL PROTECTED]> wrote:

I'm not storing the id in cookies, as this will ultimately wind up as
a web service.

I have moved the thread, which seems to have helped (as there's no new session being created). Now I just need to figure out why the 'status'
isn't being set (or read) correctly.

On Sep 4, 2008, at 5:52 PM, Chuck Hill wrote:

On Sep 4, 2008, at 5:43 PM, Josh Paul wrote:

I'm not swallowing exceptions anywhere, and if I am they're
printing to stdout.

I do think the session is locked or not checked in. I need to
investigate further.

That would give you deadlock or unlocked access, not create a new
session.

Are you storing the session ID in cookies too?


Chuck


On Sep 4, 2008, at 3:41 PM, Guido Neitzer wrote:

Only thought I have is that it might not be a good idea to fire
that DA from
a spawned thread from the RR loop. You might end up trying to
check out a
session from the session store that is already checked out.

Not sure what would cause the creation of a new session though ...
maybe
that it is throwing an exception while trying to access the old
(but locked)
session and this could create a new session.

Are you swallowing exceptions somewhere?

cug

On 04.09.08 16:33, "Josh Paul" <[EMAIL PROTECTED]> wrote:

100%.

I left out the fact that this is related to a Thread, as that's
where
the status is being created. So, I have a DA that fires the process
and another DA that checks in on it. The issue is that when
checking,
a new Session keeps getting created.

Thoughts?

On Sep 4, 2008, at 3:26 PM, Guido Neitzer wrote:

And you are sure, your session is not terminated somewhere else?

cug

On 04.09.08 15:59, "Josh Paul" <[EMAIL PROTECTED]> wrote:

I'm using WO 5.3 with a version of Wonder about 1 week old...

On Sep 4, 2008, at 2:50 PM, Guido Neitzer wrote:

On 04.09.08 15:42, "Chuck Hill" <[EMAIL PROTECTED]>
wrote:

That sort of thing should work.  Which version of WO?  There
may
have
been some related bugs in earlier versions of 5.4

As far as I know, that should work. But I always call
"existingSession()"
before I do anything else in a DA call.

cug









_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village
.net

This email sent to [EMAIL PROTECTED]


--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects










_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to