【Jenkins】使用java -jar jenkins.war --httpPort=XXXX启动Jenkins报错【解决方案】

简介: 【Jenkins】使用java -jar jenkins.war --httpPort=XXXX启动Jenkins报错【解决方案】

使用java -jar jenkins.war --httpPort=XXXX启动Jenkins报错【解决方案】

👉欢迎关注博主【米码收割机】

👉一起学习C++、Python主流编程语言。

👉机器人、人工智能等相关领域开发技术。

👉主流开发、测试技能。



一. 启动Jenkins报错

错误1:错误描述

在cmd中,执行启动命令行:

java -jar jenkins.war --httpPort=8080

报错信息如下:

Main verifyJavaVersion

严重: Running with Java class version 63 which is not in the list of supported versions: [52, 55, 61]. Run with the --enable-future-java flag to enable such behavior. See https://jenkins.io/redirect/java-support/

java.lang.UnsupportedClassVersionError: 63.0

at Main.verifyJavaVersion(Main.java:147)

at Main.main(Main.java:108)

Jenkins requires Java versions [17, 8, 11] but you are running with Java 19 from D:\JDK-19

java.lang.UnsupportedClassVersionError: 63.0

at Main.verifyJavaVersion(Main.java:147)

at Main.main(Main.java:108)

错误1: 解决方案

根据提供的错误信息,您正在使用 Java 19,而 Jenkins 支持的 Java 版本为 8、11 和 17。为了解决此问题,您需要安装一个受支持的 Java 版本并将其设置为默认的 Java 版本。

1)安装JDK

下载并安装适合您操作系统的支持的 Java 版本(例如 JDK 8、11 或 17)。您可以从 Oracle 官方网站AdoptOpenJDK下载。

2)查看java版本

下载完成后,打开一个新的命令提示符窗口,运行以下命令以验证 Java 版本:

java -version

确保显示的版本与您安装的 JDK 版本相匹配。

3)重新启动 Jenkins

使用以下命令启动 Jenkins

java -jar jenkins.war --httpPort=8080

错误2:错误描述

在cmd中,执行启动命令行:

java -jar jenkins.war --httpPort=8080

报错信息如下:

Running from: D:\Jenkins\Jenkins.war

webroot: $user.home/.jenkins

2023-05-06 09:08:57.518+0000 [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @301ms to org.eclipse.jetty.util.log.JavaUtilLog

2023-05-06 09:08:57.572+0000 [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file

2023-05-06 09:08:57.586+0000 [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath

2023-05-06 09:08:57.644+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.45.v20220203; built: 2022-02-03T09:14:34.105Z; git: 4a0c91c0be53805e3fcffdcdcc9587d5301863db; jvm 17.0.7+7

2023-05-06 09:08:57.925+0000 [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet

2023-05-06 09:08:57.955+0000 [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0

2023-05-06 09:08:57.956+0000 [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults

2023-05-06 09:08:57.957+0000 [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 660000ms

2023-05-06 09:08:58.287+0000 [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: C:\Users\mech-mind_lcl.jenkins found at: $user.home/.jenkins

2023-05-06 09:08:58.365+0000 [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@32057e6{Jenkins v2.346.2,/,file:///C:/Users/mech-mind_lcl/.jenkins/war/,AVAILABLE}{C:\Users\mech-mind_lcl.jenkins\war}

2023-05-06 09:08:58.374+0000 [id=1] INFO o.e.j.server.AbstractConnector#doStop: Stopped ServerConnector@282003e1{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}

2023-05-06 09:08:58.375+0000 [id=1] INFO o.e.j.server.session.HouseKeeper#stopScavenging: node0 Stopped scavenging

2023-05-06 09:08:58.378+0000 [id=1] INFO hudson.WebAppMain#contextDestroyed: Shutting down a Jenkins instance that was still starting up

java.lang.Throwable: reason

at hudson.WebAppMain.contextDestroyed(WebAppMain.java:383)

at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:1080)

at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:584)

at org.eclipse.jetty.server.handler.ContextHandler.contextDestroyed(ContextHandler.java:1043)

at org.eclipse.jetty.servlet.ServletHandler.doStop(ServletHandler.java:319)

at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:94)

at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180)

at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201)

at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:108)

at org.eclipse.jetty.security.SecurityHandler.doStop(SecurityHandler.java:430)

at org.eclipse.jetty.security.ConstraintSecurityHandler.doStop(ConstraintSecurityHandler.java:423)

at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:94)

at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180)

at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201)

at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:108)

at org.eclipse.jetty.server.session.SessionHandler.doStop(SessionHandler.java:520)

at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:94)

at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180)

at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201)

at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:108)

at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:1066)

at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:386)

at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1454)

at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1420)

at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1120)

at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:297)

at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:547)

at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:94)

at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180)

at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201)

at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:108)

at org.eclipse.jetty.server.Server.doStop(Server.java:470)

at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:94)

at winstone.Launcher.shutdown(Launcher.java:354)

at winstone.Launcher.(Launcher.java:217)

at winstone.Launcher.main(Launcher.java:405)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:568)

at Main._main(Main.java:342)

at Main.main(Main.java:117)

2023-05-06 09:08:58.383+0000 [id=1] INFO o.e.j.s.handler.ContextHandler#doStop: Stopped w.@32057e6{Jenkins v2.346.2,/,null,STOPPED}{C:\Users\mech-mind_lcl.jenkins\war}

Exception in thread “Jenkins initialization thread” java.lang.NoClassDefFoundError: hudson/util/HudsonFailedToLoad

at hudson.WebAppMain$3.run(WebAppMain.java:261)

Caused by: java.lang.ClassNotFoundException: hudson.util.HudsonFailedToLoad

at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:587)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)

at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:538)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)

… 1 more

2023-05-06 09:08:58.386+0000 [id=1] INFO winstone.Logger#logInternal: Jetty shutdown successfully

java.io.IOException: Failed to start Jetty

at winstone.Launcher.(Launcher.java:206)

at winstone.Launcher.main(Launcher.java:405)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:568)

at Main._main(Main.java:342)

at Main.main(Main.java:117)

Caused by: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8080

at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)

at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)

at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)

at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)

at org.eclipse.jetty.server.Server.doStart(Server.java:401)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)

at winstone.Launcher.(Launcher.java:202)

… 7 more

Caused by: java.net.BindException: Address already in use: bind

at java.base/sun.nio.ch.Net.bind0(Native Method)

at java.base/sun.nio.ch.Net.bind(Net.java:555)

at java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:337)

at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:294)

at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:89)

at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)

… 14 more

2023-05-06 09:08:58.391+0000 [id=1] SEVERE winstone.Logger#logInternal: Container startup failed

java.net.BindException: Address already in use: bind

at java.base/sun.nio.ch.Net.bind0(Native Method)

at java.base/sun.nio.ch.Net.bind(Net.java:555)

at java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:337)

at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:294)

at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:89)

at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)

Caused: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8080

at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)

at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)

at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)

at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)

at org.eclipse.jetty.server.Server.doStart(Server.java:401)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)

at winstone.Launcher.(Launcher.java:202)

Caused: java.io.IOException: Failed to start Jetty

at winstone.Launcher.(Launcher.java:206)

at winstone.Launcher.main(Launcher.java:405)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:568)

at Main._main(Main.java:342)

at Main.main(Main.java:117)

错误2: 解决方案(方法1)

从日志中可以看出,Jenkins启动失败的原因是端口冲突。错误信息显示:“Address already in use: bind”,表明8080端口已被其他程序占用。因此,Jenkins无法在8080端口上启动。


1)切换端口启动

在cmd中,使用8081或其他端口启动:

java -jar jenkins.war --httpPort=8082

2)浏览器查看

打开浏览器输入http://localhost:8082。可以看到Jenkins已经启动。

1ea22b2c87c842dda5dc9acd18043b1c.png

错误2: 解决方案(方法2)

1)关闭被占用的端口

查找并关闭占用8080端口的程序:使用以下命令查找占用8080端口的程序:

Windows:

netstat -ano | findstr :8080

Linux:

sudo lsof -i :8080

找到占用端口的程序后,结束相关进程,然后重新启动Jenkins。

2)浏览器查看

打开浏览器输入http://localhost:8080。可以看到Jenkins已经启动。

相关文章
存储 jenkins 持续交付
176 2
|
4月前
|
Java Linux
java的jar后台启动
java的jar后台启动
105 14
|
7月前
|
缓存 Java 应用服务中间件
java语言后台管理若依框架-登录提示404-接口异常-系统接口404异常如何处理-登录验证码不显示prod-api/captchaImage 404 (Not Found) 如何处理-解决方案优雅草卓伊凡
java语言后台管理若依框架-登录提示404-接口异常-系统接口404异常如何处理-登录验证码不显示prod-api/captchaImage 404 (Not Found) 如何处理-解决方案优雅草卓伊凡
1311 5
|
7月前
|
前端开发 JavaScript Java
Java打包jar运行时分离lib和jar
在`pom.xml`的`build`节点中,设置`packaging`为`jar`,并配置插件分离依赖库到`lib`目录和资源文件到`resources`目录。这样可以在运行时通过`-Dloader.path=lib,resources`加载外部依赖和资源文件,便于独立升级依赖库和修改资源文件,而无需重新打包程序。具体插件包括`maven-dependency-plugin`、`maven-resources-plugin`和`spring-boot-maven-plugin`等。
360 1
|
7月前
|
网络协议 Java Shell
java spring 项目若依框架启动失败,启动不了服务提示端口8080占用escription: Web server failed to start. Port 8080 was already in use. Action: Identify and stop the process that’s listening on port 8080 or configure this application to listen on another port-优雅草卓伊凡解决方案
java spring 项目若依框架启动失败,启动不了服务提示端口8080占用escription: Web server failed to start. Port 8080 was already in use. Action: Identify and stop the process that’s listening on port 8080 or configure this application to listen on another port-优雅草卓伊凡解决方案
395 7
|
8月前
|
JSON 前端开发 安全
【潜意识java】前后端跨域问题及解决方案
本文深入探讨了跨域问题及其解决方案。跨域是指浏览器出于安全考虑,限制从一个域加载的网页请求另一个域的资源。
1347 0
|
9月前
|
Java Maven
java项目中jar启动执行日志报错:no main manifest attribute, in /www/wwwroot/snow-server/z-server.jar-jar打包的大小明显小于正常大小如何解决
在Java项目中,启动jar包时遇到“no main manifest attribute”错误,且打包大小明显偏小。常见原因包括:1) Maven配置中跳过主程序打包;2) 缺少Manifest文件或Main-Class属性。解决方案如下:
2304 8
java项目中jar启动执行日志报错:no main manifest attribute, in /www/wwwroot/snow-server/z-server.jar-jar打包的大小明显小于正常大小如何解决
|
9月前
|
JSON 前端开发 Java
【Bug合集】——Java大小写引起传参失败,获取值为null的解决方案
类中成员变量命名问题引起传送json字符串,但是变量为null的情况做出解释,@Data注解(Spring自动生成的get和set方法)和@JsonProperty
|
10月前
|
设计模式 Java 开发者
Java多线程编程的陷阱与解决方案####
本文深入探讨了Java多线程编程中常见的问题及其解决策略。通过分析竞态条件、死锁、活锁等典型场景,并结合代码示例和实用技巧,帮助开发者有效避免这些陷阱,提升并发程序的稳定性和性能。 ####
|
10月前
|
安全 Java 开发者
Java多线程编程中的常见问题与解决方案
本文深入探讨了Java多线程编程中常见的问题,包括线程安全问题、死锁、竞态条件等,并提供了相应的解决策略。文章首先介绍了多线程的基础知识,随后详细分析了每个问题的产生原因和典型场景,最后提出了实用的解决方案,旨在帮助开发者提高多线程程序的稳定性和性能。

推荐镜像

更多