No exception occurs.  None.  See my earlier posting.  The issue
is that in QFJ 1.3.2, we always get a false return value for
sendToTarget().

Not the case with QFJ 1.3.1.

On Jan 23, 7:10 am, Sibir Chakraborty <[email protected]> wrote:
> Hi,
>
> QFJ 1.3.2 is a stable release. It is unlikely to have a Session persistance
> bug like this. However, in as in your case of "intermittent" exception
> thrown:
>
> 1. Session might get invalid due to several reasons
> 2. Please post a code snippet used while implementing yoir OnLogOn() event
> and
> 3. Check the quickFIX/J Configuration file. For convenience, please 
> check:http://www.quickfixj.org/quickfixj/usermanual/usage/configuration.html
>
> 4. Next, if you are using some user defined tags, please also enable
> (putting=Y at last) in these settings:
> **
> ValidateFieldsOutOfOrder=N
> ValidateFieldsHaveValues=N
> UseDataDictionary=N
> CheckCompID=N
>
> Let us know.
>
> Regards,
> Sibir
> **
>
> On Sat, Jan 23, 2010 at 5:23 AM, kodecharlie <[email protected]> wrote:
> > Every order I send out is ack'd by the broker; no exception occurs.
> > However, sendToTarget() returns false every invocation for QFJ 1.3.2.
>
> > For QFJ 1.3.1, sendToTarget() returns false only intermittently.
>
> > So, if the 1.3.2 behavior buggy, or is this considered proper
> > behavior?
>
> > Thanks.
>
> > On Jan 22, 2:31 am, Sibir Chakraborty <[email protected]> wrote:
> > > Not sure what you mean when you tell: "are
> > > acknowledged by the broker." but yet throws the Exception.
>
> > > Session.sendToTarget(...,...) takes the arguments as the valid Session
> > > established via LogOn msg and it's ack via a LogOn again.
>
> > > Please check the following:
>
> > > 1. The Session is established: You can check your code that you
> > > onLogON(SessionID) method is implemented via a Session object which is
> > > assigned the SessionID on LogON.
>
> > > AND
>
> > > 2. You are responding back via that same SessionID as an argument during
> > > Session.sendToTarget(FIXMsg,Session).
>
> > > You can send any FIX Msg supported via the FIX Dictionary you have used.
>
> > > I can post a sample code, if you require so.
>
> > > Regards,
> > > Sibir
>
> > > On Fri, Jan 22, 2010 at 7:28 AM, kodecharlie <[email protected]>
> > wrote:
> > > > After downloading and setting up QuickFixJ 1.3.2, every order I send
> > > > out via
>
> > > >  boolean Session.sendToTarget(Message message, SessionID sessionID)
> > > > throws SessionNotFound;
>
> > > > returns false.  All orders do make it to the FIX gateway, and are
> > > > acknowledged by the broker.
>
> > > > Question:  is this a bug in QuickFixJ 1.3.2?  I thought this
> > > > sendToTarget() would only
> > > > return false if the order was not immediately dispatched, ie,
> > > > internally queued for reason.
> > > > Why is this happening for *every* order?
>
> > > > Thanks.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Financial Information eXchange" group.
> > > > To post to this group, send email to [email protected].
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<fix-protocol%[email protected]>
> > <fix-protocol%[email protected]<fix-protocol%[email protected]>
>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/fix-protocol?hl=en.
>
> > --
> >  You received this message because you are subscribed to the Google Groups
> > "Financial Information eXchange" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<fix-protocol%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/fix-protocol?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Financial Information eXchange" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/fix-protocol?hl=en.

Reply via email to