Hello Barry,

I'm not seeing any synchronization operations which are necessary whenever different threads access and change the same object. A race condition due to that might very well exhibit the same symptoms as a deadlock (which normally results from the incorrect use of synchonization). I'd say that the getters and setters for value and status ought be synchronized, using some suitable Java technique - try adding "synchronized" after the "public" modifier.

kr
Wolfgang

Barry Flower wrote:


Hi,
I am experiencing a deadlock issue that is more likely the higher the event rate in a real-time application. Does anybody know how to avoid such a deadlock but not miss processing any of the events? I have included the java class and the jess rules as an attachment. Any help regarding tools or methods to capture the internal state of the Jess engine so I can at least determine how the deadlock is occurring would be appreciated.

I am using a status slot to provide interlocking between the jess engine and the Java application that is changing the value slot of the FastStream fact.

The delay parameter for the instantiation of FastStream can be increased from zero to a point where the deadlock condition is unlikely to happen but on my machine the deadlock nearly always occurs for a delay = 0.

;                                                   name, iters, delay
(bind ?fs (new FastStream "s1"     100    0))

Cheers
Barry



*Barry Flower* | Global Head eFM Strategy & Solutions | WIB Technology*
Westpac Institutional Bank* | Level 2, Westpac Place, 275 Kent Street, Sydney, NSW 2000* T* +61 2 8254 6308 | *M* +61 439 467 971 | *E* [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
        

        
        



Please consider our environment before printing this email.

WARNING - This email and any attachments may be confidential. If received in error, please delete and inform us by return email. Because emails and attachments may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems, you must be cautious. Westpac cannot guarantee that what you receive is what we sent. If you have any doubts about the authenticity of an email by Westpac, please contact us immediately.

It is also important to check for viruses and defects before opening or using attachments. Westpac's liability is limited to resupplying any affected attachments.

This email and its attachments are not intended to constitute any form of financial advice or recommendation of, or an offer to buy or offer to sell, any security or other financial product. We recommend that you seek your own independent legal or financial advice before proceeding with any investment decision.

Westpac Institutional Bank is a division of Westpac Banking Corporation, a company registered in New South Wales in Australia under the Corporations Act 2001 (Cth). Westpac is authorised and regulated in the United Kingdom by the Financial Services Authority and is registered at Cardiff in the United Kingdom as Branch No. BR 106. Westpac operates in the United States of America as a federally chartered branch, regulated by the Office of the Comptroller of the Currency.

Westpac Banking Corporation ABN 33 007 457 141.


--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to