Bug 1059836 – [GSS] (6.3.0) Remote Naming communication exception should be thrown on ConnectException

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1059836 - [GSS] (6.3.0) Remote Naming communication exception should be thrown on ConnectException

Summary:	[GSS] (6.3.0) Remote Naming communication exception should be thrown on Conne...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Naming (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR1
Target Release:	EAP 6.3.0
Assigned To:	Brad Maxwell
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1024153 1059837
	Show dependency tree / graph

Reported:	2014-01-30 14:09 EST by Brad Maxwell
Modified:	2014-06-28 11:42 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	In previous versions of JBoss EAP, a generic `javax.naming.NamingException` was being thrown when a `java.net.ConnectException` occurred instead of the more specific `javax.naming.CommunicationException`. This release includes a change that ensures a `javax.naming.CommunicationException` is thrown when a connection exception occurs. `CommunicationException` is a subclass of `NamingException`, so any code that previously caught a `NamingException` will still work as expected.
Story Points:	---
Clone Of:
Clones:	1059837 (view as bug list)
Environment:
Last Closed:	2014-06-28 11:42:53 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-2839	Major	Closed	Remote Naming communication exception should be thrown on ConnectException	2017-12-18 21:23 EST

Groups: None (edit)

Description Brad Maxwell 2014-01-30 14:09:06 EST

Use right exception type for communication problem , javax.naming.CommunicationException should be thrown instead of javax.naming.NamingException

Comment 1 JBoss JIRA Server 2014-01-30 15:04:26 EST

Brad Maxwell <bmaxwell@redhat.com> updated the status of jira WFLY-2839 to Resolved

Comment 2 Rostislav Svoboda 2014-02-04 06:30:22 EST

http://docs.oracle.com/javase/7/docs/api/javax/naming/CommunicationException.html

Customers apps (try - catch blocks) won't be affected by throwing CommunicationException instead of NamingException

Comment 3 Brad Maxwell 2014-02-04 12:23:54 EST

Yes, originally it was a generic NamingException, this change just uses sub classes of NamingException which are more specific, so any customer who was catching the NamingException will not be affected, they will still be caught, they will just provide information about the real issue.

Comment 5 Jan Martiska 2014-04-09 08:58:32 EDT

Verified with EAP 6.3.0.ER1 / jboss-remote-naming 1.0.8.Final-redhat-1

Note You need to log in before you can comment on or make changes to this bug.