Re: Synapse not able to send request to jboss server + solaris 5.9

[Asankha C. Perera]

Oleg Probably these would be helpful too http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6288599 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6209425 Balaji What if you try to connect over another interface on the same host? another option would be to upgrade the OS level.. or deploy Synapse and JBoss on two physical systems.. are these viable options for the time being? asankha Oleg Kalnichevski wrote: On Fri, 2007-07-06 at 12:25 -0400, Sam Berlin wrote: If I can suggest a possible problem without actually looking or knowing the code at all... Based on the symptons that it works from one OS to another, but doesn't work within the same OS, and that the sample code was using selector.select(0), selector.selectNow, and SelectionKey.OP_CONNECT... Could the problem be that when the SocketChannel.connect is called, it is returning "true" (already connected), meaning that it does not need to go through the Selector at all? I do not know if there is code that handles this case, or if this is even the place where something is going wrong, but it is a very likely and possible scenario, and is something we've often encountered when doing localhost tests. What it boils down to is that when a SocketChannel.connect is called, it can either return false (meaning it has to be added to the selector and wait for an OP_CONNECT event), or true (meaning it is now connected and finishConnect doesn't even need to be called). On localhost, it is very likely that connecting will immedaitely work. Hi Sam This sounds very plausible. Presently DefaultConnectingIOReactor does not check the return value of the socketChannel#connect() method. This can well be it. Thanks a million for this hint. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]