java.lang.InternalError: Could not start up the CDSA libraries.

Atlassian JIRA | James Dumay [Atlassian] | 6 years ago
  1. 0

    This should fix [a problem we see in the release process when talking to Amazon EC2|https://extranet.atlassian.com/display/BAMBOO/Release+Responsibilties]. Since the same code is used for Elastic Bamboo we could nail a potential support headache for customers using Elastic on Mac OS X. {code} 29-Sep-2010 11:14:22 [INFO] CSSM_ModuleLoad(): CSSMERR_CSSM_INTERNAL_ERROR 29-Sep-2010 11:14:22 [INFO] [INFO] ------------------------------------------------------------------------ 29-Sep-2010 11:14:22 [INFO] [ERROR] FATAL ERROR 29-Sep-2010 11:14:22 [INFO] [INFO] ------------------------------------------------------------------------ 29-Sep-2010 11:14:22 [INFO] [INFO] Could not start up the CDSA libraries. 29-Sep-2010 11:14:22 [INFO] [INFO] ------------------------------------------------------------------------ 29-Sep-2010 11:14:22 [INFO] [INFO] Trace 29-Sep-2010 11:14:22 [INFO] java.lang.InternalError: Could not start up the CDSA libraries. 29-Sep-2010 11:14:22 [INFO] at java.lang.ClassLoader$NativeLibrary.load(Native Method) 29-Sep-2010 11:14:22 [INFO] at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1878) 29-Sep-2010 11:14:22 [INFO] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1779) 29-Sep-2010 11:14:22 [INFO] at java.lang.Runtime.loadLibrary0(Runtime.java:823) 29-Sep-2010 11:14:22 [INFO] at java.lang.System.loadLibrary(System.java:1045) 29-Sep-2010 11:14:22 [INFO] at com.apple.crypto.provider.HmacCore.<clinit>(HmacCore.java:26) 29-Sep-2010 11:14:22 [INFO] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 29-Sep-2010 11:14:22 [INFO] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 29-Sep-2010 11:14:22 [INFO] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 29-Sep-2010 11:14:22 [INFO] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 29-Sep-2010 11:14:22 [INFO] at java.lang.Class.newInstance0(Class.java:355) 29-Sep-2010 11:14:22 [INFO] at java.lang.Class.newInstance(Class.java:308) 29-Sep-2010 11:14:22 [INFO] at java.security.Provider$Service.newInstance(Provider.java:1221) 29-Sep-2010 11:14:22 [INFO] at javax.crypto.Mac.a(DashoA13*..) 29-Sep-2010 11:14:22 [INFO] at javax.crypto.Mac.init(DashoA13*..) 29-Sep-2010 11:14:22 [INFO] at com.xerox.amazonws.common.AWSConnection.encode(AWSConnection.java:153) 29-Sep-2010 11:14:22 [INFO] at com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection.java:301) {code}

    Atlassian JIRA | 6 years ago | James Dumay [Atlassian]
    java.lang.InternalError: Could not start up the CDSA libraries.
  2. 0

    This should fix [a problem we see in the release process when talking to Amazon EC2|https://extranet.atlassian.com/display/BAMBOO/Release+Responsibilties]. Since the same code is used for Elastic Bamboo we could nail a potential support headache for customers using Elastic on Mac OS X. {code} 29-Sep-2010 11:14:22 [INFO] CSSM_ModuleLoad(): CSSMERR_CSSM_INTERNAL_ERROR 29-Sep-2010 11:14:22 [INFO] [INFO] ------------------------------------------------------------------------ 29-Sep-2010 11:14:22 [INFO] [ERROR] FATAL ERROR 29-Sep-2010 11:14:22 [INFO] [INFO] ------------------------------------------------------------------------ 29-Sep-2010 11:14:22 [INFO] [INFO] Could not start up the CDSA libraries. 29-Sep-2010 11:14:22 [INFO] [INFO] ------------------------------------------------------------------------ 29-Sep-2010 11:14:22 [INFO] [INFO] Trace 29-Sep-2010 11:14:22 [INFO] java.lang.InternalError: Could not start up the CDSA libraries. 29-Sep-2010 11:14:22 [INFO] at java.lang.ClassLoader$NativeLibrary.load(Native Method) 29-Sep-2010 11:14:22 [INFO] at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1878) 29-Sep-2010 11:14:22 [INFO] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1779) 29-Sep-2010 11:14:22 [INFO] at java.lang.Runtime.loadLibrary0(Runtime.java:823) 29-Sep-2010 11:14:22 [INFO] at java.lang.System.loadLibrary(System.java:1045) 29-Sep-2010 11:14:22 [INFO] at com.apple.crypto.provider.HmacCore.<clinit>(HmacCore.java:26) 29-Sep-2010 11:14:22 [INFO] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 29-Sep-2010 11:14:22 [INFO] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 29-Sep-2010 11:14:22 [INFO] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 29-Sep-2010 11:14:22 [INFO] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 29-Sep-2010 11:14:22 [INFO] at java.lang.Class.newInstance0(Class.java:355) 29-Sep-2010 11:14:22 [INFO] at java.lang.Class.newInstance(Class.java:308) 29-Sep-2010 11:14:22 [INFO] at java.security.Provider$Service.newInstance(Provider.java:1221) 29-Sep-2010 11:14:22 [INFO] at javax.crypto.Mac.a(DashoA13*..) 29-Sep-2010 11:14:22 [INFO] at javax.crypto.Mac.init(DashoA13*..) 29-Sep-2010 11:14:22 [INFO] at com.xerox.amazonws.common.AWSConnection.encode(AWSConnection.java:153) 29-Sep-2010 11:14:22 [INFO] at com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection.java:301) {code}

    Atlassian JIRA | 6 years ago | James Dumay [Atlassian]
    java.lang.InternalError: Could not start up the CDSA libraries.
  3. 0

    Bug 199020 – [launcher] Can't start the AWT while using new eclipse native launcher in 3.3

    eclipse.org | 1 year ago
    org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: Not implemented [need SWT compatibility pack from Apple] (java.lang.InternalError: Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line))
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Can't start shell (mac os 10.5)

    Google Groups | 9 years ago | hammett
    java.lang.InternalError: Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line
  6. 0

    doma

    blogspot.com | 1 year ago
    java.lang.InternalError: Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's Info.plist or on the command line

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.InternalError

      Could not start up the CDSA libraries.

      at java.lang.ClassLoader$NativeLibrary.load()
    2. Java RT
      System.loadLibrary
      1. java.lang.ClassLoader$NativeLibrary.load(Native Method)
      2. java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1878)
      3. java.lang.ClassLoader.loadLibrary(ClassLoader.java:1779)
      4. java.lang.Runtime.loadLibrary0(Runtime.java:823)
      5. java.lang.System.loadLibrary(System.java:1045)
      5 frames
    3. com.apple.crypto
      HmacCore.<clinit>
      1. com.apple.crypto.provider.HmacCore.<clinit>(HmacCore.java:26)
      1 frame
    4. Java RT
      Provider$Service.newInstance
      1. sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      2. sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      3. sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      4. java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      5. java.lang.Class.newInstance0(Class.java:355)
      6. java.lang.Class.newInstance(Class.java:308)
      7. java.security.Provider$Service.newInstance(Provider.java:1221)
      7 frames