The TransportHandler does not honor the passed in "initialReconnectDelay" parameter. It has a hard-coded value of "10" milliseconds.
Would also like to point out that the code seems to assume that the child transport has been created successfully as soon as the "TransportFactory.compositeConnect()" returns. During runtime, if a given node is down, the exception is actually thrown a little further down the code - when the "restoreTransport()" method is called.
|Field||Original Value||New Value|
|Attachment||patch.txt [ 17459 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||5.3.0 [ 11914 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||Dejan Bosanac [ dejanb ]|
|Project Import||Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|16d 17h 40m||1||Dejan Bosanac||15/Jan/09 18:00|