Bug 509096 - [doc] Remote Java Application page: connection limit 0 not explained
Summary: [doc] Remote Java Application page: connection limit 0 not explained
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Doc (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 4.8 RC1   Edit
Assignee: Sarika Sinha CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation
Depends on:
Blocks:
 
Reported: 2016-12-12 11:38 EST by Dani Megert CLA
Modified: 2018-05-14 10:30 EDT (History)
1 user (show)

See Also:

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 Dani Megert CLA 2016-12-12 11:38:37 EST 
4.7 M3.

From the N&N of M3:  The connection limit may be set to a fixed number, or 0

And the user knows this how?
Comment 1 Dani Megert CLA 2016-12-12 11:39:14 EST 
(In reply to Dani Megert from comment #0)
> 4.7 M3.
> 
> The connection limit may be set to a fixed number, or 0

The connection limit may be set to a fixed number, or 0 for unlimited connections.
Comment 2 Dani Megert CLA 2016-12-12 11:39:59 EST 
Also using F1 Help - no luck.
Comment 3 Sarika Sinha CLA 2017-01-06 05:16:26 EST 
Help content was changed via Bug 506343.

Are you not able to see under 
Java development user guide > Tasks > Running and Debugging > Remote Debugging

Using the remote Java application launch configuration 


The Standard (Socket Listen) connection type listens for incoming connections from a remote VM. It is typically used for debugging an application that spans multiple VMs, such as a distributed system. ◦ In the Port field of the Connect tab, type the port on your local machine where the remote VM should connect to. Generally, your host and this port is specified when the remote VM is launched.
◦ In the Connection limit field of the Connect tab, type the number of expected connections, or 0 to support an unlimited number of connections.
Comment 4 Dani Megert CLA 2017-02-03 11:57:09 EST 
Does not work for me.

It should be explained on the page.

The F1 Help gives:

Java application launch configuration
Remote debugging
Launching a Java Program

and I have to dig long to find the relevant information.
Comment 5 Sarika Sinha CLA 2017-02-07 03:52:39 EST 
This is working as before.
This commit has just added an explanation to the Standard (Socket Listen) connection type.
Comment 6 Sarika Sinha CLA 2017-03-07 00:07:36 EST 
Need to created more than 15 new String NLS variables, will do later.
Comment 7 Sarika Sinha CLA 2017-03-07 00:10:20 EST 
(In reply to Sarika Sinha from comment #6)
> Need to created more than 15 new String NLS variables, will do later.

Was meant for Bug 509095.


This needs a big change and everywhere it works like this, will look into it later.
Comment 8 Dani Megert CLA 2017-05-26 09:26:41 EDT 
Don't slip this again.
Comment 9 Sarika Sinha CLA 2017-08-10 00:29:04 EDT 
Can work on this only after Java 9 work is done.
Comment 10 Sarika Sinha CLA 2018-04-13 02:56:28 EDT 
Moving out of 4.8.
Comment 11 Dani Megert CLA 2018-04-23 10:40:58 EDT 
(In reply to Sarika Sinha from comment #10)
> Moving out of 4.8.

Please finally fix this during the 4.8 doc pass.
Comment 12 Eclipse Genie CLA 2018-05-11 07:15:18 EDT 
New Gerrit change created: https://git.eclipse.org/r/122474
Comment 14 Sarika Sinha CLA 2018-05-11 07:26:22 EDT 
The F1 will now display -


Using the remote Java application launch configuration
Remote debugging
Java application launch configuration
Launching a Java Program