This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 83971 - more informative message when the bpel debugger cannot attach is needed
Summary: more informative message when the bpel debugger cannot attach is needed
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Alexander Zgursky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-31 22:48 UTC by lchang
Modified: 2006-10-13 11:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 lchang 2006-08-31 22:48:01 UTC 
Description:  If you can't attach to the debugger because it hasn't been 
enabled, a more informative message should be given to the user:

Steps to reproduce:
1.  Build and deploy a BPEL Project
2.  For the BPEL SE ensure that the Debug Enabled property = false
3.  Open the .bpel source fro mthe BPEL Project
4.  Click on Attach Debugger and select BPEL Debugger and the Debug Port that 
the SE is assigned to. (default 3343)

Result:  The output message just shows,
14:35:53 Attached to localhost: 3343
14:36:11 Debug session finished

Expected Result:  It would be better to give the user a more informative 
message such as: "the debugger can not attach to the port" or "the debugger 
cannot be attached.  Possible reasons could be...1) wrong port 2) debug is 
disabled" ??  (Anyway, someone else besides me should come up with a better 
message.)
Comment 1 Alexander Zgursky 2006-09-22 04:57:04 UTC 
Fixed
Comment 2 deepakhp 2006-09-26 07:19:21 UTC 
Verified with 060925 build.
I get the following error message when I try to attach the debugger.
11:46:39 Connecting to localhost:3343
11:47:01 Unable to start a debug session : Unable to connect to localhost:3343 :
Connection timed out: connect

Is this the new expected behavior?
Comment 3 Alexander Zgursky 2006-09-26 08:42:38 UTC 
Yes, this is the new expected behaivor.
The new message contains the result of the "Attach..." operation - "Unable to
start a debug session", the reason - "Unable to connect to localhost:3343" and
the exception message - "Connection timed out: connect". I believe it's enough
for a user to figure out why the debug session didn't start.
Other messages are:
"Unable to start a debug session : Already connected to <host>:<port>"
"Debug session terminated : Target disconnected" - if connection is terminated
by the server or due to some network issues
"Stop connecting" - if user finishes the debug session which is in the
"Connecting" state
"Debug session finished" - if user finishes the debug session which is in the
"Running" state
"Connecting to <host>:<port>"
"Debug session started"
Comment 4 Michael Frisino 2006-09-26 09:59:09 UTC 
Attention, lets add this to the trouble shooting section of developer guide.
Comment 5 nrsunil 2006-09-26 13:05:24 UTC 
As per developer comments, I am marking as verified.