Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368072 - [dstore][ssl] no exception logged upon bind error
Summary: [dstore][ssl] no exception logged upon bind error
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.2.1   Edit
Hardware: Other other
: P3 normal (vote)
Target Milestone: 3.4 M5   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 368188
  Show dependency tree
 
Reported: 2012-01-06 22:41 EST by Onno Van den Troost CLA
Modified: 2012-02-06 09:38 EST (History)
1 user (show)

See Also:

Attachments
patch to log binding errors (2.59 KB, patch)
2012-01-09 12:28 EST, David McKnight CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Onno Van den Troost CLA 2012-01-06 22:41:26 EST 
Our customer gets 
Error binding socket on ports <port-range> 
when using SSL (it works when SSL is disabled).

One of our developers looked at it and said that OpenRSE just invokes a JVM method:
  serverSocket = sslContext.getServerSocketFactory().createServerSocket(i, backlog, bindAddr);

When an exception occurs in this method, the OpenRSE code will not log the exception.

It seems to me that we should modify OpenRSE to log the exception.

David D. helped us out and provided a dstore_core.jar with additional logging (to stderr), so you might want to check with him.

I would like to request that OpenRSE is modified to log the exception whether SSL is used or not. 

Please backport to v321.
Comment 1 David McKnight CLA 2012-01-09 12:28:22 EST 
Created attachment 209223 [details]
patch to log binding errors
Comment 2 David McKnight CLA 2012-01-09 12:29:27 EST 
I've committed a fix to log binding errors.  Does this need to be backported?
Comment 3 Onno Van den Troost CLA 2012-01-10 20:12:49 EST 
Please backport to v321.
Comment 4 David McKnight CLA 2012-01-10 20:47:44 EST 
(In reply to comment #3)
> Please backport to v321.

Yes, the backpack is bug 368188.