Support Questions

Find answers, ask questions, and share your expertise

Exception IllegalStateException: nested jar URLs not supported ..MalformedURLException

avatar
New Contributor

Running Spring Boot application running in Docker where the application is having a jive jdbc connection and writing to hive db.
The application is working fine in standalone. The issue happens in the docker container. The docker container starts , gets connected to the hive db but throws exception
executing query with Exception IllegalStateException: nested jar URLs not supported ..MalformedURLException..on the Hive driver

3 REPLIES 3

avatar
Community Manager

@rosejo Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our Hive experts @smruti @Shmoo  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.


Regards,

Diana Torres,
Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:

avatar
Expert Contributor

Hi @rosejo , the IllegalStateException accompanied by MalformedURLException related to nested JAR URLs indicates a problem with handling specific URL formats, typically within a Java environment. This issue often arises when an application classloader does not support the nested structure of JAR files directly referenced within a JAR URL, which is relatively common in environments using frameworks or libraries that dynamically load classes from JAR files.

Could you tell us if you are using the Cloudera JDBC Hive driver connector?
You can download the driver from here:
https://www.cloudera.com/downloads/connectors/hive/jdbc/2-6-26.html

In case you are using, please check if it's the latest version and the below points to fix the issue:

  • Ensure the classloader being used supports the JAR URL format required by the application. Some environments or containers may need specific configuration or a different classloader to handle nested JARs.
  • Check if unpacking the nested JAR files into a single structure helps resolve the issue, as some environments work better with flat directory structures rather than nested JAR files.
  • Verify if there’s an update or configuration option available in the framework or library being used that can handle nested JARs properly.

Please let us know if this answer your question?

Regards,

Cristian Barrueco

avatar
Community Manager

@rosejo Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks.


Regards,

Diana Torres,
Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community: