[kepler-dev] fireAtCurrentTime issue in DEDirector

ian.brown@hsbcib.com ian.brown at hsbcib.com
Thu Jan 10 01:24:52 PST 2008


Hi,
        a while back I had some issues firing the DEDirector from a number 
of threads and the answer was to wrap the firing in a change request. At 
the time Edward Lee explained that this was necessary because we were 
using fireAt rather than fireAtCurrentTime. He also made a few changes to 
the DEDirector to support the change request mechanism.
>From this, I changed our code so that the asynchronous fireAt() calls are 
wrapped in a change request and the fireAtCurrentTime() ones are not. That 
now works pretty well ... but I am occasionally seeing problems with 
fireAtCurrentTime(). See the following stack trace:

ptolemy.kernel.util.IllegalActionException: Attempt to queue an event in 
the pas
t: Current time is 1916.1180000000002 while event time is 1915.915
  in .market_tracker_wide.OrderManager.MaintainOrders
        at 
ptolemy.domains.de.kernel.DEDirector._enqueueEvent(DEDirector.java:12
37)
        at 
ptolemy.domains.de.kernel.DEDirector.fireAt(DEDirector.java:625)
        at 
ptolemy.domains.de.kernel.DEDirector.fireAtCurrentTime(DEDirector.jav
a:649)
        at 
com.hsbc.IMTActors.fix.MaintainOrders.fillNotification(MaintainOrders
.java:436)
        at 
com.hsbc.IMTActors.fix.FixApplication.executionReport(FixApplication.
java:250)
        at 
com.hsbc.IMTActors.fix.FixApplication.access$100(FixApplication.java:
53)
        at 
com.hsbc.IMTActors.fix.FixApplication$MessageProcessor.run(FixApplica
tion.java:148)
        at 
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
        at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
ad.java:273)
        at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
java:183)
        at 
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:173)
        at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)

        at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)

        at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

Does anyone have any idea why this can happen and what I can do it fix it. 
Would wrapping it in a change request help? It seems a heavyweight 
solution - I don't care when the DEDirector fires .. I just want to 
trigger a firing at the next possible opportunity.

Thanks,

Ian

ps: Edward, we're still working on what we talked about at the end of 
November. Things here move really slowly in December because of the year 
end accounting but that's all done now so we should be able to move ahead 
in the next few weeks.


************************************************************
HSBC Bank plc may be solicited in the course of its placement efforts for 
a new issue, by investment clients of the firm for whom the Bank as a firm 
already provides other services. It may equally decide to allocate to its 
own proprietary book or with an associate of HSBC Group. This represents a 
potential conflict of interest. HSBC Bank plc has internal arrangements 
designed to ensure that the firm would give unbiased and full advice to 
the corporate finance client about the valuation and pricing of the 
offering as well as internal systems, controls and procedures to identify 
and manage conflicts of interest.

HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority.
************************************************************



-----------------------------------------
SAVE PAPER - THINK BEFORE YOU PRINT!

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-dev/attachments/20080110/85f12d60/attachment-0001.htm


More information about the Kepler-dev mailing list