Re: Delayed Assignments in mulit-server environment?

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

------------=_1289210811-30467-7789
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Todd,

First of all, to tell everyone from the OW2 Shark's mailing list that we 
moved 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 BPMN for JaWE).
There is already a forum where you can post the questions for JaWE on 
SourceForge, 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 application 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 interface, do you have some special implementation 
that delays creation of assignments based on some configuration or 
properties from XPDL?

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

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

#CacheManagerClassName=org.enhydra.shark.caching.LRUCacheMgr

DatabaseManager.defaults.cache.maxCacheSize=0
DatabaseManager.defaults.cache.maxSimpleCacheSize=0
DatabaseManager.defaults.cache.maxComplexCacheSize=0
DatabaseManager.defaults.cache.maxMultiJoinCacheSize=0


Greetings,
Sasa.

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


------------=_1289210811-30467-7789
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

------------=_1289210811-30467-7789--