Issue1316

Can be reproduced like this:

[hmm@bombadil ~]$ /opt/jython2.5b3/bin/jython
-Dpython.security.respectJavaAccessibility=false
Jython 2.5b3 (Release_2_5beta3:6092, Mar 10 2009, 15:34:57) 
[Java HotSpot(TM) Server VM (Sun Microsystems Inc.)] on java1.6.0_04
Type "help", "copyright", "credits" or "license" for more information.
>>> import urllib, socket
>>> socket.setdefaulttimeout(120)
>>> fp = urllib.urlopen("http://www.jython.org")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/jython2.5b3/Lib/urllib.py", line 82, in urlopen
    return opener.open(url)
  File "/opt/jython2.5b3/Lib/urllib.py", line 190, in open
    return getattr(self, name)(url)
  File "/opt/jython2.5b3/Lib/urllib.py", line 190, in open
    return getattr(self, name)(url)
  File "/opt/jython2.5b3/Lib/urllib.py", line 325, in open_http
    h.endheaders()
  File "/opt/jython2.5b3/Lib/httplib.py", line 860, in endheaders
    self._send_output()
  File "/opt/jython2.5b3/Lib/httplib.py", line 732, in _send_output
    self.send(msg)
  File "/opt/jython2.5b3/Lib/httplib.py", line 711, in send
    self.sock.sendall(str)
  File "/opt/jython2.5b3/Lib/httplib.py", line 711, in send
    self.sock.sendall(str)
  File "<string>", line 1, in sendall
  File "/opt/jython2.5b3/Lib/socket.py", line 867, in send
    numwritten = self.sock_impl.write(s)
  File "/opt/jython2.5b3/Lib/socket.py", line 867, in send
    numwritten = self.sock_impl.write(s)
  File "/opt/jython2.5b3/Lib/socket.py", line 323, in write
    return self._do_write_net(buf)
  File "/opt/jython2.5b3/Lib/socket.py", line 307, in _do_write_net
    self.jsocket.getOutputStream().write(buf)
TypeError: write(): 1st arg can't be coerced to int
>>>

Hmm, it looks like you have found a curious corner. It seems that when
respectJavaAccessibility=false the wrong overloaded function gets
picked. The Java docs for OutputStream list two functions named write
that take a single argument. One takes a byte array the other takes an
int. Clearly the one we want to be calling from that line is the byte
array version.

On a side note, the reason setting a timeout makes a difference here is
that the networking code has two modes of operation (1) When no socket
level timeouts are set it uses the java.nio classes, (2) when a timeout
is set it uses java.net classes, because nio doesn't support timeouts.

Probably related to Issue1285

Potential fix for this over in issue1285 (just posted a patch over 
there), at least it seems to make things work for me.

works as of r6266, thanks to cgroves.

Closing, because fixed.