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.
Steps to reproduce: - add a remote Solaris host and choose SunStudio tool collection - create any remote project (e.g. Quote) - build the project - do step into Result: User is asked to provide a password then Information window appears with the message "cannot create tunnel -- Tunneler: Couldn't get port after 40 attempts".
This is the current restriction of DBX integration for 6.8. If port forwarding is disabled => DBX debugging is not supported. I think, we should waive it.
I think we should provide a short guidance explaining the problem and providing a solution. Now it's absolutely unclear.
At minimum we need to provide a helpful message to a user.
some info: - the dialog is shown by code in t-common.base - t-common does own manage of jsch session (=> password is asked twice) - displayed strings are hardcoded we need: - change t-common to allow pass it jsch Session (to prevent two password dialogs) - change text to be understandable by unexperienced users with tip how to fix the problem - make strings localizable in t-common
Ivan, let's change t-common and provide user friendly message.
posponed until we have dbx support in NB
move dbx related issues into dbx-gui component
mark issues as not fixed
port forwarding is supposed to be on by default. It says so in the O'Reily book :-) The fact that it is not enabled by default on Solaris is a bug: CR 6830483. We'll still have to give a useful error message until this is fixed.
I've lost several hours trying to decrypt message from error dialog. Please, change it to something user understandable, not developer's trace + instruction how to fix the issue.
Fix for CR 6830483 is available in snv_118
df572feaf6c1 Improved error message. It now looks like this: Cannot get a tunnel to {0} on ssh port {1}.\n\ Possible remedies:\n\ - Ensure that ''sshd'' is running on ''{0}''.\n\ - Ensure that ''AllowTcpForwarding'' is set to ''yes'' in ''/etc/ssh/ssh d_config'' on ''{0}''.\n\ - Ensure that sshd on {0} is listening on port {1}.\n\ Additional info:\n\ \t{2} Error messages in the following cases could still use some improvement: - enabling ss_attach when port forwarding is off. - incorrect sunstudio location One oddity. Why are we getting an error message about dbx glue connection as opposed to a spawn startup error? After all don't we first start dbx and then connect to it? The reason is that in master mode we first need to allocate a tunnelled listening port (Surrogate.callback_remote_addr()) and then we start dbx. It's callback_remote_addr() which fails.