RE: Re: Delayed Assignments in multi-server environment?

This is a multi-part message in MIME format...

------------=_1289225370-30467-7831
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Sasa, thanks for the quick reply and the info regarding the new location=
 of the project(s) & forum(S).

Hopefully you can answer just one more question pertaing to my situation.

If I have a single shark-based JSP webapp, hitting a single shark DB, deplo=
yed to multiple instances of tomcat (spread out over several servers each w=
ith it's own JVM) which are all sitting behind a load balancer, could cache=
ing be causing the this "delay" issue where other users (on different tomca=
ts/servers/JVMs) cannot see new assignments? If so, how much does the cache=
 impact performance if I have to turn it off?

My assignment manager class is basically a clone of the standard assignment=
 manager that comes with shark, with a few modifications to lookup workflow=
 variables in the assignments which dynamically detemine the participant. I=
 don't think that there is anything special in this code that would contrib=
ute to a delay in assignments.=20

In addition, I have not seen this "delay" issue in my TEST or QA environmen=
ts which each only have a single tomcat/server/JVM.

Thanks again for the help!


Todd Kofford
[email protected]
University of Kansas - IT

-----Original Message-----
From: Sasa Bojanic [mailto:[email protected]]=20
Sent: Monday, November 08, 2010 4:07 AM
To: [email protected]
Subject: [shark] Re: Delayed Assignments in multi-server environment?

Hi Todd,

First of all, to tell everyone from the OW2 Shark's mailing list that we mo=
ved Shark and JaWE projects to SourceForge (http://sourceforge.net/projects=
/sharkwf and http://sourceforge.net/projects/jawe). Soon, there will be 3.3=
-1 release of Shark/JaWE, and this will be the last release based on XPDL1.=
 The next releases will conform to XPDL2 (at a beginning only the automatic=
 transformation of XPDL1 files to XPDL2 files according to new schema, and =
in the future we will support more and more things from XPDL2, including BP=
MN for JaWE).
There is already a forum where you can post the questions for JaWE on Sourc=
eForge, and soon there will be the one for Shark as well, so in the future =
please post your questions to these forums.

Now, back to your question. If you are using Shark embedded into the single=
 application on the server (like your JSP application), and no other applic=
ation is using shark on top of the same database, caches should not be the =
issue. It could be an issue with your implementation of AssignmentManager i=
nterface, do you have some special implementation that delays creation of a=
ssignments based on some configuration or properties from XPDL?

On the other hand, if you are using more than one application on top of Sha=
rk (using the same shark database), then the caches has to be turned-off (t=
his is the case when using both JSP and SwingAdmin application in parallel).

To turn-off the caches, in the configuration files for both applications ca=
che entries should be commented (for CacheManagerClassName entry) or set to=
 zero (for DODS' cache entries).

#CacheManagerClassName=3Dorg.enhydra.shark.caching.LRUCacheMgr

DatabaseManager.defaults.cache.maxCacheSize=3D0
DatabaseManager.defaults.cache.maxSimpleCacheSize=3D0
DatabaseManager.defaults.cache.maxComplexCacheSize=3D0
DatabaseManager.defaults.cache.maxMultiJoinCacheSize=3D0


Greetings,
Sasa.

On 05-Nov-10 20:33, Todd Kofford wrote:
> I am using Together Workflow Server 3.1-2 in a multi-server=20
> environment with a JSP client front end similar to the JSP client=20
> example. I really hope that someone can help me with this, because=20
> it's a production problem that I need to resolve pretty quickly.
>
> I am having users report that sometimes their workflow assignments are=20
> being delayed for up to a day. For example user, Joe, creates a new=20
> workflow process, accepts the activity and then completes the=20
> assignment. In our XPDL workflow, the process is supposed to generate=20
> an activity for user Nancy next for approval. However, Nancy doesn't=20
> see her new assignment until the next day, even though she tries=20
> multiple times to refresh her list of assignments (i.e.,=20
> sConn.getResourceObject().get_sequence_work_item(0);)
>
> Has anyone seen this before? I also see this when work is done in=20
> either the JSP client webapp or admin swing app, that the other=20
> application cannot see what was done until I restart the admin app or=20
> tomcat for the JSP client webapp. Is this a cache issue?
>
> Thanks in advance (if anyone responds)
>
> Todd Kofford
> [email protected]


------------=_1289225370-30467-7831
Content-Type: text/plain; charset="UTF-8"; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: quoted-printable


--
You receive this message as a subscriber of the [email protected] mailing lis=
t.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=3Dhelp
OW2 mailing lists service home page: http://www.ow2.org/wws

------------=_1289225370-30467-7831--