Changed lines at line 3
3: Somewhere within the Sun implementation someone is not handling spaces appropriately. Since we use Maven on Windows for dev work all the third party libraries end up in 'Documents And Settings..' folder on C drive. Note the space in there. This was causing RMI heartburn though the manifestation of the problem as a socket write exception was a mis-direction. See:
4: http://www.velocityreviews.com/forums/t126367-spaces-in-path-to-app-causing-rmi-fits-with-malformedurlexception.html
5: So I found the RMI properties, one of which allows users to see debug info:
6: Somewhere within the Sun implementation someone is not handling spaces appropriately. Since we use Maven on Windows for dev work all the third party libraries end up in 'Documents And Settings..' folder on C drive. Note the space in there. This was causing RMI heartburn though the manifestation of the problem as a socket write exception was a mis-direction. See:\\
7: http://www.velocityreviews.com/forums/t126367-spaces-in-path-to-app-causing-rmi-fits-with-malformedurlexception.html
8: So I found the RMI properties, one of which allows users to see debug info:\\