Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
java.lang.NoClassDefFoundError: Could not initialize class com.amazonaws.services.s3.internal.ServiceUtils
See original GitHub issueI am building a spark project using scala in Intellij. I have added the following dependencies:
spark-redshift_2.10-0.5.1-SNAPSHOT RedshiftJDBC41-1.1.7.1007 httpcore-4.4.3 httpclient-4.5.1 aws-java-sdk-s3-1.10.23-SNAPSHOT aws-java-sdk-core-1.10.23-SNAPSHOT
I am recieving the following error: java.lang.NoClassDefFoundError: Could not initialize class com.amazonaws.services.s3.internal.ServiceUtils
where running val df = sqlContext.read.foramat(“com.databricks.spark.redshift”) .option(“url”, “jdbc:redshift://AWS_SERVER:5439/warehouse?user=USER&password=PWD”) .option(“dbtable”, “fact_time”) .option(“tempdir”, “s3n://bucket/path”) .load()
df.show()
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Based on the stacktrace, my hunch is that this is being caused by an exception in the
com.amazonaws.services.s3.internal.ServiceUtilsclass’s static initialization code. According to http://mvnrepository.com/artifact/com.amazonaws/aws-java-sdk-core/1.10.22,aws-java-sdk-corehas additional dependencies which you have not included in your project. Can you try including an appropriate version ofjoda-timeandcommons-loggingto see if that fixes things?My hunch is that ServiceUtils is trying to call a DateUtils method via its static initializer, which is failing due to missing
joda-timeclasses.Glad to hear that you were able to get things working!
In the future, I’d like to relax the requirement that the S3 bucket and Redshift cluster belong to the same region; please follow #87 to track progress on that issue.