quickfix-developers — QuickFIX developers forum

RE: [Quickfix-developers] Re: [Quickfix-users] how to send response to a client

[James C. D. <jc...@co...>]

Brian,
This is a great example of how all the differences in business requirements
from implementation to implementation cannot be completely covered by a
standard protocol. This is also a good real world example for those who are
new to FIX struggling with the map between the protocol and business needs
and how that gap is bridged. 

Would you mind commenting on the general reaction of a new counterparty to
your system when they are presented with custom field values (at the
application level)? Is it an education process as to the value the custom
values bring to the implementation?

Thanks,
Jim

-----Original Message-----
From: Brian Erst [mailto:azz...@ya...] 
Sent: Friday, June 03, 2005 9:39 AM
To: James C. Downs; azz...@ya...; 'rohan joel pais';
qui...@li...;
qui...@li...
Subject: RE: [Quickfix-developers] Re: [Quickfix-users] how to send response
to a client

James -

The problem occurs when you have a fairly sophisticated order management
system that acts as more than just a proxy pass-through to an exchange.
Here's an example of an issue that (so far) has best been resolved through
additional OrdStatus values.

The system I work on has connections to 12 different futures exchanges.
We attempt to deliver a consistent interface for all these exchanges, even
when any particular underlying exchange may not support the superset of
functionality across the many exchanges. For instance, not all of the
exchange systems support stop orders (even though the use of such orders is
widespread throughout the industry). For those exchanges that do not support
stop orders, we have created a process that simulates stop order processing
within our order management system.
Essentially, we hold the orders, listen to the price feed and submit the
orders once the trigger price has been touched.

For these orders, they may NEVER reach the exchange system (price is not
matched). We need a consistent way of telling our users when orders have
been accepted into our system for management, when (if) they have been
diverted to our internal stop processing ssytem, when the orders get elected
into the market and when the order actually reaches the market.

The simplest way to handle this (by far) was to add a few additional
OrdStatus/ExecType values. We define "NEW" as being accepted by OUR
application and add three new values ('l' for locally working stops, 'e' for
stop order election and 'x' for at the exchange).

In this way, our clients know where an order is at all times. Just as
importantly, our helpdesk knows where that order is as well. If the client
experiences a communications failure and needs to work their orders, they
should still have some idea as to what their current market risk is while
talking with our helpdesk to manage their open orders.

- Brian Erst
Thynk Software, Inc.

--- "James C. Downs" <jc...@co...> wrote:

> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ:
> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> Brian,
> I'm curious why in your case the OrdStatus = "NEW" was not sufficient 
> to indicate that the order was accepted by the exchange and in the 
> market? What exchange/venue was most problematic for you in this 
> regard?
> 
> Thanks,
> Jim
> 
> -----Original Message-----
> From: qui...@li...
> [mailto:qui...@li...] On Behalf Of 
> Brian Erst
> Sent: Friday, June 03, 2005 7:45 AM
> To: rohan joel pais; qui...@li...;
> qui...@li...
> Subject: [Quickfix-developers] Re: [Quickfix-users] how to send 
> response to a client
> 
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ:
> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> I have a very similar application and I eventually decided that the 
> "better"
> way was to add additional ExecType/OrdStatus values and use those to 
> differentiate between "my application has received the order"
> and "the exchange has received the order".
> 
> In my particular case, I use Pending New (OrdStatus='0') to indicate 
> that my app received and databased the order. I created a new 
> OrdStatus ('x'
> for at
> the eXchange) to indicate that the order had been received by the 
> exchange.
> 
> FIX hasn't fully come to terms with third-party order management 
> systems acting as a bridge between clients and exchanges. Hopefully 
> they will start looking at that (if they haven't already) as most of 
> the ISVs out there are now adding some sort of FIX interface to their 
> order management systems.
> 
> - Brian Erst
> Thynk Software, Inc.
> 
> --- rohan joel pais <roh...@re...> wrote:
> 
> >   
> > Hi all,
> >        I need some help in developing a new project. It is like
> this
> > -  My application will act like a passer, which recieves fix
> messages
> > from the client and then converts it into another format and sends
> it
> > to the exchange.
> > But my problem here is i want to tell the client that i have
> recieved
> > his order, without sending him the execution report. so i am asking
> 
> > whether i can build my own response message and send it to the
> client.
> > 
> > with regards
> > rohan pais
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own 
> Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own 
> Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
> 

Re: [Quickfix-developers] Re: [Quickfix-users] how to send response to a client

[Brian E. <azz...@ya...>]

Caleb -

That is exactly our issue. We could be even more fine-grained than we
are, but we attempted to minimize the number of extensions we were
making to the protocol. We felt that adding just the three new extended
field values provided enough information for our clients to know the
true state of their order without causing them to have to do a lot of
coding to support our non-standard values.

We could easily have used another 4-5 statuses, but the net value to
our clients was limited.

- Brian Erst
Thynk Software, Inc.

--- Caleb Epstein <cal...@gm...> wrote:

> On 6/3/05, James C. Downs <jc...@co...> wrote:
> 
> > I'm curious why in your case the OrdStatus = "NEW" was not
> sufficient to
> > indicate that the order was accepted by the exchange and in the
> market? What
> > exchange/venue was most problematic for you in this regard?
> 
> I think the answer depends on how fine-grained you want to make the
> information you pass back to clients of a system.  Especially if
> messages take more than one hop before they go out the door. 
> Consider
> for example this system:
> 
> Client app -> FIX router -> ECNs
> 
> If the FIX router were purely a message-passing application, it would
> just rely on the ECNs to generate all of the execution reports and
> wouldn't generate any of its own.  But what if the Client App wants
> to
> distinguish between a message that:
> 
> * It has created, but not yet sent to the router
> * Has been sent to the router (or we think it has)
> * Has been acknowledged by the router as having been received (but
> hasn't been sent to the ECN yet)
> * Has been sent by the router to the ECN (or the router thinks it
> has)
> 
> And so on.  Different systems may want to have some sort of feedback
> for any/all of these events, so I can see a need for finer-grained
> status codes.  As with routing FIX in general though, the more hops
> you have, the more fields or codes you need if you want to capture
> all
> of the this information.  This can turn into a mess pretty fast.
> 
> -- 
> Caleb Epstein
> caleb dot epstein at gmail dot com
> 

RE: [Quickfix-developers] Re: [Quickfix-users] how to send response to a client

[Brian E. <azz...@ya...>]

James -

The problem occurs when you have a fairly sophisticated order
management system that acts as more than just a proxy pass-through to
an exchange. Here's an example of an issue that (so far) has best been
resolved through additional OrdStatus values.

The system I work on has connections to 12 different futures exchanges.
We attempt to deliver a consistent interface for all these exchanges,
even when any particular underlying exchange may not support the
superset of functionality across the many exchanges. For instance, not
all of the exchange systems support stop orders (even though the use of
such orders is widespread throughout the industry). For those exchanges
that do not support stop orders, we have created a process that
simulates stop order processing within our order management system.
Essentially, we hold the orders, listen to the price feed and submit
the orders once the trigger price has been touched.

For these orders, they may NEVER reach the exchange system (price is
not matched). We need a consistent way of telling our users when orders
have been accepted into our system for management, when (if) they have
been diverted to our internal stop processing ssytem, when the orders
get elected into the market and when the order actually reaches the
market.

The simplest way to handle this (by far) was to add a few additional
OrdStatus/ExecType values. We define "NEW" as being accepted by OUR
application and add three new values ('l' for locally working stops,
'e' for stop order election and 'x' for at the exchange).

In this way, our clients know where an order is at all times. Just as
importantly, our helpdesk knows where that order is as well. If the
client experiences a communications failure and needs to work their
orders, they should still have some idea as to what their current
market risk is while talking with our helpdesk to manage their open
orders.

- Brian Erst
Thynk Software, Inc.

--- "James C. Downs" <jc...@co...> wrote:

> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ:
> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> Brian,
> I'm curious why in your case the OrdStatus = "NEW" was not sufficient
> to
> indicate that the order was accepted by the exchange and in the
> market? What
> exchange/venue was most problematic for you in this regard?
> 
> Thanks,
> Jim 
> 
> -----Original Message-----
> From: qui...@li...
> [mailto:qui...@li...] On Behalf Of
> Brian
> Erst
> Sent: Friday, June 03, 2005 7:45 AM
> To: rohan joel pais; qui...@li...;
> qui...@li...
> Subject: [Quickfix-developers] Re: [Quickfix-users] how to send
> response to
> a client
> 
> QuickFIX Documentation:
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ:
> http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
> 
> I have a very similar application and I eventually decided that the
> "better"
> way was to add additional ExecType/OrdStatus values and use those to
> differentiate between "my application has received the order"
> and "the exchange has received the order".
> 
> In my particular case, I use Pending New (OrdStatus='0') to indicate
> that my
> app received and databased the order. I created a new OrdStatus ('x'
> for at
> the eXchange) to indicate that the order had been received by the
> exchange.
> 
> FIX hasn't fully come to terms with third-party order management
> systems
> acting as a bridge between clients and exchanges. Hopefully they will
> start
> looking at that (if they haven't already) as most of the ISVs out
> there are
> now adding some sort of FIX interface to their order management
> systems.
> 
> - Brian Erst
> Thynk Software, Inc.
> 
> --- rohan joel pais <roh...@re...> wrote:
> 
> >   
> > Hi all,
> >        I need some help in developing a new project. It is like
> this
> > -  My application will act like a passer, which recieves fix
> messages 
> > from the client and then converts it into another format and sends
> it 
> > to the exchange.
> > But my problem here is i want to tell the client that i have
> recieved 
> > his order, without sending him the execution report. so i am asking
> 
> > whether i can build my own response message and send it to the
> client.
> > 
> > with regards
> > rohan pais
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using
> Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using
> Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
> 

Re: [Quickfix-developers] Re: [Quickfix-users] how to send response to a client

[Caleb E. <cal...@gm...>]

On 6/3/05, James C. Downs <jc...@co...> wrote:

> I'm curious why in your case the OrdStatus =3D "NEW" was not sufficient t=
o
> indicate that the order was accepted by the exchange and in the market? W=
hat
> exchange/venue was most problematic for you in this regard?

I think the answer depends on how fine-grained you want to make the
information you pass back to clients of a system.  Especially if
messages take more than one hop before they go out the door.  Consider
for example this system:

Client app -> FIX router -> ECNs

If the FIX router were purely a message-passing application, it would
just rely on the ECNs to generate all of the execution reports and
wouldn't generate any of its own.  But what if the Client App wants to
distinguish between a message that:

* It has created, but not yet sent to the router
* Has been sent to the router (or we think it has)
* Has been acknowledged by the router as having been received (but
hasn't been sent to the ECN yet)
* Has been sent by the router to the ECN (or the router thinks it has)

And so on.  Different systems may want to have some sort of feedback
for any/all of these events, so I can see a need for finer-grained
status codes.  As with routing FIX in general though, the more hops
you have, the more fields or codes you need if you want to capture all
of the this information.  This can turn into a mess pretty fast.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

RE: [Quickfix-developers] Re: [Quickfix-users] how to send response to a client

[James C. D. <jc...@co...>]

Brian,
I'm curious why in your case the OrdStatus = "NEW" was not sufficient to
indicate that the order was accepted by the exchange and in the market? What
exchange/venue was most problematic for you in this regard?

Thanks,
Jim 

-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of Brian
Erst
Sent: Friday, June 03, 2005 7:45 AM
To: rohan joel pais; qui...@li...;
qui...@li...
Subject: [Quickfix-developers] Re: [Quickfix-users] how to send response to
a client

QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
QuickFIX Support: http://www.quickfixengine.org/services.html

I have a very similar application and I eventually decided that the "better"
way was to add additional ExecType/OrdStatus values and use those to
differentiate between "my application has received the order"
and "the exchange has received the order".

In my particular case, I use Pending New (OrdStatus='0') to indicate that my
app received and databased the order. I created a new OrdStatus ('x' for at
the eXchange) to indicate that the order had been received by the exchange.

FIX hasn't fully come to terms with third-party order management systems
acting as a bridge between clients and exchanges. Hopefully they will start
looking at that (if they haven't already) as most of the ISVs out there are
now adding some sort of FIX interface to their order management systems.

- Brian Erst
Thynk Software, Inc.

--- rohan joel pais <roh...@re...> wrote:

>   
> Hi all,
>        I need some help in developing a new project. It is like this
> -  My application will act like a passer, which recieves fix messages 
> from the client and then converts it into another format and sends it 
> to the exchange.
> But my problem here is i want to tell the client that i have recieved 
> his order, without sending him the execution report. so i am asking 
> whether i can build my own response message and send it to the client.
> 
> with regards
> rohan pais
> 



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] regarding Mysql

[Andrew M. <an...@nm...>]

If you go to /src/sql in quickfix you'll find scripts to create the needed 
tables.

-Andrew


On Fri, 3 Jun 2005, rohan joel pais wrote:

> 
Hi all,
        Can Any body send me the details of Mysql implementation, i need the implementation detail to maintain a database for my quickfix project.
     with regards
                                rohan pais

[Quickfix-developers] Re: [Quickfix-users] how to send response to a client

[Brian E. <azz...@ya...>]

I have a very similar application and I eventually decided that the
"better" way was to add additional ExecType/OrdStatus values and use
those to differentiate between "my application has received the order"
and "the exchange has received the order".

In my particular case, I use Pending New (OrdStatus='0') to indicate
that my app received and databased the order. I created a new OrdStatus
('x' for at the eXchange) to indicate that the order had been received
by the exchange.

FIX hasn't fully come to terms with third-party order management
systems acting as a bridge between clients and exchanges. Hopefully
they will start looking at that (if they haven't already) as most of
the ISVs out there are now adding some sort of FIX interface to their
order management systems.

- Brian Erst
Thynk Software, Inc.

--- rohan joel pais <roh...@re...> wrote:

>   
> Hi all,
>        I need some help in developing a new project. It is like this
> -  My application will act like a passer, which recieves fix messages
> from the client and then converts it into another format and sends it
> to the exchange.
> But my problem here is i want to tell the client that i have recieved
> his order, without sending him the execution report. so i am asking
> whether i can build my own response message and send it to the
> client.
> 
> with regards
> rohan pais
> 

[Quickfix-developers] Re: Quickfix-developers digest, Vol 1 #781 - 1 msg

[Michael L. <mly...@gm...>]

Alvin, you can retreive the session at the onCreate callback using the
static SessionLookup function. After you retreive the session you can
do a logoff on the session and this will prevent the session from
logging on at all.
-Michael

On 6/2/05, qui...@li...
<qui...@li...> wrote:
> Send Quickfix-developers mailing list submissions to
>         qui...@li...
>=20
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> or, via email, send a message with subject or body 'help' to
>         qui...@li...
>=20
> You can reach the person managing the list at
>         qui...@li...
>=20
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Quickfix-developers digest..."
>=20
>=20
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/i=
ndex.html
> QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ
> QuickFIX Support: http://www.quickfixengine.org/services.html
>=20
>=20
>=20
> Today's Topics:
>=20
>    1. Session Java object (Alvin Wang)
>=20
> --__--__--
>=20
> Message: 1
> To: QuickFix <qui...@li...>
> Cc: or...@qu...
> From: Alvin Wang <AW...@FF...>
> Date: Thu, 2 Jun 2005 14:31:35 -0400
> Subject: [Quickfix-developers] Session Java object
>=20
> This is a multipart message in MIME format.
>=20
> --=3D_alternative 0065C4E485257014_=3D
> Content-Type: text/plain; charset=3D"us-ascii"
> Content-Transfer-Encoding: 7bit
>=20
> Hi,
>=20
> It seems there is only one way to create a Session object in Java:
> public static native Session lookupSession(SessionID sessionID);
>=20
> But if the session is not completely built up yet (for example, the
> sequence numbers cannot be agreed on and counterparty sends logout messag=
e
> in response my logon message), lookupSession will return null.  Therefore=
, I cannot use the following messages to try
> to check the status and adjust SeqNum....
>   public native boolean isEnabled();
>   public native boolean sentLogon();
>   public native boolean sentLogout();
>   public native boolean receivedLogon();
>   public native boolean isLoggedOn();
>   public native void reset() throws IOException;
>   public native void setNextSenderMsgSeqNum(int int0) throws IOException;
>   public native void setNextTargetMsgSeqNum(int int0) throws IOException;
>=20
> So I wonder how to check the status and adjust SeqNum without a session
> object being created succesfully?
>=20
>=20
>=20
> BTW, It seems that a logout message does not invoke fromAdmin callback:
> public void fromAdmin(Message message, SessionID sessionID)
>=20
> But the logon message invokes toAdmin callback.
> I wonder if there is a bug?
>=20
>=20
> Thanks a lot!
> Alvin
>=20
> **********************************************************************
> This e-mail message is intended solely for the use of the addressee. The =
message
>  may contain information that is privileged and confidential.  Disclosure=
 to
> anyone other than the intended recipient is prohibited. If you are not th=
e
> intended recipient, please do not disseminate, distribute or copy this
> communication, by e-mail or otherwise. Instead, please notify us immediat=
ely by
> return e-mail (including the original message with your reply) and then d=
elete
> and discard all copies of the message.
> We have taken precautions to minimize the risk of transmitting software v=
iruses
>  but nevertheless advise you to carry out your own virus checks on any
> attachment to  this  message.  We  accept  no  liability  for any loss or=
 damage
>  caused by software viruses.
> **********************************************************************
>=20
> --=3D_alternative 0065C4E485257014_=3D
> Content-Type: text/html; charset=3D"us-ascii"
> Content-Transfer-Encoding: 7bit
>=20
>=20
> <br><font size=3D2 face=3D"sans-serif">Hi,</font>
> <br>
> <br><font size=3D2 face=3D"sans-serif">It seems there is only one way to =
create a Session object in Java:</font>
> <br><font size=3D2 face=3D"sans-serif"><b>public static native Session lo=
okupSession(SessionID sessionID);</b></font>
> <br>
> <br><font size=3D2 face=3D"sans-serif">But if the session is not complete=
ly built up yet (for example, the sequence numbers cannot be agreed on and =
counterparty sends logout message in response my logon message), <b>lookupS=
ession</b> will return null. &nbsp;Therefore, I cannot use the following me=
ssages to try to check the status and adjust SeqNum....</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native boolean isEna=
bled();</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native boolean sentL=
ogon();</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native boolean sentL=
ogout();</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native boolean recei=
vedLogon();</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native boolean isLog=
gedOn();</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native void reset() =
throws IOException;</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native void setNextS=
enderMsgSeqNum(int int0) throws IOException;</font>
> <br><font size=3D2 face=3D"sans-serif">&nbsp; public native void setNextT=
argetMsgSeqNum(int int0) throws IOException;</font>
> <br>
> <br><font size=3D2 face=3D"sans-serif">So I wonder how to check the statu=
s and adjust SeqNum without a session object being created succesfully?</fo=
nt>
> <br>
> <br>
> <br>
> <br><font size=3D2 face=3D"sans-serif">BTW, It seems that a logout messag=
e does not invoke fromAdmin callback:</font><font size=3D3 face=3D"Times Ne=
w Roman"> </font><font size=3D2 face=3D"sans-serif"><br>
> public void fromAdmin(Message message, SessionID sessionID) &nbsp;</font>=
<font size=3D3 face=3D"Times New Roman"> <br>
> </font><font size=3D2 face=3D"sans-serif"><br>
> But the logon message invokes toAdmin callback. </font>
> <br><font size=3D2 face=3D"sans-serif">I wonder if there is a bug? </font=
>
> <br>
> <br>
> <br><font size=3D2 face=3D"sans-serif">Thanks a lot!</font><font size=3D3=
 face=3D"Times New Roman"> </font>
> <br><font size=3D3 face=3D"Times New Roman">Alvin</font>
> <br>
> **********************************************************************
> This e-mail message is intended solely for the use of the addressee. The =
message
>  may contain information that is privileged and confidential.  Disclosure=
 to
> anyone other than the intended recipient is prohibited. If you are not th=
e
> intended recipient, please do not disseminate, distribute or copy this
> communication, by e-mail or otherwise. Instead, please notify us immediat=
ely by
> return e-mail (including the original message with your reply) and then d=
elete
> and discard all copies of the message.
> We have taken precautions to minimize the risk of transmitting software v=
iruses
>  but nevertheless advise you to carry out your own virus checks on any
> attachment to  this  message.  We  accept  no  liability  for any loss or=
 damage
>  caused by software viruses.
> **********************************************************************
>=20
> --=3D_alternative 0065C4E485257014_=3D--
>=20
>=20
>=20
> --__--__--
>=20
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>=20
>=20
> End of Quickfix-developers Digest
>

[Quickfix-developers] how to send response to a client

[rohan j. p. <roh...@re...>]

 =A0=0AHi all,=0A       I need some help in developing a new project. It is=
 like this -  My application will act like a passer, which recieves fix mes=
sages from the client and then converts it into another format and sends it=
 to the exchange.=0ABut my problem here is i want to tell the client that i=
 have recieved his order, without sending him the execution report. so i am=
 asking whether i can build my own response message and send it to the clie=
nt.=0A=0Awith regards=0Arohan pais=0A

[Quickfix-developers] how to send response to a client

[rohan j. p. <roh...@re...>]

 =A0=0AHi all,=0A       I need some help in developing a new project. It is=
 like this -  My application will act like a passer, which recieves fix mes=
sages from the client and then converts it into another format and sends it=
 to the exchange.=0ABut my problem here is i want to tell the client that i=
 have recieved his order, without sending him the execution report. so i am=
 asking whether i can build my own response message and send it to the clie=
nt.=0A=0Awith regards=0Arohan pais=0A

[Quickfix-developers] regarding Mysql

[rohan j. p. <roh...@re...>]

 =A0=0AHi all,=0A       Can Any body send me the details of Mysql implement=
ation, i need the implementation detail to maintain a database for my quick=
fix project.=0A    with regards=0A                               rohan pais

[Quickfix-developers] Session Java object

[Alvin W. <AW...@FF...>]

Hi,

It seems there is only one way to create a Session object in Java:
public static native Session lookupSession(SessionID sessionID);

But if the session is not completely built up yet (for example, the 
sequence numbers cannot be agreed on and counterparty sends logout message 
in response my logon message), lookupSession will return null.  Therefore, I cannot use the following messages to try 
to check the status and adjust SeqNum....
  public native boolean isEnabled();
  public native boolean sentLogon();
  public native boolean sentLogout();
  public native boolean receivedLogon();
  public native boolean isLoggedOn();
  public native void reset() throws IOException;
  public native void setNextSenderMsgSeqNum(int int0) throws IOException;
  public native void setNextTargetMsgSeqNum(int int0) throws IOException;

So I wonder how to check the status and adjust SeqNum without a session 
object being created succesfully?



BTW, It seems that a logout message does not invoke fromAdmin callback: 
public void fromAdmin(Message message, SessionID sessionID)   

But the logon message invokes toAdmin callback. 
I wonder if there is a bug? 


Thanks a lot! 
Alvin

**********************************************************************
This e-mail message is intended solely for the use of the addressee. The message
 may contain information that is privileged and confidential.  Disclosure to
anyone other than the intended recipient is prohibited. If you are not the
intended recipient, please do not disseminate, distribute or copy this
communication, by e-mail or otherwise. Instead, please notify us immediately by
return e-mail (including the original message with your reply) and then delete
and discard all copies of the message.
We have taken precautions to minimize the risk of transmitting software viruses
 but nevertheless advise you to carry out your own virus checks on any
attachment to  this  message.  We  accept  no  liability  for any loss or damage
 caused by software viruses.
**********************************************************************

Re: [Quickfix-developers] vs2005

[Richard P. <pro...@gm...>]

SGkgQW5keSwKCk5vdCBzdXJlIGlmIHRoaXMgcGVydGFpbnMgdG8geW91ciBzaXR1YXRpb24gYnV0
IGhlcmUgaXMgYW4gZXhjZXJwdAp0YWtlbiBmcm9tIHRoZSBsaW5rIGJlbG93OgoKaHR0cDovL3d3
dy5ld2Vlay5jb20vYXJ0aWNsZTIvMCwxNzU5LDE4MjAyMjUsMDAuYXNwCgoiQXQgaXNzdWUgaXMg
dGhlIG5vdGlvbiBvZiBicmVha2luZyBhcHBsaWNhdGlvbnMuIE1pY3Jvc29mdCBoYXMKaWRlbnRp
ZmllZCBzaXR1YXRpb25zIHdoZXJlIGFwcGxpY2F0aW9ucyB3cml0dGVuIHRvIHRoZSAuTmV0IEZy
YW1ld29yawoxLjEgYnJlYWsgd2hlbiBydW4gYWdhaW5zdCB0aGUgLk5ldCBGcmFtZXdvcmsgMi4w
LiBUaGUgaXNzdWVzIGFyb3NlCndpdGggdGhlIHJlbGVhc2Ugb2YgQmV0YSAyIG9mIFZpc3VhbCBT
dHVkaW8gMjAwNSwiCgpBcyBhIHNpZGUgbm90ZSwgYW55b25lIGNhbiBvYnRhaW4gYSBmcmVlIGNv
cHkgb2YgVlMgMjAwNSBiZXRhIGZvcgp0ZXN0aW5nIHB1cnBvc2VzIGF0OgpodHRwOi8vbXNkbi5t
aWNyb3NvZnQuY29tL2dldHRoZWJldGFzL2NvdW50cnkvCk9yIGlmIHlvdSBoYXZlIE1TRE4sIGkg
YmVsaWV2ZSB5b3Ugd2lsbCBnZXQgYSBmcmVlIGNvcHkgd2l0aCB5b3VyIGp1bmUgc2hpcG1lbnQu
CgotUmljaAoKPiBUbzogUXVpY2tGaXgKPiBTdWJqZWN0OiBbUXVpY2tmaXgtZGV2ZWxvcGVyc10g
dnMyMDA1Cj4gCj4gIAo+ICAKPiAKPiBXaGVuIHNlbmRpbmcgYSBuZXcgb3JkZXIgdXNpbmcgdGhl
IC5uZXQgZGxsczsgIEkgYW0gZ2V0dGluZyBhIG1lc3NhZ2UKPiByZWplY3RlZCByZXR1cm4gc3Rh
dGluZyB0aGF0IHJlcXVpcmVkIGZpZWxkIDYgaXMgbWlzc2luZy4gIEZpZWxkIDYgaXMgbm90Cj4g
cmVxdWlyZWQgb3IgZXZlbiBhIHBhcnQgb2YgYSBOZXcgT3JkZXIgliBTaW5nbGUuICBBbm90aGVy
IGRldmVsb3BlciBpbiB0aGUKPiBvZmZpY2UgdXNpbmcgLk5FVCAyMDAzIGFuZCB0aGUgc2FtZSBk
bGxzIGlzIG5vdCBoYXZpbmcgdGhpcyBwcm9ibGVtLiAgSXMKPiB0aGlzIGEgcHJvYmxlbSB3aXRo
IHRoZSAuTkVUIDIwMDUgYmV0YT8gIEkgdGhvdWdodCBJJ2QgY2hlY2sgdG8gc2VlIGlmCj4gYW55
b25lIGVsc2UgaXMgaGF2aW5nIHNpbWlsYXIgcHJvYmxlbXMgYmVmb3JlIEkgZ28gdGhyb3VnaCB0
aGUgcHJvY2VzcyBvZgo+IHVuaW5zdGFsbGluZyAyMDA1IGJldGEgYW5kIHJlaW5zdGFsbGluZyAy
MDAzLiAKPiAKPiAgIAo+IAo+ICAgCj4gCj4gVGhhbmsgeW91LCAKPiAKPiAgIAo+IAo+IEFuZHkg
Cj4gCj4K

RE: [Quickfix-developers] vs2005

[James C. D. <jc...@co...>]

Andy,
Do all the unit and acceptance tests run and pass when the assemblies are
built using VS 2005 beta?
Jim

  _____  

From: qui...@li...
[mailto:qui...@li...] On Behalf Of Dave
Linaker
Sent: Thursday, June 02, 2005 6:42 AM
To: an...@rh...; 'QuickFix'
Subject: RE: [Quickfix-developers] vs2005


Hi Andy,
 
6 is a required field in the ExecutionReport (i.e. the response to the
NewOrderSingle). Is the rejection definitely in relation to the order?
 
Which version of FIX are you using? Do you have a tag 372 in the reject
message? If so, what is the value?
 
Are you using the same DataDictionary as the other developer?
 
Kind regards
 
Dave
-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
an...@rh...
Sent: 02 June 2005 11:59
To: QuickFix
Subject: [Quickfix-developers] vs2005


When sending a new order using the .net dlls;  I am getting a message
rejected return stating that required field 6 is missing.  Field 6 is not
required or even a part of a New Order - Single.  Another developer in the
office using .NET 2003 and the same dlls is not having this problem.  Is
this a problem with the .NET 2005 beta?  I thought I'd check to see if
anyone else is having similar problems before I go through the process of
uninstalling 2005 beta and reinstalling 2003.
 
 
Thank you,
 
Andy 
 

RE: [Quickfix-developers] vs2005

[Dave L. <dav...@ma...>]

Hi Andy,
 
6 is a required field in the ExecutionReport (i.e. the response to the
NewOrderSingle). Is the rejection definitely in relation to the order?
 
Which version of FIX are you using? Do you have a tag 372 in the reject
message? If so, what is the value?
 
Are you using the same DataDictionary as the other developer?
 
Kind regards
 
Dave
-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
an...@rh...
Sent: 02 June 2005 11:59
To: QuickFix
Subject: [Quickfix-developers] vs2005


When sending a new order using the .net dlls;  I am getting a message
rejected return stating that required field 6 is missing.  Field 6 is
not required or even a part of a New Order - Single.  Another developer
in the office using .NET 2003 and the same dlls is not having this
problem.  Is this a problem with the .NET 2005 beta?  I thought I'd
check to see if anyone else is having similar problems before I go
through the process of uninstalling 2005 beta and reinstalling 2003.
 
 
Thank you,
 
Andy 
 

[Quickfix-developers] vs2005

[<an...@rh...>]

When sending a new order using the .net dlls;  I am getting a message
rejected return stating that required field 6 is missing.  Field 6 is
not required or even a part of a New Order - Single.  Another developer
in the office using .NET 2003 and the same dlls is not having this
problem.  Is this a problem with the .NET 2005 beta?  I thought I'd
check to see if anyone else is having similar problems before I go
through the process of uninstalling 2005 beta and reinstalling 2003.
=20
=20
Thank you,
=20
Andy=20
=20

[Quickfix-developers] AIX port of QuickFIX

[Joerg T. <Joe...@ma...>]

Hi all,

just wondering whether anybody of you managed to build QuickFIX on AIX (4.3 or newer)?
Would be interested to hear your experiences.

Thanks, Jörg

-- 
Joerg Thoennes
                                http://macd.com
Tel.: +49 (0)241 44597-24      Macdonald Associates GmbH
Fax : +49 (0)241 44597-10      Lothringer Str. 52, D-52070 Aachen

Re: [Quickfix-developers] Rawdata field

[Oren M. <or...@qu...>]

Caleb's patch has been checked into CVS along with a unit test based on =
your code.

--oren
  ----- Original Message -----=20
  From: Alexey Zubko=20
  To: Caleb Epstein=20
  Cc: qui...@li...=20
  Sent: Tuesday, May 31, 2005 11:15 AM
  Subject: Re: [Quickfix-developers] Rawdata field


  Caleb,

  Thank you. The patch solved the problem.


  P.S.
  Misspelling: reinterpret_cast


Regards,
		Alexey Zubko

  Caleb Epstein wrote:=20
On 5/31/05, Alexey Zubko <ale...@in...> wrote:

   Enclosed are the logs.
   =20
I actually get crashes trying to send the last message in that
outgoing file (the one with the 0xA4 bytes in RawData).  It looks.
like the CheckSum calculation gets messed up by high-bit ASCII
characters and goes negative, which is out-of-spec.  This patch fixes
the problem.

diff -u -b -u -p -r1.18 Field.h=20
--- Field.h     28 Dec 2004 15:23:26 -0000      1.18=20
+++ Field.h     31 May 2005 15:44:37 -0000=20
@@ -121,7 +121,10 @@ private:=20
       m_length =3D m_data.length();=20
     }=20
 =20
-    const char* iter =3D m_data.c_str();=20
+    // Treat strings as unsigned in case values contain high-bit=20
+    // chars.  Don't want checksum to go negative.=20
+    const unsigned char* iter =3D=20
+        reintepret_cast<const unsigned char*> (m_data.c_str());=20
     m_total =3D std::accumulate( iter, iter + m_length, 0 );=20
 =20
     m_calculated =3D true;=20

  

Re: [Quickfix-developers] Rawdata field

[Caleb E. <cal...@gm...>]

>  Misspelling: reinterpret_cast

Oops.   I guess I should have compiled it first :)

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Rawdata field

[Alexey Z. <ale...@in...>]

Caleb,

Thank you. The patch solved the problem.


P.S.
Misspelling: reinterpret_cast

Regards,
		Alexey Zubko


Caleb Epstein wrote:

>On 5/31/05, Alexey Zubko <ale...@in...> wrote:
>
>  
>
>> Enclosed are the logs.
>>    
>>
>
>I actually get crashes trying to send the last message in that
>.outgoing file (the one with the 0xA4 bytes in RawData).  It looks
>like the CheckSum calculation gets messed up by high-bit ASCII
>characters and goes negative, which is out-of-spec.  This patch fixes
>the problem.
>
>diff -u -b -u -p -r1.18 Field.h 
>--- Field.h     28 Dec 2004 15:23:26 -0000      1.18 
>+++ Field.h     31 May 2005 15:44:37 -0000 
>@@ -121,7 +121,10 @@ private: 
>       m_length = m_data.length(); 
>     } 
>  
>-    const char* iter = m_data.c_str(); 
>+    // Treat strings as unsigned in case values contain high-bit 
>+    // chars.  Don't want checksum to go negative. 
>+    const unsigned char* iter = 
>+        reintepret_cast<const unsigned char*> (m_data.c_str()); 
>     m_total = std::accumulate( iter, iter + m_length, 0 ); 
>  
>     m_calculated = true; 
>
>  
>

Re: [Quickfix-developers] Rawdata field

[Caleb E. <cal...@gm...>]

On 5/31/05, Alexey Zubko <ale...@in...> wrote:

>  Enclosed are the logs.

I actually get crashes trying to send the last message in that
.outgoing file (the one with the 0xA4 bytes in RawData).  It looks
like the CheckSum calculation gets messed up by high-bit ASCII
characters and goes negative, which is out-of-spec.  This patch fixes
the problem.

diff -u -b -u -p -r1.18 Field.h=20
--- Field.h     28 Dec 2004 15:23:26 -0000      1.18=20
+++ Field.h     31 May 2005 15:44:37 -0000=20
@@ -121,7 +121,10 @@ private:=20
       m_length =3D m_data.length();=20
     }=20
 =20
-    const char* iter =3D m_data.c_str();=20
+    // Treat strings as unsigned in case values contain high-bit=20
+    // chars.  Don't want checksum to go negative.=20
+    const unsigned char* iter =3D=20
+        reintepret_cast<const unsigned char*> (m_data.c_str());=20
     m_total =3D std::accumulate( iter, iter + m_length, 0 );=20
 =20
     m_calculated =3D true;=20

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Rawdata field

[Alexey Z. <ale...@in...>]

20050527-15:15:54 : Created session
20050527-15:15:54 : Connecting to localhost on port 1111
20050527-15:15:54 : Connection succeeded
20050527-15:15:55 : Initiated logon request
20050527-15:15:55 : Received logon response
20050527-15:18:09 : Created session
20050527-15:18:09 : Connecting to localhost on port 1111
20050527-15:18:09 : Connection succeeded
20050527-15:18:10 : Initiated logon request
20050527-15:18:10 : Dropped Connection
20050527-15:18:20 : Connecting to localhost on port 1111
20050527-15:18:20 : Connection succeeded
20050527-15:18:20 : Initiated logon request
20050527-15:18:20 : Dropped Connection
20050527-15:56:56 : Initiated logout request
20050527-15:56:56 : Received logout response
20050527-15:56:56 : Disconnecting
20050527-16:16:46 : Created session
20050527-16:16:46 : Connecting to localhost on port 1111
20050527-16:16:46 : Connection succeeded
20050527-16:16:47 : Initiated logon request
20050527-16:16:47 : Received logon response
20050527-16:23:59 : Received logout request
20050527-16:23:59 : Sending logout response
20050527-16:23:59 : Disconnecting
20050527-16:23:59 : Initiated logon request
20050527-16:24:07 : Connecting to localhost on port 1111
20050527-16:24:07 : Connection succeeded
20050527-16:24:07 : Initiated logon request
20050527-16:24:07 : Received logon response
20050527-16:24:27 : Initiated logout request
20050527-16:24:27 : Received logout response
20050527-16:24:27 : Disconnecting
20050527-16:25:01 : Created session
20050527-16:25:01 : Connecting to localhost on port 1111
20050527-16:25:02 : Connection succeeded
20050527-16:25:02 : Initiated logon request
20050527-16:25:02 : Received logon response
20050527-16:25:42 : Initiated logout request
20050527-16:25:42 : Received logout response
20050527-16:25:42 : Disconnecting
20050527-16:26:17 : Created session
20050527-16:26:17 : Connecting to localhost on port 1111
20050527-16:26:17 : Connection succeeded
20050527-16:26:18 : Initiated logon request
20050527-16:26:18 : Received logon response
20050527-16:27:03 : Received logout request
20050527-16:27:03 : Sending logout response
20050527-16:27:03 : Disconnecting
20050527-16:27:03 : Initiated logon request
20050527-16:27:08 : Connecting to localhost on port 1111
20050527-16:27:09 : Connection failed
20050527-16:27:18 : Connecting to localhost on port 1111
20050527-16:27:19 : Connection failed
20050527-16:27:28 : Connecting to localhost on port 1111
20050527-16:27:29 : Connection failed
20050527-16:27:38 : Connecting to localhost on port 1111
20050527-16:27:40 : Connection failed
20050527-16:27:48 : Connecting to localhost on port 1111
20050527-16:27:49 : Connection failed
20050527-16:27:58 : Connecting to localhost on port 1111
20050527-16:27:59 : Connection failed
20050527-16:28:08 : Connecting to localhost on port 1111
20050527-16:28:09 : Connection failed
20050527-16:28:18 : Connecting to localhost on port 1111
20050527-16:28:19 : Connection failed
20050527-16:28:28 : Connecting to localhost on port 1111
20050527-16:28:29 : Connection failed
20050527-16:28:38 : Connecting to localhost on port 1111
20050527-16:28:39 : Connection failed
20050527-16:28:48 : Connecting to localhost on port 1111
20050527-16:28:49 : Connection failed
20050527-16:28:58 : Connecting to localhost on port 1111
20050527-16:28:59 : Connection failed
20050527-16:29:08 : Connecting to localhost on port 1111
20050527-16:29:09 : Connection failed
20050527-16:29:18 : Connecting to localhost on port 1111
20050527-16:29:19 : Connection failed
20050527-16:29:28 : Connecting to localhost on port 1111
20050527-16:29:29 : Connection failed
20050527-16:29:38 : Connecting to localhost on port 1111
20050527-16:29:39 : Connection failed
20050527-16:29:48 : Connecting to localhost on port 1111
20050527-16:29:49 : Connection failed
20050527-16:29:58 : Connecting to localhost on port 1111
20050527-16:29:59 : Connection failed
20050527-16:30:08 : Connecting to localhost on port 1111
20050527-16:30:09 : Connection failed
20050527-16:30:18 : Connecting to localhost on port 1111
20050527-16:30:20 : Connection failed
20050527-16:30:28 : Connecting to localhost on port 1111
20050527-16:30:29 : Connection failed
20050527-16:30:38 : Connecting to localhost on port 1111
20050527-16:30:38 : Connection succeeded
20050527-16:30:38 : Initiated logon request
20050527-16:30:38 : Received logon response
20050527-16:30:42 : Created session
20050527-16:30:42 : Connecting to localhost on port 1111
20050527-16:30:42 : Connection succeeded
20050527-16:30:43 : Initiated logon request
20050527-16:30:43 : Dropped Connection
20050527-16:30:47 : Initiated logout request
20050527-16:30:47 : Received logout response
20050527-16:30:47 : Disconnecting
20050527-16:30:53 : Connecting to localhost on port 1111
20050527-16:30:53 : Connection succeeded
20050527-16:30:53 : Initiated logon request
20050527-16:30:53 : Received logon response
20050527-16:30:53 : MsgSeqNum too high, expecting  111 but received 112
20050527-16:30:53 : Sent ResendRequest FROM: 111 TO: 111
20050527-16:30:53 : Received SequenceReset FROM: 111 TO: 112
20050527-16:30:53 : Processing QUEUED message: 112
20050527-16:34:03 : Initiated logout request
20050527-16:34:03 : Received logout response
20050527-16:34:03 : Disconnecting
20050527-16:34:35 : Created session
20050527-16:34:35 : Connecting to localhost on port 1111
20050527-16:34:35 : Connection succeeded
20050527-16:34:36 : Initiated logon request
20050527-16:34:36 : Received logon response
20050527-16:34:45 : Initiated logout request
20050527-16:34:45 : Received logout response
20050527-16:34:45 : Disconnecting
20050527-16:34:54 : Created session
20050527-16:34:54 : Connecting to localhost on port 1111
20050527-16:34:54 : Connection succeeded
20050527-16:34:55 : Initiated logon request
20050527-16:34:55 : Received logon response
20050527-16:36:02 : Created session
20050527-16:36:02 : Connecting to localhost on port 1111
20050527-16:36:02 : Connection succeeded
20050527-16:36:03 : Initiated logon request
20050527-16:36:03 : Received logon response
20050527-16:36:03 : MsgSeqNum too high, expecting  123 but received 124
20050527-16:36:03 : Sent ResendRequest FROM: 123 TO: 123
20050527-16:36:03 : Received SequenceReset FROM: 123 TO: 124
20050527-16:36:03 : Processing QUEUED message: 124
20050527-16:36:32 : Created session
20050527-16:36:32 : Connecting to localhost on port 1111
20050527-16:36:32 : Connection succeeded
20050527-16:36:33 : Initiated logon request
20050527-16:36:33 : Received logon response
20050527-16:36:52 : Created session
20050527-16:36:52 : Connecting to localhost on port 1111
20050527-16:36:52 : Connection succeeded
20050527-16:36:53 : Initiated logon request
20050527-16:36:53 : Received logon response
20050527-16:37:36 : Sent test request TEST
20050527-16:38:34 : Created session
20050527-16:38:34 : Connecting to localhost on port 1111
20050527-16:38:34 : Connection succeeded
20050527-16:38:35 : Initiated logon request
20050527-16:38:35 : Received logon response
20050527-16:38:35 : MsgSeqNum too high, expecting  130 but received 131
20050527-16:38:35 : Sent ResendRequest FROM: 130 TO: 130
20050527-16:38:35 : Received SequenceReset FROM: 130 TO: 131
20050527-16:38:35 : Processing QUEUED message: 131
20050527-16:38:45 : Created session
20050527-16:38:45 : Connecting to localhost on port 1111
20050527-16:38:46 : Connection succeeded
20050527-16:38:48 : Initiated logon request
20050527-16:38:48 : Received logon response
20050527-16:41:11 : Timed out waiting for heartbeat
20050527-16:41:11 : Dropped Connection
20050527-16:41:12 : Connecting to localhost on port 1111
20050527-16:41:12 : Connection succeeded
20050527-16:41:12 : Initiated logon request
20050527-16:41:12 : Received logon response
20050527-16:41:12 : Received ResendRequest FROM: 240 TO: 240
20050527-16:41:12 : Resending Message: 240
20050527-17:43:57 : Created session
20050527-17:43:57 : Connecting to localhost on port 1111
20050527-17:43:57 : Connection succeeded
20050527-17:43:58 : Initiated logon request
20050527-17:43:58 : Received logon response
20050527-17:43:58 : MsgSeqNum too high, expecting  138 but received 140
20050527-17:43:58 : Sent ResendRequest FROM: 138 TO: 139
20050527-17:43:58 : Received SequenceReset FROM: 138 TO: 140
20050527-17:43:58 : Processing QUEUED message: 140
20050527-17:46:27 : Received logout request
20050527-17:46:27 : Sending logout response
20050527-17:46:27 : Disconnecting
20050527-17:46:27 : Initiated logon request
20050527-17:46:28 : Connecting to localhost on port 1111
20050527-17:46:29 : Connection failed
20050527-17:46:38 : Connecting to localhost on port 1111
20050527-17:46:39 : Connection failed
20050527-17:46:48 : Connecting to localhost on port 1111
20050527-17:46:49 : Connection failed
20050527-17:46:58 : Connecting to localhost on port 1111
20050527-17:46:59 : Connection failed
20050527-17:47:08 : Connecting to localhost on port 1111
20050527-17:47:09 : Connection failed
20050527-17:47:50 : Created session
20050527-17:47:50 : Connecting to localhost on port 1111
20050527-17:47:50 : Connection succeeded
20050527-17:47:51 : Initiated logon request
20050527-17:47:51 : Received logon response
20050527-17:48:35 : Received logout request
20050527-17:48:35 : Sending logout response
20050527-17:48:35 : Disconnecting
20050527-17:48:35 : Initiated logon request
20050527-17:49:02 : Created session
20050527-17:49:02 : Connecting to localhost on port 1111
20050527-17:49:03 : Connection succeeded
20050527-17:49:04 : Initiated logon request
20050527-17:49:04 : Received logon response
20050527-17:50:07 : Created session
20050527-17:50:07 : Connecting to localhost on port 1111
20050527-17:50:07 : Connection succeeded
20050527-17:50:08 : Initiated logon request
20050527-17:50:08 : Received logon response
20050527-17:50:52 : Created session
20050527-17:50:52 : Connecting to localhost on port 1111
20050527-17:50:53 : Connection failed
20050527-17:50:54 : Connecting to localhost on port 1111
20050527-17:50:55 : Connection failed
20050527-17:51:04 : Connecting to localhost on port 1111
20050527-17:51:05 : Connection succeeded
20050527-17:51:05 : Initiated logon request
20050527-17:51:05 : Received logon response
20050527-19:17:58 : Initiated logout request
20050527-19:17:58 : Received logout response
20050527-19:17:58 : Disconnecting
20050527-19:31:56 : Created session
20050527-19:31:56 : Connecting to localhost on port 1111
20050527-19:31:57 : Connection failed
20050527-19:31:58 : Connecting to localhost on port 1111
20050527-19:31:59 : Connection failed
20050527-19:32:08 : Connecting to localhost on port 1111
20050527-19:32:08 : Connection succeeded
20050527-19:32:08 : Initiated logon request
20050527-19:32:08 : Received logon response
20050527-19:32:18 : Initiated logout request
20050527-19:32:18 : Received logout response
20050527-19:32:18 : Disconnecting
20050527-19:32:19 : Created session
20050527-19:32:19 : Connecting to localhost on port 1111
20050527-19:32:19 : Connection succeeded
20050527-19:32:20 : Initiated logon request
20050527-19:32:20 : Received logon response
20050527-19:33:04 : Created session
20050527-19:33:04 : Connecting to localhost on port 1111
20050527-19:33:04 : Connection succeeded
20050527-19:33:05 : Initiated logon request
20050527-19:33:05 : Received logon response
20050527-19:33:08 : Initiated logout request
20050527-19:33:08 : Received logout response
20050527-19:33:08 : Disconnecting
20050527-19:33:09 : Created session
20050527-19:33:09 : Connecting to localhost on port 1111
20050527-19:33:09 : Connection succeeded
20050527-19:33:10 : Initiated logon request
20050527-19:33:10 : Received logon response
20050527-19:33:52 : Created session
20050527-19:33:52 : Connecting to localhost on port 1111
20050527-19:33:53 : Connection succeeded
20050527-19:33:53 : Initiated logon request
20050527-19:33:53 : Received logon response
20050527-19:33:55 : Initiated logout request
20050527-19:33:55 : Received logout response
20050527-19:33:55 : Disconnecting
20050527-19:33:56 : Created session
20050527-19:33:56 : Connecting to localhost on port 1111
20050527-19:33:56 : Connection succeeded
20050527-19:33:57 : Initiated logon request
20050527-19:33:57 : Received logon response
20050527-19:34:40 : Created session
20050527-19:34:40 : Connecting to localhost on port 1111
20050527-19:34:41 : Connection succeeded
20050527-19:34:41 : Initiated logon request
20050527-19:34:41 : Received logon response
20050527-19:34:43 : Initiated logout request
20050527-19:34:43 : Received logout response
20050527-19:34:43 : Disconnecting
20050527-19:34:44 : Created session
20050527-19:34:44 : Connecting to localhost on port 1111
20050527-19:34:44 : Connection succeeded
20050527-19:34:45 : Initiated logon request
20050527-19:34:45 : Received logon response
20050527-19:34:48 : Initiated logout request
20050527-19:34:48 : Received logout response
20050527-19:34:48 : Disconnecting
20050527-19:34:48 : Created session
20050527-19:34:48 : Connecting to localhost on port 1111
20050527-19:34:48 : Connection succeeded
20050527-19:34:49 : Initiated logon request
20050527-19:34:49 : Received logon response
20050527-19:34:52 : Initiated logout request
20050527-19:34:52 : Received logout response
20050527-19:34:52 : Disconnecting
20050527-19:34:52 : Created session
20050527-19:34:52 : Connecting to localhost on port 1111
20050527-19:34:52 : Connection succeeded
20050527-19:34:53 : Initiated logon request
20050527-19:34:53 : Received logon response
20050527-19:34:55 : Initiated logout request
20050527-19:34:55 : Received logout response
20050527-19:34:55 : Disconnecting
20050527-19:34:56 : Created session
20050527-19:34:56 : Connecting to localhost on port 1111
20050527-19:34:56 : Connection succeeded
20050527-19:34:57 : Initiated logon request
20050527-19:34:57 : Received logon response
20050527-19:34:59 : Initiated logout request
20050527-19:34:59 : Received logout response
20050527-19:34:59 : Disconnecting
20050527-19:34:59 : Created session
20050527-19:34:59 : Connecting to localhost on port 1111
20050527-19:34:59 : Connection succeeded
20050527-19:35:00 : Created session
20050527-19:35:00 : Connecting to localhost on port 1111
20050527-19:35:00 : Connection succeeded
20050527-19:35:01 : Created session
20050527-19:35:01 : Connecting to localhost on port 1111
20050527-19:35:01 : Connection succeeded
20050527-19:35:02 : Created session
20050527-19:35:02 : Connecting to localhost on port 1111
20050527-19:35:02 : Connection succeeded
20050527-19:35:02 : Created session
20050527-19:35:03 : Connecting to localhost on port 1111
20050527-19:35:03 : Connection succeeded
20050527-19:35:04 : Created session
20050527-19:35:04 : Connecting to localhost on port 1111
20050527-19:35:04 : Connection succeeded
20050527-19:35:04 : Created session
20050527-19:35:04 : Connecting to localhost on port 1111
20050527-19:35:04 : Connection succeeded
20050527-19:35:05 : Created session
20050527-19:35:05 : Connecting to localhost on port 1111
20050527-19:35:05 : Connection succeeded
20050527-19:35:06 : Initiated logon request
20050527-19:35:06 : Received logon response
20050527-19:35:07 : Initiated logout request
20050527-19:35:07 : Received logout response
20050527-19:35:07 : Disconnecting
20050527-19:35:07 : Created session
20050527-19:35:07 : Connecting to localhost on port 1111
20050527-19:35:07 : Connection succeeded
20050527-19:35:07 : Created session
20050527-19:35:07 : Connecting to localhost on port 1111
20050527-19:35:07 : Connection succeeded
20050527-19:35:08 : Created session
20050527-19:35:08 : Connecting to localhost on port 1111
20050527-19:35:08 : Connection succeeded
20050527-19:35:08 : Created session
20050527-19:35:08 : Connecting to localhost on port 1111
20050527-19:35:08 : Connection succeeded
20050527-19:35:08 : Created session
20050527-19:35:09 : Connecting to localhost on port 1111
20050527-19:35:09 : Connection succeeded
20050527-19:35:10 : Initiated logon request
20050527-19:35:10 : Received logon response
20050527-19:35:19 : Initiated logout request
20050527-19:35:19 : Received logout response
20050527-19:35:19 : Disconnecting
20050527-19:35:19 : Created session
20050527-19:35:19 : Connecting to localhost on port 1111
20050527-19:35:19 : Connection succeeded
20050527-19:35:20 : Created session
20050527-19:35:20 : Connecting to localhost on port 1111
20050527-19:35:20 : Connection succeeded
20050527-19:35:20 : Created session
20050527-19:35:20 : Connecting to localhost on port 1111
20050527-19:35:20 : Connection succeeded
20050527-19:35:20 : Created session
20050527-19:35:20 : Connecting to localhost on port 1111
20050527-19:35:20 : Connection succeeded
20050527-19:35:21 : Created session
20050527-19:35:21 : Connecting to localhost on port 1111
20050527-19:35:21 : Connection succeeded
20050527-19:35:21 : Created session
20050527-19:35:21 : Connecting to localhost on port 1111
20050527-19:35:21 : Connection succeeded
20050527-19:35:21 : Created session
20050527-19:35:22 : Connecting to localhost on port 1111
20050527-19:35:22 : Connection succeeded
20050527-19:35:22 : Created session
20050527-19:35:22 : Connecting to localhost on port 1111
20050527-19:35:22 : Connection succeeded
20050527-19:35:22 : Created session
20050527-19:35:22 : Connecting to localhost on port 1111
20050527-19:35:22 : Connection succeeded
20050527-19:35:23 : Created session
20050527-19:35:23 : Connecting to localhost on port 1111
20050527-19:35:23 : Connection succeeded
20050527-19:35:24 : Created session
20050527-19:35:24 : Connecting to localhost on port 1111
20050527-19:35:24 : Connection succeeded
20050527-19:35:25 : Initiated logon request
20050527-19:35:25 : Received logon response
20050527-19:35:34 : Initiated logout request
20050527-19:35:34 : Received logout response
20050527-19:35:34 : Disconnecting
20050527-19:35:34 : Created session
20050527-19:35:34 : Connecting to localhost on port 1111
20050527-19:35:34 : Connection succeeded
20050527-19:35:35 : Initiated logon request
20050527-19:35:35 : Received logon response
20050527-19:36:37 : Initiated logout request
20050527-19:36:37 : Received logout response
20050527-19:36:37 : Disconnecting
20050527-19:36:38 : Created session
20050527-19:36:38 : Connecting to localhost on port 1111
20050527-19:36:38 : Connection succeeded
20050527-19:36:39 : Initiated logon request
20050527-19:36:39 : Received logon response
20050527-19:36:45 : Initiated logout request
20050527-19:36:45 : Received logout response
20050527-19:36:45 : Disconnecting
20050527-19:36:45 : Created session
20050527-19:36:45 : Connecting to localhost on port 1111
20050527-19:36:45 : Connection succeeded
20050527-19:36:46 : Initiated logon request
20050527-19:36:46 : Received logon response
20050527-19:36:54 : Initiated logout request
20050527-19:36:54 : Received logout response
20050527-19:36:54 : Disconnecting
20050527-19:36:55 : Created session
20050527-19:36:55 : Connecting to localhost on port 1111
20050527-19:36:55 : Connection succeeded
20050527-19:36:56 : Initiated logon request
20050527-19:36:56 : Received logon response
20050527-19:36:58 : Initiated logout request
20050527-19:36:58 : Received logout response
20050527-19:36:58 : Disconnecting
20050527-19:36:58 : Created session
20050527-19:36:58 : Connecting to localhost on port 1111
20050527-19:36:58 : Connection succeeded
20050527-19:36:59 : Initiated logon request
20050527-19:36:59 : Received logon response
20050527-19:37:02 : Initiated logout request
20050527-19:37:02 : Received logout response
20050527-19:37:02 : Disconnecting
20050527-19:37:03 : Created session
20050527-19:37:03 : Connecting to localhost on port 1111
20050527-19:37:03 : Connection succeeded
20050527-19:37:04 : Initiated logon request
20050527-19:37:04 : Received logon response
20050527-19:37:10 : Initiated logout request
20050527-19:37:10 : Received logout response
20050527-19:37:10 : Disconnecting
20050527-19:37:10 : Created session
20050527-19:37:10 : Connecting to localhost on port 1111
20050527-19:37:10 : Connection succeeded
20050527-19:37:11 : Initiated logon request
20050527-19:37:11 : Received logon response
20050527-19:37:15 : Initiated logout request
20050527-19:37:15 : Received logout response
20050527-19:37:15 : Disconnecting
20050527-19:37:15 : Created session
20050527-19:37:15 : Connecting to localhost on port 1111
20050527-19:37:15 : Connection succeeded
20050527-19:37:16 : Initiated logon request
20050527-19:37:16 : Received logon response
20050527-19:37:27 : Initiated logout request
20050527-19:37:27 : Received logout response
20050527-19:37:27 : Disconnecting
20050527-19:37:28 : Created session
20050527-19:37:28 : Connecting to localhost on port 1111
20050527-19:37:28 : Connection succeeded
20050527-19:37:29 : Initiated logon request
20050527-19:37:29 : Received logon response
20050527-19:37:43 : Initiated logout request
20050527-19:37:43 : Received logout response
20050527-19:37:43 : Disconnecting
20050527-19:37:43 : Created session
20050527-19:37:43 : Connecting to localhost on port 1111
20050527-19:37:43 : Connection succeeded
20050527-19:37:44 : Initiated logon request
20050527-19:37:44 : Received logon response
20050527-19:40:46 : Created session
20050527-19:40:46 : Connecting to localhost on port 1111
20050527-19:40:48 : Connection failed
20050527-19:40:49 : Connecting to localhost on port 1111
20050527-19:40:49 : Connection succeeded
20050527-19:40:49 : Initiated logon request
20050527-19:40:49 : Received logon response
20050527-19:41:36 : Created session
20050527-19:41:36 : Connecting to localhost on port 1111
20050527-19:41:36 : Connection succeeded
20050527-19:41:37 : Initiated logon request
20050527-19:41:37 : Received logout request
20050527-19:41:37 : Sending logout response
20050527-19:41:37 : Disconnecting
20050527-19:41:37 : Initiated logon request
20050527-19:41:47 : Connecting to localhost on port 1111
20050527-19:41:47 : Connection succeeded
20050527-19:41:47 : Initiated logon request
20050527-19:41:47 : Received logon response
20050527-19:41:47 : MsgSeqNum too high, expecting  573 but received 576
20050527-19:41:47 : Sent ResendRequest FROM: 573 TO: 575
20050527-19:41:47 : Received ResendRequest FROM: 679 TO: 679
20050527-19:41:47 : Sent SequenceReset TO: 680
20050527-19:41:47 : Received SequenceReset FROM: 573 TO: 576
20050527-19:41:47 : Processing QUEUED message: 576
20050527-19:41:56 : Created session
20050527-19:41:56 : Connecting to localhost on port 1111
20050527-19:41:56 : Connection succeeded
20050527-19:41:57 : Initiated logon request
20050527-19:41:57 : Received logon response
20050527-19:41:57 : MsgSeqNum too high, expecting  577 but received 578
20050527-19:41:57 : Sent ResendRequest FROM: 577 TO: 577
20050527-19:41:57 : Received ResendRequest FROM: 681 TO: 681
20050527-19:41:57 : Sent SequenceReset TO: 682
20050527-19:41:57 : Received SequenceReset FROM: 577 TO: 578
20050527-19:41:57 : Processing QUEUED message: 578
20050527-19:41:59 : Received ResendRequest FROM: 683 TO: 683
20050527-19:41:59 : Sent SequenceReset TO: 684
20050527-19:41:59 : MsgSeqNum too high, expecting  579 but received 581
20050527-19:41:59 : Sent ResendRequest FROM: 579 TO: 580
20050527-19:41:59 : Received SequenceReset FROM: 579 TO: 581
20050527-19:41:59 : Processing QUEUED message: 581
20050527-19:42:05 : Created session
20050527-19:42:05 : Connecting to localhost on port 1111
20050527-19:42:05 : Connection succeeded
20050527-19:42:06 : Initiated logon request
20050527-19:42:06 : Received logon response
20050527-19:42:06 : MsgSeqNum too high, expecting  581 but received 582
20050527-19:42:06 : Sent ResendRequest FROM: 581 TO: 581
20050527-19:42:18 : Created session
20050527-19:42:18 : Connecting to localhost on port 1111
20050527-19:42:18 : Connection succeeded
20050527-19:42:19 : Initiated logon request
20050527-19:42:19 : Received logon response
20050527-19:42:19 : MsgSeqNum too high, expecting  581 but received 583
20050527-19:42:19 : Sent ResendRequest FROM: 581 TO: 582
20050527-19:44:50 : Created session
20050527-19:44:50 : Connecting to localhost on port 1111
20050527-19:44:50 : Connection succeeded
20050527-19:44:51 : Initiated logon request
20050527-19:44:51 : Received logon response
20050527-19:44:51 : MsgSeqNum too high, expecting  581 but received 584
20050527-19:44:51 : Sent ResendRequest FROM: 581 TO: 583
20050527-19:45:02 : Created session
20050527-19:45:02 : Connecting to localhost on port 1111
20050527-19:45:02 : Connection succeeded
20050527-19:45:03 : Initiated logon request
20050527-19:45:03 : Received logon response
20050527-19:45:03 : MsgSeqNum too high, expecting  581 but received 585
20050527-19:45:03 : Sent ResendRequest FROM: 581 TO: 584
20050527-19:45:10 : Created session
20050527-19:45:10 : Connecting to localhost on port 1111
20050527-19:45:10 : Connection succeeded
20050527-19:45:11 : Initiated logon request
20050527-19:45:11 : Received logon response
20050527-19:45:11 : MsgSeqNum too high, expecting  581 but received 586
20050527-19:45:11 : Sent ResendRequest FROM: 581 TO: 585
20050527-19:46:27 : Created session
20050527-19:46:27 : Connecting to localhost on port 1111
20050527-19:46:27 : Connection succeeded
20050527-19:46:28 : Initiated logon request
20050527-19:46:28 : Received logon response
20050527-19:46:28 : MsgSeqNum too high, expecting  581 but received 587
20050527-19:46:28 : Sent ResendRequest FROM: 581 TO: 586
20050527-19:46:28 : Received SequenceReset FROM: 582 TO: 587
20050527-19:46:28 : Processing QUEUED message: 587
20050527-19:46:57 : Created session
20050527-19:46:57 : Connecting to localhost on port 1111
20050527-19:46:57 : Connection succeeded
20050527-19:46:58 : Initiated logon request
20050527-19:46:58 : Received logon response
20050527-19:50:51 : Created session
20050527-19:50:51 : Connecting to localhost on port 1111
20050527-19:50:51 : Connection succeeded
20050527-19:50:52 : Initiated logon request
20050527-19:50:52 : Received logon response
20050527-19:52:01 : Received logout request
20050527-19:52:01 : Sending logout response
20050527-19:52:01 : Disconnecting
20050527-19:52:01 : Initiated logon request
20050527-19:52:02 : Connecting to localhost on port 1111
20050527-19:52:03 : Connection failed
20050527-19:52:12 : Connecting to localhost on port 1111
20050527-19:52:12 : Connection succeeded
20050527-19:52:12 : Initiated logon request
20050527-19:52:12 : Received logon response
20050527-19:52:48 : Sent test request TEST
20050527-19:53:24 : Timed out waiting for heartbeat
20050527-19:53:24 : Dropped Connection
20050527-19:53:32 : Connecting to localhost on port 1111
20050527-19:53:32 : Connection succeeded
20050527-19:53:32 : Initiated logon request
20050527-19:53:52 : Timed out waiting for logon response
20050527-19:53:52 : Dropped Connection
20050527-19:54:02 : Connecting to localhost on port 1111
20050527-19:54:02 : Connection succeeded
20050527-19:54:02 : Initiated logon request
20050527-19:54:22 : Timed out waiting for logon response
20050527-19:54:22 : Dropped Connection
20050527-19:54:32 : Connecting to localhost on port 1111
20050527-19:54:32 : Connection succeeded
20050527-19:54:32 : Initiated logon request
20050527-19:54:52 : Timed out waiting for logon response
20050527-19:54:52 : Dropped Connection
20050527-19:55:02 : Connecting to localhost on port 1111
20050527-19:55:02 : Connection succeeded
20050527-19:55:02 : Initiated logon request
20050527-19:55:22 : Timed out waiting for logon response
20050527-19:55:22 : Dropped Connection
20050527-19:55:32 : Connecting to localhost on port 1111
20050527-19:55:32 : Connection succeeded
20050527-19:55:32 : Initiated logon request
20050527-19:55:52 : Timed out waiting for logon response
20050527-19:55:52 : Dropped Connection
20050527-19:56:02 : Connecting to localhost on port 1111
20050527-19:56:03 : Connection failed
20050527-19:56:12 : Connecting to localhost on port 1111
20050527-19:56:13 : Connection failed
20050527-19:56:22 : Connecting to localhost on port 1111
20050527-19:56:23 : Connection failed
20050527-19:56:32 : Connecting to localhost on port 1111
20050527-19:56:33 : Connection failed
20050527-19:56:42 : Connecting to localhost on port 1111
20050527-19:56:43 : Connection failed
20050527-19:56:52 : Connecting to localhost on port 1111
20050527-19:56:53 : Connection failed
20050527-19:57:02 : Connecting to localhost on port 1111
20050527-19:57:03 : Connection failed
20050527-19:57:12 : Connecting to localhost on port 1111
20050527-19:57:13 : Connection failed
20050527-19:57:22 : Connecting to localhost on port 1111
20050527-19:57:23 : Connection failed
20050527-19:57:32 : Connecting to localhost on port 1111
20050527-19:57:33 : Connection failed
20050527-19:57:42 : Connecting to localhost on port 1111
20050527-19:57:44 : Connection failed
20050527-19:57:52 : Connecting to localhost on port 1111
20050527-19:57:53 : Connection failed
20050527-19:58:02 : Connecting to localhost on port 1111
20050527-19:58:03 : Connection failed
20050527-19:58:12 : Connecting to localhost on port 1111
20050527-19:58:13 : Connection failed
20050527-19:58:22 : Connecting to localhost on port 1111
20050527-19:58:23 : Connection failed
20050527-19:58:32 : Connecting to localhost on port 1111
20050527-19:58:33 : Connection failed
20050527-19:58:42 : Connecting to localhost on port 1111
20050527-19:58:43 : Connection failed
20050527-19:58:52 : Connecting to localhost on port 1111
20050527-19:58:53 : Connection failed
20050527-19:59:02 : Connecting to localhost on port 1111
20050527-19:59:03 : Connection failed
20050527-19:59:12 : Connecting to localhost on port 1111
20050527-19:59:13 : Connection failed
20050527-19:59:22 : Connecting to localhost on port 1111
20050527-19:59:23 : Connection failed
20050527-19:59:32 : Connecting to localhost on port 1111
20050527-19:59:33 : Connection failed
20050527-19:59:42 : Connecting to localhost on port 1111
20050527-19:59:43 : Connection failed
20050527-19:59:52 : Connecting to localhost on port 1111
20050527-19:59:53 : Connection failed
20050527-20:00:02 : Connecting to localhost on port 1111
20050527-20:00:03 : Connection failed
20050527-20:00:12 : Connecting to localhost on port 1111
20050527-20:00:14 : Connection failed
20050527-20:00:22 : Connecting to localhost on port 1111
20050527-20:00:23 : Connection failed
20050527-20:00:32 : Connecting to localhost on port 1111
20050527-20:00:33 : Connection failed
20050527-20:00:42 : Connecting to localhost on port 1111
20050527-20:00:43 : Connection failed
20050527-20:00:52 : Connecting to localhost on port 1111
20050527-20:00:53 : Connection failed
20050527-20:01:02 : Connecting to localhost on port 1111
20050527-20:01:03 : Connection failed
20050527-20:01:12 : Connecting to localhost on port 1111
20050527-20:01:13 : Connection failed
20050527-20:01:22 : Connecting to localhost on port 1111
20050527-20:01:23 : Connection failed
20050527-20:01:32 : Connecting to localhost on port 1111
20050527-20:01:33 : Connection failed
20050527-20:01:42 : Connecting to localhost on port 1111
20050527-20:01:43 : Connection failed
20050527-20:01:52 : Connecting to localhost on port 1111
20050527-20:01:53 : Connection failed
20050527-20:02:02 : Connecting to localhost on port 1111
20050527-20:02:03 : Connection failed
20050527-20:02:12 : Connecting to localhost on port 1111
20050527-20:02:13 : Connection failed
20050527-20:02:22 : Connecting to localhost on port 1111
20050527-20:02:23 : Connection failed
20050527-20:02:32 : Connecting to localhost on port 1111
20050527-20:02:33 : Connection failed
20050527-20:02:42 : Connecting to localhost on port 1111
20050527-20:02:43 : Connection failed
20050527-20:02:52 : Connecting to localhost on port 1111
20050527-20:02:54 : Connection failed
20050527-20:03:02 : Connecting to localhost on port 1111
20050527-20:03:03 : Connection failed
20050527-20:03:12 : Connecting to localhost on port 1111
20050527-20:03:13 : Connection failed
20050527-20:03:22 : Connecting to localhost on port 1111
20050527-20:03:23 : Connection failed
20050527-20:03:32 : Connecting to localhost on port 1111
20050527-20:03:33 : Connection failed
20050527-20:03:42 : Connecting to localhost on port 1111
20050527-20:03:43 : Connection failed
20050527-20:03:52 : Connecting to localhost on port 1111
20050527-20:03:53 : Connection failed
20050527-20:04:02 : Connecting to localhost on port 1111
20050527-20:04:03 : Connection failed
20050527-20:04:12 : Connecting to localhost on port 1111
20050527-20:04:13 : Connection failed
20050527-20:04:22 : Connecting to localhost on port 1111
20050527-20:04:23 : Connection failed
20050527-20:04:32 : Connecting to localhost on port 1111
20050527-20:04:33 : Connection failed
20050527-20:04:42 : Connecting to localhost on port 1111
20050527-20:04:43 : Connection failed
20050527-20:04:52 : Connecting to localhost on port 1111
20050527-20:04:53 : Connection failed
20050527-20:05:02 : Connecting to localhost on port 1111
20050527-20:05:03 : Connection failed
20050527-20:05:12 : Connecting to localhost on port 1111
20050527-20:05:13 : Connection failed
20050527-20:05:22 : Connecting to localhost on port 1111
20050527-20:05:23 : Connection failed
20050527-20:05:32 : Connecting to localhost on port 1111
20050527-20:05:34 : Connection failed
20050527-20:05:42 : Connecting to localhost on port 1111
20050527-20:05:43 : Connection failed
20050527-20:05:52 : Connecting to localhost on port 1111
20050527-20:05:53 : Connection failed
20050527-20:06:02 : Connecting to localhost on port 1111
20050527-20:06:03 : Connection failed
20050527-20:06:12 : Connecting to localhost on port 1111
20050527-20:06:13 : Connection failed
20050527-20:06:22 : Connecting to localhost on port 1111
20050527-20:06:23 : Connection failed
20050527-20:06:32 : Connecting to localhost on port 1111
20050527-20:06:33 : Connection failed
20050527-20:06:42 : Connecting to localhost on port 1111
20050527-20:06:43 : Connection failed
20050527-20:06:52 : Connecting to localhost on port 1111
20050527-20:06:53 : Connection failed
20050527-20:07:02 : Connecting to localhost on port 1111
20050527-20:07:03 : Connection failed
20050527-20:07:12 : Connecting to localhost on port 1111
20050527-20:07:13 : Connection failed
20050527-20:07:22 : Connecting to localhost on port 1111
20050527-20:07:23 : Connection failed
20050527-20:07:32 : Connecting to localhost on port 1111
20050527-20:07:33 : Connection failed
20050527-20:07:42 : Connecting to localhost on port 1111
20050527-20:07:43 : Connection failed
20050527-20:07:52 : Connecting to localhost on port 1111
20050527-20:07:53 : Connection failed
20050527-20:08:02 : Connecting to localhost on port 1111
20050527-20:08:04 : Connection failed
20050527-20:08:12 : Connecting to localhost on port 1111
20050527-20:08:13 : Connection failed
20050527-20:08:22 : Connecting to localhost on port 1111
20050527-20:08:23 : Connection failed
20050527-20:08:32 : Connecting to localhost on port 1111
20050527-20:08:33 : Connection failed
20050527-20:08:42 : Connecting to localhost on port 1111
20050527-20:08:43 : Connection failed
20050527-20:08:52 : Connecting to localhost on port 1111
20050527-20:08:53 : Connection failed
20050527-20:09:02 : Connecting to localhost on port 1111
20050527-20:09:03 : Connection failed
20050527-20:09:12 : Connecting to localhost on port 1111
20050527-20:09:13 : Connection failed
20050527-20:09:22 : Connecting to localhost on port 1111
20050527-20:09:23 : Connection failed
20050527-20:09:32 : Connecting to localhost on port 1111
20050527-20:09:33 : Connection failed
20050527-20:09:42 : Connecting to localhost on port 1111
20050527-20:09:43 : Connection failed
20050527-20:09:52 : Connecting to localhost on port 1111
20050527-20:09:53 : Connection failed
20050527-20:10:02 : Connecting to localhost on port 1111
20050527-20:10:03 : Connection failed
20050527-20:10:12 : Connecting to localhost on port 1111
20050527-20:10:13 : Connection failed
20050527-20:10:22 : Connecting to localhost on port 1111
20050527-20:10:24 : Connection failed
20050527-20:10:32 : Connecting to localhost on port 1111
20050527-20:10:33 : Connection failed
20050527-20:10:42 : Connecting to localhost on port 1111
20050527-20:10:43 : Connection failed
20050527-20:10:52 : Connecting to localhost on port 1111
20050527-20:10:53 : Connection failed
20050527-20:11:02 : Connecting to localhost on port 1111
20050527-20:11:03 : Connection failed
20050527-20:11:12 : Connecting to localhost on port 1111
20050527-20:11:13 : Connection failed
20050527-20:11:22 : Connecting to localhost on port 1111
20050527-20:11:23 : Connection failed
20050527-20:11:32 : Connecting to localhost on port 1111
20050527-20:11:33 : Connection failed
20050527-20:11:42 : Connecting to localhost on port 1111
20050527-20:11:43 : Connection failed
20050527-20:11:52 : Connecting to localhost on port 1111
20050527-20:11:53 : Connection failed
20050527-20:12:02 : Connecting to localhost on port 1111
20050527-20:12:03 : Connection failed
20050527-20:12:12 : Connecting to localhost on port 1111
20050527-20:12:13 : Connection failed
20050527-20:12:22 : Connecting to localhost on port 1111
20050527-20:12:23 : Connection failed
20050527-20:12:32 : Connecting to localhost on port 1111
20050527-20:12:33 : Connection failed
20050527-20:12:42 : Connecting to localhost on port 1111
20050527-20:12:43 : Connection failed
20050527-20:12:52 : Connecting to localhost on port 1111
20050527-20:12:53 : Connection failed
20050527-20:13:02 : Connecting to localhost on port 1111
20050527-20:13:03 : Connection failed
20050527-20:13:12 : Connecting to localhost on port 1111
20050527-20:13:13 : Connection failed
20050527-20:13:22 : Connecting to localhost on port 1111
20050527-20:13:23 : Connection failed
20050527-20:13:32 : Connecting to localhost on port 1111
20050527-20:13:33 : Connection failed
20050527-20:13:42 : Connecting to localhost on port 1111
20050527-20:13:43 : Connection failed
20050527-20:13:52 : Connecting to localhost on port 1111
20050527-20:13:54 : Connection failed
20050527-20:14:02 : Connecting to localhost on port 1111
20050527-20:14:03 : Connection failed
20050527-20:14:12 : Connecting to localhost on port 1111
20050527-20:14:13 : Connection failed
20050527-20:14:22 : Connecting to localhost on port 1111
20050527-20:14:23 : Connection failed
20050527-20:14:32 : Connecting to localhost on port 1111
20050527-20:14:33 : Connection failed
20050527-20:14:42 : Connecting to localhost on port 1111
20050527-20:14:43 : Connection failed
20050527-20:14:52 : Connecting to localhost on port 1111
20050527-20:14:53 : Connection failed
20050527-20:15:02 : Connecting to localhost on port 1111
20050527-20:15:03 : Connection failed
20050527-20:15:12 : Connecting to localhost on port 1111
20050527-20:15:13 : Connection failed
20050527-20:15:22 : Connecting to localhost on port 1111
20050527-20:15:23 : Connection failed
20050527-20:15:32 : Connecting to localhost on port 1111
20050527-20:15:33 : Connection failed
20050527-20:15:42 : Connecting to localhost on port 1111
20050527-20:15:43 : Connection failed
20050527-20:15:52 : Connecting to localhost on port 1111
20050527-20:15:53 : Connection failed
20050527-20:16:02 : Connecting to localhost on port 1111
20050527-20:16:03 : Connection failed
20050527-20:16:12 : Connecting to localhost on port 1111
20050527-20:16:13 : Connection failed
20050527-20:16:22 : Connecting to localhost on port 1111
20050527-20:16:23 : Connection failed
20050527-20:16:32 : Connecting to localhost on port 1111
20050527-20:16:34 : Connection failed
20050527-20:16:42 : Connecting to localhost on port 1111
20050527-20:16:43 : Connection failed
20050527-20:16:52 : Connecting to localhost on port 1111
20050527-20:16:53 : Connection failed
20050527-20:17:02 : Connecting to localhost on port 1111
20050527-20:17:03 : Connection failed
20050527-20:17:12 : Connecting to localhost on port 1111
20050527-20:17:13 : Connection failed
20050527-20:17:22 : Connecting to localhost on port 1111
20050527-20:17:23 : Connection failed
20050527-20:17:32 : Connecting to localhost on port 1111
20050527-20:17:33 : Connection failed
20050527-20:17:42 : Connecting to localhost on port 1111
20050527-20:17:43 : Connection failed
20050527-20:17:52 : Connecting to localhost on port 1111
20050527-20:17:53 : Connection failed
20050527-20:18:02 : Connecting to localhost on port 1111
20050527-20:18:03 : Connection failed
20050527-20:18:12 : Connecting to localhost on port 1111
20050527-20:18:13 : Connection failed
20050527-20:18:22 : Connecting to localhost on port 1111
20050527-20:18:23 : Connection failed
20050527-20:18:32 : Connecting to localhost on port 1111
20050527-20:18:33 : Connection failed
20050527-20:18:42 : Connecting to localhost on port 1111
20050527-20:18:43 : Connection failed
20050527-20:18:52 : Connecting to localhost on port 1111
20050527-20:18:53 : Connection failed
20050527-20:19:02 : Connecting to localhost on port 1111
20050527-20:19:03 : Connection failed
20050527-20:19:12 : Connecting to localhost on port 1111
20050527-20:19:14 : Connection failed
20050527-20:19:22 : Connecting to localhost on port 1111
20050527-20:19:23 : Connection failed
20050527-20:19:32 : Connecting to localhost on port 1111
20050527-20:19:33 : Connection failed
20050527-20:19:42 : Connecting to localhost on port 1111
20050527-20:19:43 : Connection failed
20050527-20:19:52 : Connecting to localhost on port 1111
20050527-20:19:53 : Connection failed
20050527-20:20:02 : Connecting to localhost on port 1111
20050527-20:20:03 : Connection failed
20050527-20:20:12 : Connecting to localhost on port 1111
20050527-20:20:13 : Connection failed
20050527-20:20:22 : Connecting to localhost on port 1111
20050527-20:20:23 : Connection failed
20050527-20:20:32 : Connecting to localhost on port 1111
20050527-20:20:33 : Connection failed
20050527-20:20:42 : Connecting to localhost on port 1111
20050527-20:20:43 : Connection failed
20050527-20:20:52 : Connecting to localhost on port 1111
20050527-20:20:53 : Connection failed
20050527-20:21:02 : Connecting to localhost on port 1111
20050527-20:21:03 : Connection failed
20050527-20:21:12 : Connecting to localhost on port 1111
20050527-20:21:13 : Connection failed
20050527-20:21:22 : Connecting to localhost on port 1111
20050527-20:21:23 : Connection failed
20050527-20:21:32 : Connecting to localhost on port 1111
20050527-20:21:33 : Connection failed
20050527-20:21:42 : Connecting to localhost on port 1111
20050527-20:21:43 : Connection failed
20050527-20:21:52 : Connecting to localhost on port 1111
20050527-20:21:54 : Connection failed
20050527-20:22:02 : Connecting to localhost on port 1111
20050527-20:22:03 : Connection failed
20050527-20:22:12 : Connecting to localhost on port 1111
20050527-20:22:13 : Connection failed
20050527-20:22:22 : Connecting to localhost on port 1111
20050527-20:22:23 : Connection failed
20050527-20:22:32 : Connecting to localhost on port 1111
20050527-20:22:33 : Connection failed
20050527-20:22:42 : Connecting to localhost on port 1111
20050527-20:22:43 : Connection failed
20050527-20:22:52 : Connecting to localhost on port 1111
20050527-20:22:53 : Connection failed
20050527-20:23:02 : Connecting to localhost on port 1111
20050527-20:23:03 : Connection failed
20050527-20:23:12 : Connecting to localhost on port 1111
20050527-20:23:13 : Connection failed
20050527-20:23:22 : Connecting to localhost on port 1111
20050527-20:23:23 : Connection failed
20050527-20:23:32 : Connecting to localhost on port 1111
20050527-20:23:33 : Connection failed
20050527-20:23:42 : Connecting to localhost on port 1111
20050527-20:23:43 : Connection failed
20050527-20:23:52 : Connecting to localhost on port 1111
20050527-20:23:53 : Connection failed
20050527-20:24:02 : Connecting to localhost on port 1111
20050527-20:24:03 : Connection failed
20050527-20:24:12 : Connecting to localhost on port 1111
20050527-20:24:13 : Connection failed
20050527-20:24:22 : Connecting to localhost on port 1111
20050527-20:24:24 : Connection failed
20050527-20:24:32 : Connecting to localhost on port 1111
20050527-20:24:33 : Connection failed
20050527-20:24:42 : Connecting to localhost on port 1111
20050527-20:24:43 : Connection failed
20050527-20:24:52 : Connecting to localhost on port 1111
20050527-20:24:53 : Connection failed
20050527-20:25:02 : Connecting to localhost on port 1111
20050527-20:25:03 : Connection failed
20050527-20:25:12 : Connecting to localhost on port 1111
20050527-20:25:13 : Connection failed
20050527-20:25:22 : Connecting to localhost on port 1111
20050527-20:25:23 : Connection failed
20050527-20:25:32 : Connecting to localhost on port 1111
20050527-20:25:33 : Connection failed
20050527-20:25:42 : Connecting to localhost on port 1111
20050527-20:25:43 : Connection failed
20050527-20:25:52 : Connecting to localhost on port 1111
20050527-20:25:53 : Connection failed
20050527-20:26:02 : Connecting to localhost on port 1111
20050527-20:26:03 : Connection failed
20050527-20:26:12 : Connecting to localhost on port 1111
20050527-20:26:13 : Connection failed
20050527-20:26:22 : Connecting to localhost on port 1111
20050527-20:26:23 : Connection failed
20050527-20:26:32 : Connecting to localhost on port 1111
20050527-20:26:33 : Connection failed
20050527-20:26:42 : Connecting to localhost on port 1111
20050527-20:26:43 : Connection failed
20050527-20:26:52 : Connecting to localhost on port 1111
20050527-20:26:53 : Connection failed
20050527-20:27:02 : Connecting to localhost on port 1111
20050527-20:27:04 : Connection failed
20050527-20:27:12 : Connecting to localhost on port 1111
20050527-20:27:13 : Connection failed
20050527-20:27:22 : Connecting to localhost on port 1111
20050527-20:27:23 : Connection failed
20050527-20:27:32 : Connecting to localhost on port 1111
20050527-20:27:33 : Connection failed
20050527-20:27:42 : Connecting to localhost on port 1111
20050527-20:27:43 : Connection failed
20050527-20:27:52 : Connecting to localhost on port 1111
20050527-20:27:53 : Connection failed
20050527-20:28:02 : Connecting to localhost on port 1111
20050527-20:28:03 : Connection failed
20050527-20:28:12 : Connecting to localhost on port 1111
20050527-20:28:13 : Connection failed
20050527-20:28:22 : Connecting to localhost on port 1111
20050527-20:28:23 : Connection failed
20050527-20:28:32 : Connecting to localhost on port 1111
20050527-20:28:33 : Connection failed
20050527-20:28:42 : Connecting to localhost on port 1111
20050527-20:28:43 : Connection failed
20050527-20:28:52 : Connecting to localhost on port 1111
20050527-20:28:53 : Connection failed
20050527-20:29:02 : Connecting to localhost on port 1111
20050527-20:29:03 : Connection failed
20050527-20:29:12 : Connecting to localhost on port 1111
20050527-20:29:13 : Connection failed
20050527-20:29:22 : Connecting to localhost on port 1111
20050527-20:29:23 : Connection failed
20050527-20:29:32 : Connecting to localhost on port 1111
20050527-20:29:33 : Connection failed
20050527-20:29:42 : Connecting to localhost on port 1111
20050527-20:29:44 : Connection failed
20050527-20:29:52 : Connecting to localhost on port 1111
20050527-20:29:53 : Connection failed
20050527-20:30:02 : Connecting to localhost on port 1111
20050527-20:30:03 : Connection failed
20050527-20:30:12 : Connecting to localhost on port 1111
20050527-20:30:13 : Connection failed
20050527-20:30:22 : Connecting to localhost on port 1111
20050527-20:30:23 : Connection failed
20050527-20:30:32 : Connecting to localhost on port 1111
20050527-20:30:33 : Connection failed
20050527-20:30:42 : Connecting to localhost on port 1111
20050527-20:30:43 : Connection failed
20050527-20:30:52 : Connecting to localhost on port 1111
20050527-20:30:53 : Connection failed
20050527-20:31:02 : Connecting to localhost on port 1111
20050527-20:31:03 : Connection failed
20050527-20:31:12 : Connecting to localhost on port 1111
20050527-20:31:13 : Connection failed
20050527-20:31:22 : Connecting to localhost on port 1111
20050527-20:31:23 : Connection failed
20050527-20:31:32 : Connecting to localhost on port 1111
20050527-20:31:33 : Connection failed
20050527-20:31:42 : Connecting to localhost on port 1111
20050527-20:31:43 : Connection failed
20050527-20:31:52 : Connecting to localhost on port 1111
20050527-20:31:53 : Connection failed
20050527-20:32:02 : Connecting to localhost on port 1111
20050527-20:32:03 : Connection failed
20050527-20:32:12 : Connecting to localhost on port 1111
20050527-20:32:14 : Connection failed
20050527-20:32:22 : Connecting to localhost on port 1111
20050527-20:32:23 : Connection failed
20050527-20:32:32 : Connecting to localhost on port 1111
20050527-20:32:33 : Connection failed
20050527-20:32:42 : Connecting to localhost on port 1111
20050527-20:32:43 : Connection failed
20050527-20:32:52 : Connecting to localhost on port 1111
20050527-20:32:53 : Connection failed
20050527-20:33:02 : Connecting to localhost on port 1111
20050527-20:33:03 : Connection failed
20050527-20:33:12 : Connecting to localhost on port 1111
20050527-20:33:13 : Connection failed
20050527-20:33:22 : Connecting to localhost on port 1111
20050527-20:33:23 : Connection failed
20050527-20:33:32 : Connecting to localhost on port 1111
20050527-20:33:33 : Connection failed
20050527-20:33:42 : Connecting to localhost on port 1111
20050527-20:33:43 : Connection failed
20050527-20:33:52 : Connecting to localhost on port 1111
20050527-20:33:53 : Connection failed
20050527-20:34:02 : Connecting to localhost on port 1111
20050527-20:34:03 : Connection failed
20050527-20:34:12 : Connecting to localhost on port 1111
20050527-20:34:13 : Connection failed
20050527-20:34:22 : Connecting to localhost on port 1111
20050527-20:34:23 : Connection failed
20050527-20:34:32 : Connecting to localhost on port 1111
20050527-20:34:33 : Connection failed
20050527-20:34:42 : Connecting to localhost on port 1111
20050527-20:34:43 : Connection failed
20050527-20:34:52 : Connecting to localhost on port 1111
20050527-20:34:54 : Connection failed
20050527-20:35:02 : Connecting to localhost on port 1111
20050527-20:35:03 : Connection failed
20050527-20:35:12 : Connecting to localhost on port 1111
20050527-20:35:13 : Connection failed
20050527-20:35:22 : Connecting to localhost on port 1111
20050527-20:35:23 : Connection failed
20050527-20:35:32 : Connecting to localhost on port 1111
20050527-20:35:33 : Connection failed
20050527-20:35:42 : Connecting to localhost on port 1111
20050527-20:35:43 : Connection failed
20050527-20:35:52 : Connecting to localhost on port 1111
20050527-20:35:53 : Connection failed
20050527-20:36:02 : Connecting to localhost on port 1111
20050527-20:36:03 : Connection failed
20050527-20:36:12 : Connecting to localhost on port 1111
20050527-20:36:13 : Connection failed
20050527-20:36:22 : Connecting to localhost on port 1111
20050527-20:36:23 : Connection failed
20050527-20:36:32 : Connecting to localhost on port 1111
20050527-20:36:33 : Connection failed
20050527-20:36:42 : Connecting to localhost on port 1111
20050527-20:36:43 : Connection failed
20050527-20:36:52 : Connecting to localhost on port 1111
20050527-20:36:53 : Connection failed
20050527-20:37:02 : Connecting to localhost on port 1111
20050527-20:37:03 : Connection failed
20050527-20:37:12 : Connecting to localhost on port 1111
20050527-20:37:13 : Connection failed
20050527-20:37:22 : Connecting to localhost on port 1111
20050527-20:37:23 : Connection failed
20050527-20:37:32 : Connecting to localhost on port 1111
20050527-20:37:34 : Connection failed
20050527-20:37:42 : Connecting to localhost on port 1111
20050527-20:37:43 : Connection failed
20050527-20:37:52 : Connecting to localhost on port 1111
20050527-20:37:53 : Connection failed
20050527-20:38:02 : Connecting to localhost on port 1111
20050527-20:38:03 : Connection failed
20050527-20:38:12 : Connecting to localhost on port 1111
20050527-20:38:13 : Connection failed
20050527-20:38:22 : Connecting to localhost on port 1111
20050527-20:38:23 : Connection failed
20050527-20:38:32 : Connecting to localhost on port 1111
20050527-20:38:33 : Connection failed
20050527-20:38:42 : Connecting to localhost on port 1111
20050527-20:38:43 : Connection failed
20050527-20:38:52 : Connecting to localhost on port 1111
20050527-20:38:53 : Connection failed
20050527-20:39:02 : Connecting to localhost on port 1111
20050527-20:39:03 : Connection failed
20050527-20:39:12 : Connecting to localhost on port 1111
20050527-20:39:13 : Connection failed
20050527-20:39:22 : Connecting to localhost on port 1111
20050527-20:39:23 : Connection failed
20050527-20:39:32 : Connecting to localhost on port 1111
20050527-20:39:33 : Connection failed
20050527-20:39:42 : Connecting to localhost on port 1111
20050527-20:39:43 : Connection failed
20050527-20:39:52 : Connecting to localhost on port 1111
20050527-20:39:53 : Connection failed
20050527-20:40:02 : Connecting to localhost on port 1111
20050527-20:40:03 : Connection failed
20050527-20:40:12 : Connecting to localhost on port 1111
20050527-20:40:14 : Connection failed
20050527-20:40:22 : Connecting to localhost on port 1111
20050527-20:40:23 : Connection failed
20050527-20:40:32 : Connecting to localhost on port 1111
20050527-20:40:33 : Connection failed
20050527-20:40:42 : Connecting to localhost on port 1111
20050527-20:40:43 : Connection failed
20050527-20:40:52 : Connecting to localhost on port 1111
20050527-20:40:53 : Connection failed
20050527-20:41:02 : Connecting to localhost on port 1111
20050527-20:41:03 : Connection failed
20050527-20:41:12 : Connecting to localhost on port 1111
20050527-20:41:13 : Connection failed
20050527-20:41:22 : Connecting to localhost on port 1111
20050527-20:41:23 : Connection failed
20050527-20:41:32 : Connecting to localhost on port 1111
20050527-20:41:33 : Connection failed
20050527-20:41:42 : Connecting to localhost on port 1111
20050527-20:41:43 : Connection failed
20050527-20:41:52 : Connecting to localhost on port 1111
20050527-20:41:53 : Connection failed
20050527-20:42:02 : Connecting to localhost on port 1111
20050527-20:42:03 : Connection failed
20050527-20:42:12 : Connecting to localhost on port 1111
20050527-20:42:13 : Connection failed
20050527-20:42:22 : Connecting to localhost on port 1111
20050527-20:42:23 : Connection failed
20050527-20:42:32 : Connecting to localhost on port 1111
20050527-20:42:33 : Connection failed
20050527-20:42:42 : Connecting to localhost on port 1111
20050527-20:42:44 : Connection failed
20050527-20:42:52 : Connecting to localhost on port 1111
20050527-20:42:53 : Connection failed
20050527-20:43:02 : Connecting to localhost on port 1111
20050527-20:43:03 : Connection failed
20050527-20:43:12 : Connecting to localhost on port 1111
20050527-20:43:13 : Connection failed
20050527-20:43:22 : Connecting to localhost on port 1111
20050527-20:43:23 : Connection failed
20050527-20:43:32 : Connecting to localhost on port 1111
20050527-20:43:33 : Connection failed
20050527-20:43:42 : Connecting to localhost on port 1111
20050527-20:43:43 : Connection failed
20050527-20:43:52 : Connecting to localhost on port 1111
20050527-20:43:53 : Connection failed
20050527-20:44:02 : Connecting to localhost on port 1111
20050527-20:44:03 : Connection failed
20050527-20:44:12 : Connecting to localhost on port 1111
20050527-20:44:13 : Connection failed
20050527-20:44:22 : Connecting to localhost on port 1111
20050527-20:44:23 : Connection failed
20050527-20:44:32 : Connecting to localhost on port 1111
20050527-20:44:33 : Connection failed
20050527-20:44:42 : Connecting to localhost on port 1111
20050527-20:44:43 : Connection failed
20050527-20:44:52 : Connecting to localhost on port 1111
20050527-20:44:53 : Connection failed
20050527-20:45:02 : Connecting to localhost on port 1111
20050527-20:45:03 : Connection failed
20050527-20:45:12 : Connecting to localhost on port 1111
20050527-20:45:13 : Connection failed
20050527-20:45:22 : Connecting to localhost on port 1111
20050527-20:45:24 : Connection failed
20050527-20:45:32 : Connecting to localhost on port 1111
20050527-20:45:33 : Connection failed
20050527-20:45:42 : Connecting to localhost on port 1111
20050527-20:45:43 : Connection failed
20050527-20:45:52 : Connecting to localhost on port 1111
20050527-20:45:53 : Connection failed
20050527-20:46:02 : Connecting to localhost on port 1111
20050527-20:46:03 : Connection failed
20050527-20:46:12 : Connecting to localhost on port 1111
20050527-20:46:13 : Connection failed
20050527-20:46:22 : Connecting to localhost on port 1111
20050527-20:46:23 : Connection failed
20050527-20:46:32 : Connecting to localhost on port 1111
20050527-20:46:33 : Connection failed
20050527-20:46:42 : Connecting to localhost on port 1111
20050527-20:46:43 : Connection failed
20050527-20:46:52 : Connecting to localhost on port 1111
20050527-20:46:53 : Connection failed
20050527-20:47:02 : Connecting to localhost on port 1111
20050527-20:47:03 : Connection failed
20050527-20:47:12 : Connecting to localhost on port 1111
20050527-20:47:13 : Connection failed
20050527-20:47:22 : Connecting to localhost on port 1111
20050527-20:47:23 : Connection failed
20050527-20:47:32 : Connecting to localhost on port 1111
20050527-20:47:33 : Connection failed
20050527-20:47:42 : Connecting to localhost on port 1111
20050527-20:47:43 : Connection failed
20050527-20:47:52 : Connecting to localhost on port 1111
20050527-20:47:53 : Connection failed
20050527-20:48:02 : Connecting to localhost on port 1111
20050527-20:48:04 : Connection failed
20050527-20:48:12 : Connecting to localhost on port 1111
20050527-20:48:13 : Connection failed
20050527-20:48:22 : Connecting to localhost on port 1111
20050527-20:48:23 : Connection failed
20050527-20:48:32 : Connecting to localhost on port 1111
20050527-20:48:33 : Connection failed
20050527-20:48:42 : Connecting to localhost on port 1111
20050527-20:48:43 : Connection failed
20050527-20:48:52 : Connecting to localhost on port 1111
20050527-20:48:53 : Connection failed
20050527-20:49:02 : Connecting to localhost on port 1111
20050527-20:49:03 : Connection failed
20050527-20:49:12 : Connecting to localhost on port 1111
20050527-20:49:13 : Connection failed
20050527-20:49:22 : Connecting to localhost on port 1111
20050527-20:49:23 : Connection failed
20050531-14:18:01 : Created session
20050531-14:18:01 : Connecting to localhost on port 1111
20050531-14:18:01 : Connection succeeded
20050531-14:18:02 : Initiated logon request
20050531-14:18:02 : Received logon response

Re: [Quickfix-developers] Rawdata field

[Caleb E. <cal...@gm...>]

On 5/31/05, Alexey Zubko <ale...@in...> wrote:

>  I use the last version - 1.9.4.
>  I sent FIX42::News message with RawData field filled with a random value=
.
>  When the data was -92 I got the problem.
>  Note it happened not on the first messages.

Session logfiles (and optionally code) might help to debug this.  Not
sure what you mean by the value of RawData being "-92".  Is this the
actual string value?

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] Rawdata field

[Alexey Z. <ale...@in...>]

Caleb,

I use the last version - 1.9.4.
I sent FIX42::News message with RawData field filled with a random value.
When the data was -92 I got the problem.
Note it happened not on the first messages.

I'm sorry I have no time to debug the code by myself right now.
Let me know if you need more details.

Regards,
		Alexey Zubko



Caleb Epstein wrote:

>On 5/27/05, Alexey Zubko <ale...@in...> wrote:
>
>  
>
>> I need to send a binary data in a message and I put RawDataLength and
>>RawData fields.
>> But sometimes I have a 'Could not convert field' exception during sending
>>of the message.
>> Is there a limitation on data or is there a known problem in quickfix?
>>    
>>
>
>Which version of QuickFIX?  There were bugs in versions prior to 1.9.3
>when messages contained embedded \0 bytes, even in data fields.
>
>  
>

Re: [Quickfix-developers] Rawdata field

[Caleb E. <cal...@gm...>]

On 5/27/05, Alexey Zubko <ale...@in...> wrote:

>  I need to send a binary data in a message and I put RawDataLength and
> RawData fields.
>  But sometimes I have a 'Could not convert field' exception during sendin=
g
> of the message.
>  Is there a limitation on data or is there a known problem in quickfix?

Which version of QuickFIX?  There were bugs in versions prior to 1.9.3
when messages contained embedded \0 bytes, even in data fields.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com