[JBIDE-8862] Determining driver for some existing but non-deltacloud URL takes very long - JBoss Issue Tracker

Details

Steps to Reproduce:

Hide

1. create a new connection
2. set for example 'http://www.seznam.cz' to URL
3. set url to running instance
3. Cancel the dialog
Currently: background job called 'Determining driver for cloud url www.seznam.cz' is still running even after correct url was already detected. When cancel is requested, job still runs. Job quits after about 5 minutes. I've been trying another URLs (redhat.com, jboss.org and these seem fine - job exits very fast)

Expected: job is able to detect (non)cloud quickly

Show
1. create a new connection 2. set for example 'http://www.seznam.cz' to URL 3. set url to running instance 3. Cancel the dialog Currently: background job called 'Determining driver for cloud url www.seznam.cz' is still running even after correct url was already detected. When cancel is requested, job still runs. Job quits after about 5 minutes. I've been trying another URLs (redhat.com, jboss.org and these seem fine - job exits very fast) Expected: job is able to detect (non)cloud quickly

is related to

JBIDE-12458 Removal of deltacloud from trunk

Hide

Permalink

Andre Dietisheim added a comment - 04/Sep/12 4:37 AM

we're not developing Deltacloud any longer. See ~~JBIDE-12458~~

Show

Andre Dietisheim added a comment - 04/Sep/12 4:37 AM we're not developing Deltacloud any longer. See JBIDE-12458