w for implementation differences.
--Glen
> I don't get it, the 1st sync will sync on the session - which
> I believe
> should be ok since that's will be the same session object
> each time (based
> on what scope you have - either serlvet session or
> appSession). The 2nd
I don't get it, the 1st sync will sync on the session - which I believe
should be ok since that's will be the same session object each time (based
on what scope you have - either serlvet session or appSession). The 2nd
sync will sync on something that is local (or specific) to t
> Locking the String or Object that is placed in the hashtable
> will do it
> since that is presistent across all threads - and it doesn't
> really matter
> which kind of Object it is - we just need something/anything
> to sync on.
The problem is that you want only o
Locking the String or Object that is placed in the hashtable will do it
since that is presistent across all threads - and it doesn't really matter
which kind of Object it is - we just need something/anything to sync on.
There really isn't much to say about what's happenin
ot kicked off of irc but I think the problem would be
> solved by
> something like this:
> String lockObject = null ;
> Object service = null ;
> sync (session) {
> Hashtable locks = session.get("AxisLocks");
> if ( locks == null ) session.set("AxisLoc
proach below at
least allows other services to be invoked.
-Dug
Glen - got kicked off of irc but I think the problem would be solved by
something like this:
String lockObject = null ;
Object service = null ;
sync (session) {
Hashtable locks = session.get("AxisLocks");
if ( locks == null
Glen - got kicked off of irc but I think the problem would be solved by
something like this:
String lockObject = null ;
Object service = null ;
sync (session) {
Hashtable locks = session.get("AxisLocks");
if ( locks == null ) session.set("AxisLocks", locks = new
> It looks like (according to cvs) you added the sync blocks in
> JavaProvider and its cause use some problems.
> I'm trying to understand why those sync blocks were added.
> From what I can
> tell they don't prevent multiple threads from clobbering each others
>
Glen,
It looks like (according to cvs) you added the sync blocks in
JavaProvider and its cause use some problems.
I'm trying to understand why those sync blocks were added. From what I can
tell they don't prevent multiple threads from clobbering each others
service object that&#
