RE: [Quickfix-users] Problem logging in - Socket Error: Connection reset by peer

[Kimpton, C \(Chris\) <Chr...@ra...>]

Hi J=F6rg,

Many thanks - that was it - I did not reverse the sender/target ids.



On your other points.

>> I am trying to write a simple FIX proxy type process - so that I can=20
>> simulate a busy response.

> Just curious: What do you mean by busy response?=20

When "busy" is turned on (not coded yet) I want to reject the messages us=
ing FIX reject messages, until the I turn it off again.  The initiator sh=
ould then retry until it does not get this kind of response.  This is too=
l for testing a specific problem only.


> Why do you use:

> ResetOnDisconnect=3DY
> ResetOnLogout=3DY

Just clutching at straws to try and get my basic problem solved - the soc=
ket error.  I will probably remove these when they start causing more pro=
blems ;-)


> And you could use the isLoggedOn() method of the session instead of usi=
ng a _loggedOn variable. This variable is not thread-
> safe, ie the JVM spec does not guarantee that another thread sees the a=
ctual value of _loggedOn. Please use

>  private synchronized boolean getLoggedOn() { return this._loggedOn; }
>  private synchronized setLoggedOn( final boolean loggedOn } { this._log=
gedOn =3D loggedOn; }

> Do you know that you can send message to a FIX session even if it is no=
t logged on? I.e.=20
> this check is not necessary, except you explitely want that behaviour.

It was more to cut down on superfluous messages being passed around - but=
=20I might review that when I actually get it doing the proxying...  As t=
o the JVM spec side of things, I did not know that, but I will bear that =
in mind.

Thanks again,
Chris
_____________________________________________________________

This email (including any attachments to it) is confidential, legally pri=
vileged, subject to copyright and is sent for the personal attention of t=
he intended recipient only. If you have received this email in error, ple=
ase advise us immediately and delete it. You are notified that disclosing=
, copying, distributing or taking any action in reliance on the contents =
of this information is strictly prohibited. Although we have taken reason=
able precautions to ensure no viruses are present in this email, we canno=
t accept responsibility for any loss or damage arising from the viruses i=
n this email or attachments. We exclude any liability for the content of =
this email, or for the consequences of any actions taken on the basis of =
the information provided in this email or its attachments, unless that in=
formation is subsequently confirmed in writing. If this email contains an=
=20offer, that should be considered as an invitation to treat.
_____________________________________________________________