[ https://issues.jboss.org/browse/JBIDE-8354?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8354: ------------------------------------ Summary: Launch instance wizard: NPE reported (gracefully in dialog) when launching instance and .pem is not stored locally (was: Connecting to dc instance via RSE ends with NPE when .pem is not stored locally) Steps to Reproduce: 1. have an ec2 cloud 2. open launch instance wizard 3. create new key , but do not store the private part to your local disk 4. enable creating RSE connection, hit Finish 5. After instance is launched, RSE is connecting. It asks for password (enter anyhing) Currently: It takes 5minutes to fihish connecting . In the end an error with NPE is reported. Expected: Error is reported, but it says that the credentials were not valid. was: 1. have an ec2 cloud 2. open launch instance wizard 3. create new key , but do not store the private part to your local disk 4. enable creating RSE connection, hit Finish Currently: After instance is launched, RSE is connecting. It asks for password (enter anyhing), then you accept server keys. Then it takes quite 5minutes to fihish the connecting background job. In the end an error with NPE is reported. Expected: Once (wrong) password is given or authentication is canceled, RSE should stop trying to connect (it won't succeed anyway), no NPE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8354?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8354: ------------------------------------ Fix Version/s: 3.2.1 3.3.0.M1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8354?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8354: ------------------------------------ Steps to Reproduce: You can also replicate this issue by simply providing bad user or pw as stated in JBIDE-8356 1. have an ec2 cloud 2. open launch instance wizard 3. create new key , but do not store the private part to your local disk 4. enable creating RSE connection, hit Finish 5. After instance is launched, RSE is connecting. It asks for password (enter anyhing) Currently: It takes 5minutes to fihish connecting . In the end an error with NPE is reported. Expected: Error is reported, but it says that the credentials were not valid. was: 1. have an ec2 cloud 2. open launch instance wizard 3. create new key , but do not store the private part to your local disk 4. enable creating RSE connection, hit Finish 5. After instance is launched, RSE is connecting. It asks for password (enter anyhing) Currently: It takes 5minutes to fihish connecting . In the end an error with NPE is reported. Expected: Error is reported, but it says that the credentials were not valid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8354?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8354: ------------------------------------ Attachment: CreateRSEFromInstanceJob.java.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8354?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-8354: ------------------------------------- ok, NPE is gone on v0.0.1.v20110503-1752-H179-M1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira