I would not worry about this, especially on solaris.
You're first test was invalid. You ran on an idle system. The OS is going
to give the Java process whatever amount of the CPU it needs to complete its
work. On an idle system, there is nothing competing for the CPU. In this
scenario, a very
I would not worry about this, especially on solaris.
You're first test was invalid. You ran on an idle system. The OS is going
to give the Java process whatever amount of the CPU it needs to complete its
work. On an idle system, there is nothing competing for the CPU. In this
scenario, a very
I have a similar situation, and am kicking around JMS/MDBs.
I'm interested in the feedback you get on this question.
On Wed, Feb 11, 2009 at 8:45 PM, Dan Seaver wrote:
>
> Is there any recommended "Best Practice" for instantiating and accessing a
> StatelfulKnowledgeSession in a J2EE environmen
gt; date, or use the PseudoClock, setting it to the appropriate time, before
> inserting each event. There are semantic differences in both approaches, so
> you need to look at the whole of your scenario to decide what is more
> appropriate to you.
>
>Ok, can someone help tran
Edson,
I'm very interested in fusion. I'm looking at it using it for fraud
detection in a credit card authorization system.
Quick question - can the time of facts be asserted? I'm thinking around how
to handle testing, and business requirements of batch authorizations. (where
3rd parties send i
