Re: [Quickfixj-users] Working with SSL and non SSL session on 1.1.0

[Jeronimo G. <jj...@pr...>]

This problem happens when the initiator is a non-ssl session (and the 
acceptor is defined to have both SSL and non-SSL sessions).
Anyway, I've tried to connect a non-SSL initiator using QFJ 1.1.0  to 
port 6002 (which is defined to be not encrypted in the configuration) 
and the same problem happens too (with exactly the same log output).

Obviously SSL connections to port 6001 are accepted OK, and if I define 
both 6001 and 6002 ports as non-SSL it works well too with non-SSL 
initiators connecting with 6001 and 6002 ports.


Toli Kuznets wrote:

>QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>QuickFIX/J Support: http://www.quickfixj.org/support/
>Jeronimo,
>
>I'll leave it up to Joerg and Steve to figure out the details of SSL
>connectivity, since they know about it than i do.
>
>One potential problem that i noticed is that your secondary SSL
>connection is coming from QFJ 1.0.5 - Steve did some rework on SSL
>code in 1.1.0.
>
>Can you try having the second initiator be a 1.1.0 QFJ code as well?
>Could be a quick and easy way to eliminate one unknown variable.
>
>  
>
>> But, when I tried to connect an iniciator (implemented with QuickFIXJ
>>1.0.5)  and with the following configuration:
>> [default]
>> ConnectionType=initiator
>> ....
>>    
>>
>
>  
>