Description of problem:
For scalable jbosseap-6.0/jbossews-2.0 app, when rhc threaddump the app, would get duplicate threaddump message when the app have more than one gear.

For scalable ruby-1.8/ruby-1.9 app, if it has more than one gears, would be told "The threaddump command is not supported on scalable applications"

Version-Release number of selected component (if applicable):
http://download.lab.bos.redhat.com/rel-eng/OpenShiftEnterprise/1.2/2013-06-26.3/


How reproducible:
Always

Steps to Reproduce:
1.Create a scalable jbossews-2.0 app named "app6", do threaddump

[root@dhcp-8-133 workspace]# rhc threaddump app6
Success
The thread dump file will be available via: rhc tail app6 -f */logs/catalina.out -o '-n 250'


2.Scale-up this app, and do threaddump

[root@dhcp-8-133 workspace]# rhc threaddump app6
Success
The thread dump file will be available via: rhc tail app6 -f */logs/catalina.out -o '-n 250'
Success
The thread dump file will be available via: rhc tail app6 -f */logs/catalina.out -o '-n 250'



3. Create a scalable ruby-1.8 app named ruby18s ,visit it and do threaddump

[root@dhcp-8-133 workspace]# rhc threaddump ruby18s
Success
The thread dump file will be available via: rhc tail ruby18s -f /var/lib/openshift/51cbf9690759864b250000bd/ruby//logs//error_log-20130627-* -o '-n 250'


4. Scale-up this app twice, and do threaddump

[root@dhcp-8-133 workspace]# rhc threaddump ruby18s
The threaddump command is not supported on scalable applications.
The threaddump command is not supported on scalable applications.


Actual results:

Expected results:
We should keep consistent when dealing with scalable jboss/ruby apps, and give a correct prompt just like what the comment said in  https://bugzilla.redhat.com/show_bug.cgi?id=974933

Additional info: