的Windows Azure Java SDK的密鑰存儲路徑問題

我試圖建立Windows Azure中的Java SDK在Windows 7計算機跟着他們的維基設置頁面 https://github.com/Azure/azure-sdk-for-java/wiki/Devbox-Setup 的Windows Azure Java SDK的密鑰存儲路徑問題

當我運行測試用例/試圖訪問Azure的REST Web服務URLS ，低於錯誤。

set management.keystore.path=E:/Program Files (x86)/Java/jdk1.7.0_51/jre/lib/security/clientcert.jks

的Windows Azure SDK的Java密鑰庫路徑問題

java.lang.IllegalArgumentException: The keystore path cannot be null or empty. 
    at com.microsoft.windowsazure.core.utils.SSLContextFactory.create(SSLContextFactory.java:86) 
    at com.microsoft.windowsazure.core.utils.SSLContextFactory.create(SSLContextFactory.java:60) 
    at com.microsoft.windowsazure.credentials.CertificateCloudCredentials.applyConfig(CertificateCloudCredentials.java:128) 
    at com.microsoft.windowsazure.core.pipeline.apache.Exports$2.create(Exports.java:51) 
    at com.microsoft.windowsazure.core.pipeline.apache.Exports$2.create(Exports.java:1) 
    at com.microsoft.windowsazure.core.DefaultBuilder.build(DefaultBuilder.java:200) 
    at com.microsoft.windowsazure.core.pipeline.apache.Exports$3.create(Exports.java:65) 
    at com.microsoft.windowsazure.core.pipeline.apache.Exports$3.create(Exports.java:1) 
    at com.microsoft.windowsazure.core.DefaultBuilder.build(DefaultBuilder.java:200) 
    at com.microsoft.windowsazure.core.DefaultBuilder$1.create(DefaultBuilder.java:138) 
    at com.microsoft.windowsazure.core.DefaultBuilder.build(DefaultBuilder.java:200) 
    at com.microsoft.windowsazure.Configuration.create(Configuration.java:113) 
    at com.microsoft.windowsazure.management.storage.StorageManagementService.create(StorageManagementService.java:47) 
    at com.microsoft.windowsazure.management.compute.ComputeManagementIntegrationTestBase.createStorageManagementClient(ComputeManagementIntegrationTestBase.java:63) 
    at com.microsoft.windowsazure.management.compute.VirtualMachineOperationsTests.setup(VirtualMachineOperationsTests.java:61) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
    at java.lang.reflect.Method.invoke(Unknown Source) 
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) 
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) 
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) 
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) 
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 
    at org.junit.runners.ParentRunner.run(ParentRunner.java:309) 
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) 
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) 

java.lang.NullPointerException 
    at com.microsoft.windowsazure.management.compute.VirtualMachineOperationsTests.cleanHostedService(VirtualMachineOperationsTests.java:452) 
    at com.microsoft.windowsazure.management.compute.VirtualMachineOperationsTests.cleanup(VirtualMachineOperationsTests.java:79) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
    at java.lang.reflect.Method.invoke(Unknown Source) 
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) 
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) 
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) 
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) 
    at org.junit.runners.ParentRunner.run(ParentRunner.java:309) 
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) 
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

來源

2014-10-16 Yarish Kumar

嘗試切換到Java SDK的最新版本。我寫了一篇非常基本的指導性文章，幫助您解決JKS問題。看起來你正在使用的命名空間來自早期版本。

http://azure.microsoft.com/blog/2014/09/15/getting-started-with-the-azure-java-management-libraries/

來源

2014-10-17 06:33:05

這種簡單的Hello World樣的程序爲我工作 - 因爲你是硬編碼JKS文件的路徑和密碼。但在Azure Java SDK中，它被設置爲環境變量，Azure java SDK無法正確讀取它。我請求你修復它。非常感謝：） – 2014-10-21 08:19:29

的Windows Azure Java SDK的密鑰存儲路徑問題

回答

相關問題