[QFJ-68] SocketConnectProtocol=vm_pipe Created: 07/Sep/06 Updated: 07/Sep/06 Resolved: 07/Sep/06 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | 1.0.2 |
| Fix Version/s: | None |
| Type: | Other | Priority: | Minor |
| Reporter: | Michael Briganti | Assignee: | Steve Bate |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows NT/jdk1.5.0_06 |
||
| Description |
|
The default protocol is tcp and the documentation makes no reference to Sockect [ Connect | Accept ] Protocol, nonetheless... When I set initiator/acceptor to use vm_pipe I receive the following on the initiator, event> (Connection failed: Failed to get the session.) Is the option currently being supported for the current engine in Windows NT/jdk1.5.0_06, if so I will try to dig a little further. Thanks |
| Comments |
| Comment by Steve Bate [ 07/Sep/06 ] |
|
I'm assuming both the initiator and acceptor are running in the same JVM. I modified the SocketInitiatorTest in my workspace to use VM_PIPE and it worked. I was able to cause the message you mentioned if my ports did not match between the initiator and acceptor. For example, if I used port 9879 for the initiator and port 9878 for the acceptor. Is it possible that this is causing your problem? The port is used for the VM_PIPE, but not the host. |
| Comment by Michael Briganti [ 07/Sep/06 ] |
|
|
| Comment by Steve Bate [ 07/Sep/06 ] |
|
OK, good. Thanks for letting me know. |