Re: [Quickfixj-users] Client suddenly stopped sending messages

[Christoph J. <chr...@ma...>]

When the initiator tries to establish a connection and this fails then the error message should be 
printed directly to the event log:

error   : java.net.ConnectException during connection to /xxxxxxxxxxxx java.net.ConnectException: 
Connection refused (Next retry in 30000 milliseconds)

For this to work you need to supply a LogFactory implementation with your initiator. Ee.g. the 
FileLogFactory.

Chris.

On 21/08/18 10:52, Vamsi Krishna wrote:
> It's working now.may be issue is on acceptor side. But at initiator level I want to print all 
> socket level errors.where can I modify that?
>
> On Tue, Aug 21, 2018, 2:11 PM Christoph John <chr...@ma... 
> <mailto:chr...@ma...>> wrote:
>
>     Hi,
>
>     with this little amount of information it is hard to tell what the problem is.
>     Which version of QFJ are you using?Make sure that you use the most recent version.
>     Could you post some log snippetswhere the problem occurs?
>
>     Chris.
>
>
>     On 17/08/18 10:16, Vamsi Krishna wrote:
>>     QuickFIX/J Documentation:http://www.quickfixj.org/documentation/
>>     QuickFIX/J Support:http://www.quickfixj.org/support/
>>
>>
>>
>>
>>     Hi Team,
>>
>>     My quickFixJ client suddenly stopped sending messages to server.From client side and server
>>     side nothing changed.
>>
>>     Any clue form your side what might happened.
>>
>>     Regards
>>     Vamsi Krishna
>>
>>
>>     ------------------------------------------------------------------------------
>>

-- 
Christoph John
Software Engineering
T +49 241 557080-28
chr...@ma...

MACD GmbH
Oppenhoffallee 103
52066 Aachen, Germany
www.macd.com

Amtsgericht Aachen: HRB 8151
Ust.-Id: DE 813021663
Geschäftsführer: George Macdonald