Community
Participate
Working Groups
Build Identifier: 3.0.0.M06 When I try to start the latest milestone 6 from within Eclipse an exception is thrown and SSH is not available. When I start Virgo from the filesystem everything works as expected and I can connect to Virgo via SSH. Reproducible: Always
Created attachment 199170 [details] The serviceability log The exceptions start at line 891 and 1183
(In reply to comment #1) > Created attachment 199170 [details] > The serviceability log > > The exceptions start at line 891 and 1183 One more thing I am using Eclipse 3.7, Spring IDE 2.7.0 and Virgo Tooling 1.0.0.201106292003-SNAPSHOT.
Deferring as this is a tooling fix. It should be possible to work around this bug by specifying some extra parameters in the runtime configuration.
What would those parameters be? Would they interfere with non-ssh case if we included them in all configs? Assuming so, we could provide a checkbox for using SSH in the Server Runtime UI.
(In reply to comment #4) > What would those parameters be? Would they interfere with non-ssh case if we > included them in all configs? Assuming so, we could provide a checkbox for > using SSH in the Server Runtime UI. Hi, Currently in 3.5 the following properties are defined for the ssh: these 2 are in configuration/config.ini: osgi.console.ssh.useDefaultSecureStorage=false osgi.console.useConfigAdmin=true these 2 are in dmk.bat -Dssh.server.keystore="%CONFIG_DIR%/hostkey.ser" -Djava.security.auth.login.config="%CONFIG_DIR%\org.eclipse.virgo.kernel.authentication.config" In addition, in configuration and repository/ext folders there are osgi.console.properties files, which define some properties for the console. The properties above should be available when Virgo is run. Does the tooling uses config.ini and dmk.bat as they are in the Virgo installation? If it does, then the properties should come from there, otherwise the tooling should set them.
(In reply to comment #5) > Does the tooling uses config.ini and dmk.bat as they are in the Virgo installation? The tooling does not use dmk.bat. That much I know. ;-)
Frieder, sorry for taking so long to get back to you on this -- just missed that I had the reply saved but not submitted.. (In reply to comment #6) > (In reply to comment #5) > > Does the tooling uses config.ini and dmk.bat as they are in the Virgo > installation? > > The tooling does not use dmk.bat. That much I know. ;-) Right. :). Well I just checked and they appear in dmk.sh as well. :D (In reply to comment #5) > (In reply to comment #4) > The properties above should be available when Virgo is run. Does the tooling > uses config.ini and dmk.bat as they are in the Virgo installation? If it does, > then the properties should come from there, otherwise the tooling should set > them. So, both values are already being set, but the keystore setting is only set for Virgo 3.5 servers. Is that what you're using?
See related bug 351328 which is probably the cause. I won't close until we can test that.
(In reply to comment #8) > See related bug 351328 which is probably the cause. I won't close until we can > test that. As can be seen from the log, the exception is: Cannot start ssh: Property org.eclipse.equinox.console.jaas.file is not set; cannot use JAAS authentication [2011-07-06 11:09:20.284] ERROR ManagedService Update Queue System.err java.lang.IllegalArgumentException: Property org.eclipse.equinox.console.jaas.file is not set; cannot use JAAS authentication So if the property is set, and the server is Virgo 3.5, SSH should work. If it fails, it should be with another problem. I think that this is not related to bug 351328, at least the exception from the log.
I wasn't able to reproduce this issue with: Eclipse Virgo Tools 1.0.1.201408222103-SNAPSHOT Eclipse Virgo Server for Apache Tomcat 3.6.3.RELEASE Please reopen if need be.
