strange behaviour with direct actions / woadaptor
strange behaviour with direct actions / woadaptor
- Subject: strange behaviour with direct actions / woadaptor
- From: Cornelius Jaeger <email@hidden>
- Date: Fri, 19 Dec 2003 14:02:53 +0100
hi list,
i'm getting strange behavior with a direct action.
nothing fancy, a client app sends a request, gets authenticated, and if
ok, i grab values from the url to update the client information stored
on the server.
i wrote a test client that hammers the server with varying intervals.
strangely. no matter what the interval 20 s or 100 ms when i access the
instances directly on their port, all is good. if i go via the
webserver the values are updated every 60 seconds. exactly, every 60
seconds. sounds like a timer (timeout) somewhere.
just for good context.
a. this happens even if there is only 1 instance running
b. there is definitely no session being created
c. there are no wotimers running (that i implemented anyway).
d. this is an isolated editingcontext (not session().default etc.).
e. time time fetch lag is 1 (second presumably)
f. wocaching is disabled (this seemed like a good viable thing to do)
the only information i'm getting is that when i deploy on my
testmachine everything works.
panther server it doesn't. strange is that the transaction count in
JavaMonitor doens't increase.
so i'm getting the same reply all the time, the app doesn't seem to get
the request at all.
so, the only thing i can come up with, due to lack of understanding, is
that there is something with the adaptor.
and, as a foot note, can someone explain what wocaching actually does?
thx for any help.
cornelius
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.