Issue1269872

classification
Title: REGRESSION: ConnectException not IOException?
Type: Severity: normal
Components: Core Versions:
Milestone:
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: cgroves, slamb
Priority: high Keywords:

Created on 2005-08-25.00:56:31 by slamb, last changed 2006-08-09.01:05:42 by cgroves.

Files
File name Uploaded Description Edit Remove
connect-io-exception.py slamb, 2005-08-25.00:56:31 Reproduction recipe
Messages
msg1028 (view) Author: Scott Lamb (slamb) Date: 2005-08-25.00:56:31
The attached script fails with Jython 2.2a1. It succeeds with Jython 
2.1.

For some reason, a ConnectException (which is a SocketException, 
which is an IOException) is falling through a try/except IOException, 
e block.

This occurs on this OS X Tiger 10.4.2 system:

[slamb@slamb-mac ~]$ uname -a
Darwin slamb-mac.dhcp.2wire.com 8.2.0 Darwin Kernel Version 
8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/
RELEASE_PPC Power Macintosh unknown PowerMac7,3 Darwin
[slamb@slamb-mac ~]$ java -version
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 
1.4.2_07-215)
Java HotSpot(TM) Client VM (build 1.4.2-50, mixed mode)
msg1029 (view) Author: Scott Lamb (slamb) Date: 2005-08-27.17:07:58
Logged In: YES 
user_id=360426

It looks like raising from Jython code a ConnectException, SocketException, or 
IOException works fine.

Raising from Java a ConnectException or SocketException does not. Raising an 
IOException works fine.
msg1030 (view) Author: Charlie Groves (cgroves) Date: 2006-08-09.01:05:42
Logged In: YES 
user_id=1174327

This is the same problem as 1531644.  With r2874 applied on
the 2.3 branch the test passes.  If that change is pulled
over to the trunk this should be fixed.
History
Date User Action Args
2005-08-25 00:56:31slambcreate