[TYRUS-91] connectToServer creates 2 SessionImpl instances Created: 13/Feb/13 Updated: 14/Feb/13 Resolved: 14/Feb/13
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
I had an issue with some simple clientcode:
container = ContainerProvider.getClientContainer();
The onMessage call on myHandler never got called.
I debugged this, and it turned out that there were 2 Session objects:
The Session object that is passed into this onOpen method is the second
I wonder however, if it is intentional that a second SessionImpl is
|Comment by johanvos [ 13/Feb/13 ]|
The following patch on RemoteEndpoint fixed my problem – but I didn't look at the internals of SPIRemoteEndpoint, so this may introduce other issues, although all tests still run fine:
|Comment by Pavel Bucek [ 13/Feb/13 ]|
well, i have it fixed already in my local workspace and I took similar approach .. nevertheless, having you posted this here makes it actually more difficult I cannot accept any contribution without OCA - http://www.oracle.com/technetwork/community/oca-486395.html. Have you signed that? (Unable to find your name there).
|Comment by Pavel Bucek [ 14/Feb/13 ]|
fixed in the trunk, thanks!