com/typesafe/config/ConfigException : Unsupported major.minor version

最新推荐文章于 2025-10-07 06:50:38 发布
原创 最新推荐文章于 2025-10-07 06:50:38 发布 · 1.3k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#elasticsearch

本文介绍了解决启动Cerebro时出现的UnsupportedClassVersionError错误的方法，该问题通常是由于JDK版本不兼容导致，解决方案为安装JDK 8。

启动cerebro的时候报错：

Exception in thread “main” java.lang.UnsupportedClassVersionError: com/typesafe/config/ConfigException : Unsupported major.minor version 52.0

解决方法：
安装jdk8

com.typesafe.config
ruangongtaotao的专栏
02-18 986
com.typesafe.config 提供了一套 标准化、高可维护性的配置管理方案，尤其适合需要灵活配置、多环境支持、与 Scala/Java 生态深度集成的应用（如 Akka、Play Framework、Lagom 等）。com.typesafe.config 是 Typesafe Config 库的核心包，主要用于 统一、灵活地管理应用程序配置，支持从多种格式（如 HOCON、JSON、Java Properties）加载配置，并提供类型安全的访问接口。统一配置管理 微服务架构中多模块共享配置。
com.typesafe.config.Config
gjq5464的博客
07-27 1359
com.typesafe.config.ConfigObject; com.typesafe.config.Config; 1.在pom文件中引入依赖 <dependency> <groupId>com.typesafe</groupId> <artifactId>config</artifactId> <version>1.3.3</vers
com/typesafe/config/ConfigException :Unsupported major.minor version 52.0解决办法
hexinghua0126的博客
04-11 1343
1.首先解释一下：stanford parser和jdk版本对应关系J2SE 8 = 52, J2SE 7 = 51, J2SE 6.0 = 50, J2SE 5.0 = 49, JDK 1.4 = 48, JDK 1.3 = 47, JDK 1.2 = 46, JDK 1.1 = 45Unsupported major.minor version 52.0: 看到Unsupported你是不是会...
Typesafe Config 配置管理示例
最新发布
Leon_Jinhai_Sun的博客
10-07 324
下面是最新依赖的 Maven 坐标和一个详细的使用示例，希望能帮助你快速上手。
config包之ExceptionConfig浅析
jason_z的专栏
09-24 1284
org.apache.status.config.ExceptionConfig浅析struts-config.xml文件中每个元素都对应着一个org.apache.struts.config.ExceptionConfig对象元素用于配置异常处理。它可以包含零个或者多个元素，在元素中定义的代表全局异常。元素中的className属性是指定和元素对应的配置类，默认为org.apache.str
com.typesafe.config.ConfigException$Missing读取配置文件报错
weixin_44069378的博客
08-24 3727
在使用ConfigFactory.load读取配置文件的时候，会报如下错误： com.typesafe.config.ConfigException$Missing：No configuration setting found for key ‘xx’ 这是由于配置文件名称不对引起的。 ConfigFactory.load读取文件必须是以下名称： application.conf, application.json,application.properties或者以.properties,.conf,.js
JSP内置对象-----config,Exception
weixin_34342905的博客
08-10 169
<%@ page language="java" contentType="text/html; charset=utf-8" pageEncoding="utf-8" errorPage="exception.jsp"%><!-- errorPage="exception.jsp" 当抛出异常时，交给页面处理 --> <!DOCTYPE h...
Caused by: com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'kafka' at com.typesafe.config.impl.SimpleConfig.findKeyOrNull(SimpleConfig.java:152) ~[flink-dist_2.12-1.13.0.jar:1.13.0] at com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:145) ~[flink-dist_2.12-1.13.0.jar:1.13.0] at com.typesafe.config.impl.SimpleConfig.findOrNull(SimpleConfig.java:172) ~[flink-dist_2.12-1.13.0.jar:1.13.0] at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:184) ~[flink-dist_2.12-1.13.0.jar:1.13.0] at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:189) ~[flink-dist_2.12-1.13.0.jar:1.13.0] at com.typesafe.config.impl.SimpleConfig.getString(SimpleConfig.java:246) ~[flink-dist_2.12-1.13.0.jar:1.13.0] at com.huawei.it.x.flink.common.config.KafkaConfig.<init>(KafkaConfig.java:50) ~[XMultiSignalDtcVhrProcessFlinkStream.jar:?]
08-20
我们遇到了一个配置缺失的错误：`com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'kafka'`。这个错误发生在Flink作业中，具体是在尝试加载Kafka配置时，没有找到名为'kafka'...
config-1.2.1-API文档-中文版.zip
06-05
Maven坐标：com.typesafe:config:1.2.1； 标签：typesafe、config、中文文档、jar包、java； 使用方法：解压翻译后的API文档，用浏览器打开“index.html”文件，即可纵览文档内容。 人性化翻译，文档中的代码和结构...
[WARNING] The requested profile "yarn-build" could not be activated because it does not exist. [ERROR] Failed to execute goal on project application: Could not collect dependencies for project org.thingsboard.mqtt-broker:application:jar:2.2.0-SNAPSHOT [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker:dao:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker:dao:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker:dao:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker.common.integration:cluster-integration-api:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker.common.integration:cluster-integration-api:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker.common.integration:cluster-integration-api:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker.common:actor:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker.common:actor:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker.common:actor:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker.common:queue:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker.common:queue:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker.common:queue:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker.common:util:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker.common:util:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker.common:util:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker.common:stats:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker.common:stats:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker.common:stats:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker:ui-ngx:jar:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker:ui-ngx:pom:2.2.0-SNAPSHOT (absent): Could not transfer artifact org.thingsboard.mqtt-broker:ui-ngx:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] Failed to read artifact descriptor for org.thingsboard.mqtt-broker:dao:jar:tests:2.2.0-SNAPSHOT [ERROR] Caused by: The following artifacts could not be resolved: org.thingsboard.mqtt-broker:dao:pom:2.2.0-SNAPSHOT (absent): org.thingsboard.mqtt-broker:dao:pom:2.2.0-SNAPSHOT failed to transfer from https://repo.typesafe.com/typesafe/releases/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of typesafe has elapsed or updates are forced. Original error: Could not transfer artifact org.thingsboard.mqtt-broker:dao:pom:2.2.0-SNAPSHOT from/to typesafe (https://repo.typesafe.com/typesafe/releases/): Connection reset [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
07-03
Maven 构建失败提示 `Could not transfer artifact org.thingsboard.mqtt-broker` 并报告连接被重置（`Connection reset from repo.typesafe.com`），这通常表明在尝试从远程仓库下载依赖时发生了网络中断或 SSL/TLS...
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native librar
xu1314的专栏
12-11 2523
1. 启动nodemanager 在windows下从命令窗口启动nodemanager的方式，在命令窗口执行%MW_HOME%/wlserver/server/bin/startNodeManager.cmd[监听地址] [监听端口]，如：%MW_HOME%/wlserver/bin/startNodeManager.cmd127.0.0.1 5556。MW_HOME是安装Weblogic
spark-assembly linux下运行local模式缺失包
04-12
spark streaming job 打成jar包，在linux系统下运行local模式，报错： 18/04/12 14:14:18 ERROR SparkContext: Error initializing SparkContext. com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'akka.version' at com.typesafe.config.impl.SimpleConfig.findKey(SimpleConfig.java:124) at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:145) at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:151) at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:159) at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:164) at com.typesafe.config.impl.SimpleConfig.getString(SimpleConfig.java:206) at akka.actor.ActorSystem$Settings.<init>(ActorSystem.scala:169) at akka.actor.ActorSystemImpl.<init>(ActorSystem.scala:505) at akka.actor.ActorSystem$.apply(ActorSystem.scala:142) at akka.actor.ActorSystem$.apply(ActorSystem.scala:119) at org.apache.spark.util.AkkaUtils$.org$apache$spark$util$AkkaUtils$$doCreateActorSystem(AkkaUtils.scala:121) at org.apache.spark.util.AkkaUtils$$anonfun$1.apply(AkkaUtils.scala:53) at org.apache.spark.util.AkkaUtils$$anonfun$1.apply(AkkaUtils.scala:52) 补全spark-assembly jar包解决问题。 java -cp ./wd:./spark-assembly.jar:./spark-streaming-job.jar job-main
spring中的AopConfigException、NotAnAtAspectException出现的情况和解决方法
qq_42240540的博客
04-16 612
在这个示例中，@Aspect注解的类LoggingAspect定义了一个切点表达式serviceMethod()，并在@Before注解中使用该切点。在这个示例中，@Aspect注解的类LoggingAspect定义了一个切点表达式serviceMethod()，并在@Before注解中使用该切点。通常出现这个异常的情况是，被标注为@Aspect注解的类不符合AspectJ切面的语法要求，例如缺少必要的切点表达式等，且是AopConfigException的子类。
netty冲突 play sbt_com.typesafe.config.ConfigException $ Missing：找不到键'play'的配置设置...
weixin_39653442的博客
12-30 220
com.typesafe.config.ConfigException $ Missing：找不到键'play'的配置设置com.typesafe.config.ConfigException $ Missing：找不到com.typesafe.config.impl.SimpleConfig中键'play'的配置设置 . com.typesafe.com的com.typesafe.config...
解析Spring AopConfigException异常
博客
08-02 468
AopConfigException是Spring框架中的一个异常类，用于表示在配置AOP切面时出现的错误。错误的切面定义：切面定义中可能存在语法错误或不正确的配置。错误的切入点表达式：切入点表达式可能无法匹配任何连接点，或者包含无效的语法。无效的通知类型：使用了不受支持的通知类型，例如使用了@Before通知，但没有提供正确的参数。当AopConfigException异常被抛出时，它通常会包含详细的错误信息，以帮助我们定位问题所在。// 前置通知的逻辑 } // ...其他通知方法 }
使用typesafe报错：No configuration setting found for key ‘...‘
程研板的博客
08-28 2626
导入的包 <dependency> <groupId>com.typesafe</groupId> <artifactId>config</artifactId> <version>1.3.3</version> </dependency> 测试代码 import com.typesafe.config.{ConfigFactory,Config} object Config
关于使用typesafe报错 “No configuration setting found for key ‘xxx‘”
JinKla的博客
10-21 1353
使用typesafe加载配置文件时，报错无法定位key val load: Config = ConfigFactory.load val dataPath: String = load.getString("datapath") println(dataPath) 报错： 仔细检查，配置文件命名规范是以conf结尾，maven包也导入正确，最后逐个通过注释pom文件代码，定位到问题： <packaging>pom</packaging> 此行代码注释后
试用配置管理库typesafe.config
某先生的专栏
04-29 1万+
Typesafe的Config库，纯Java写成、零外部依赖、代码精简、功能灵活、API友好。支持Java properties、JSON、JSON超集格式HOCON以及环境变量。它也是Akka的配置管理库 Useage Typesafe的Config库，默认加载classpath下的application.conf,application.json和application.prope
Unsupported major.minor version 52.0解决办法
热门推荐
hchhan的博客
07-18 34万+
一、错误现象： 当改变了jdk版本时，在编译java时，会遇到Unsupported major.minor version错误。jdk版本和stanford parser对应关系 JDK版本和Java编译器内部的版本号 J2SE 8 = 52, J2SE 7 = 51, J2SE 6.0 = 50, J2SE 5.0 = 49, JDK 1.4 = 48, JDK 1.3 = 47, JD...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值