<html><head><base href="x-msg://236/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi<div><br><div><div>On 9 Apr 2013, at 10:56, V_Rajendraprasad wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><div style="direction: ltr; font-family: Tahoma; color: rgb(0, 0, 0); font-size: 10pt; ">suddenly the below error appread<br>ERROR I am Geeting: socket connection failure.<br>can any one suggest me...on this... <span class="Apple-converted-space"> </span><br><div><div style="font-family: Tahoma; font-size: 13px; "><div class="BodyFragment"><font size="2"><span style="font-size: 10pt; "></span></font></div></div></div></div></div></span></blockquote><div><br></div></div>Looks like a 'socket connection failure' to me! ;)</div><div><br></div><div>Have you checked to see if a network interruption (interface down, firewall/rules changed, etc) could've terminated the connection? Are you sure that the broker is still up and running and contactable on the requisite port(s) from the client?</div><div><br></div><div>Cheers,</div><div>Tim</div></body></html>