Troubleshooting DataStax Studio

Fixing problems in DataStax Studio.

The DataStax Enterprise Help Center also provides troubleshooting information.

HTTP protocol

DataStax Studio does not run with HTTPS everywhere. Preface the URL used to run DataStax Studio with HTTP and not HTTPS.

Binding to localhost on a cloud deployment

By default, Studio binds itself to the IP address 127.0.0.1 (or localhost). If running in the cloud, this prevents Studio from accepting connections from external addresses.When installing, change the address to which Studio binds itself to that of the host it is running on. If you have already installed Studio in the cloud using localhost, you can change the value in the conf/configuration.yaml file to the host's IP address.

Studio UI behaves strangely after upgrade

If you leave an old Studio session open in a browser, using an older version of Studio, and then upgrade to a new version, you can experience strange behavior. This is caused by caching in the browser. You can solve this problem by force-loading the index.html page. For example, if using the Chrome browser, you can navigate to the top-level index.html page and click on the refresh button while holding down the control key.

Starting Studio on Windows 7

While running Studio on the Microsoft Windows 7 operating system, out-of-date libraries can prevent system-specific JNI libraries from being loaded correctly. The result is the following stack trace:

leveldbjni-64-
1-6036870325998847314.8: Can't find dependent libraries]
        at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
        at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
        at org.fusesource.leveldbjni.JniDBFactory.<clinit>(JniDBFactory.java:48)
        at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog.<init>(Level
dbEventLog.scala:97)
        at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog$$anonfun$7.a
pply(LeveldbEventLog.scala:358)
        at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog$$anonfun$7.a
pply(LeveldbEventLog.scala:358)
        at akka.actor.TypedCreatorFunctionConsumer.produce(IndirectActorProducer
.scala:87)
You can fix this problem by updating the Microsoft Visual C++ 2010 Redistributable Package libraries in question: