It is not possible to start Karaf from JBDS unless it is first started from cmd line previously. Might be related to authentication issues?
Jira - please give more details on exactly what you tried.
Created attachment 898077 [details] JBDS 7.1.1.GA/ JBDSIS 7.0.1.GA - Karaf started from JBDS JBDS having started karaf 2.3.2
Could not verify with JBDS 7.1.1.GA/ JBDSIS 7.0.1.GA. See attachment. Please use https://issues.jboss.org/browse/FUSETOOLS for FuseIDE issues. Thanks
Hi, I just tried to reproduce the issue. Steps 1) Install JBDS 7.1.1.GA 2) Install JBDS-IS from https://devstudio.jboss.com/updates/7.0/integration-stack/ 3) Install jboss-fuse-full-6.1.0.redhat-379.zip 4) Add a JBoss Fuse 6.1 runtime and server into JBDS 5) Start the server Shell Window contains Error connecting 0.0.0.0:8101 : SSH client error: java.net.ConnectException: Connection refused Error connecting 0.0.0.0:8101 : SSH client error: java.net.ConnectException: Connection refused Error connecting 0.0.0.0:8101 : SSH Authentication failed. and the server STARTS but the Shell window is not connected - sorry for inaccurate description It seems that the problem is a missing admin user. If I start Fuse from CMD line, execute esb:create-admin-user then I can connect from JBDS. So the JBDS should either configure the admin user when not preset or infor developer what is necessary to be done.
Sorry for bouncing this one around. - I was able to verify your issue. It's the user's responsibility to edit the etc/users.properties to uncomment out the "admin" user, issue the create-admin-user command in a shell instance of the server or provide their own credentials. We talked about extending the error diagnostic but the issue will be moot with the new server adapters. Ultimately the user's responsible for setting up the fabric before starting the fuse tooling.
Sorry for re-opening - a last question, as I mentioned in the comment above. Maybe you could add a hint into error message - like 'Are security credentials configured in JBoss Fuse runtime?' as a paert of error message
Is this is still an issue then need to raise a jira in FUSETOOLS.
Jira issue was raised. See https://issues.jboss.org/browse/FUSETOOLS-1397