SpringBoot项目导出可执行jar包,启动时报错:factory already defined

近期用springboot框架做了个小型项目,用来处理用户回复的消息相关。阿里云服务器上没有tomcat,所以打算将项目打包成jar运行。使用eclipse中的 项目右键 -> export -> 可执行jar,这种方式下的jar无法正常运行,报错如下:

严重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: A child container failed during start
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:423)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:928)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	at org.apache.catalina.startup.Tomcat.start(Tomcat.java:455)
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.initialize(TomcatWebServer.java:106)
	at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.<init>(TomcatWebServer.java:86)
	at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getTomcatWebServer(TomcatServletWebServerFactory.java:415)
	at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getWebServer(TomcatServletWebServerFactory.java:174)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.createWebServer(ServletWebServerApplicationContext.java:181)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:154)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
	at com.chl.SpiderRun.main(SpiderRun.java:22)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:921)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:831)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
	at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:902)
	... 26 more
Caused by: java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.StandardRoot@7e28ed99]
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
	... 34 more
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.StandardRoot@7e28ed99]
	at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:173)
	at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4783)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4918)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
	at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:902)
	... 34 more
Caused by: java.lang.Error: factory already defined
	at java.net.URL.setURLStreamHandlerFactory(URL.java:1112)
	at org.apache.catalina.webresources.TomcatURLStreamHandlerFactory.<init>(TomcatURLStreamHandlerFactory.java:130)
	at org.apache.catalina.webresources.TomcatURLStreamHandlerFactory.getInstanceInternal(TomcatURLStreamHandlerFactory.java:53)
	at org.apache.catalina.webresources.TomcatURLStreamHandlerFactory.register(TomcatURLStreamHandlerFactory.java:77)
	at org.apache.catalina.webresources.StandardRoot.registerURLStreamHandlerFactory(StandardRoot.java:699)
	at org.apache.catalina.webresources.StandardRoot.initInternal(StandardRoot.java:682)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
	... 44 more

网上查了下,针对这个错误具体的原因没有找到,但很多内容指向打包方式,所以重新配置下,用maven方式打包

<!-- 打包类型 -->
<packaging>jar</packaging>

<!-- 打包处理 -->
<build>
	<finalName>Spider</finalName>
	<plugins>
		<plugin>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-maven-plugin</artifactId>
			<executions>
				<execution>
					<goals>
						<goal>repackage</goal>
					</goals>
				</execution>
			</executions>
			
			<!-- 排除一些指定文件 -->
			<configuration>
				<extensions>
					<extension>*.md</extension>
					<extension>AttactController.java</extension>
					<extension>**/webmagic/*</extension>
				</extensions>
			</configuration>
		</plugin>
	</plugins>
</build>

执行以下命令获得jar包

mvn clean package

执行jar运行

java -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=128m -Xms256m -Xmx256m -Xmn128m -Xss256k -jar spider.jar

出现以下信息说明正常

chenhailongdeMacBook-Pro:Desktop chenhailong$ java -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=128m -Xms256m -Xmx256m -Xmn128m -Xss256k -jar LawSpider-va.jar 
2019-09-19 14:41:51,865  INFO Version:21 - HV000001: Hibernate Validator 6.0.14.Final

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::        (v2.1.3.RELEASE)

2019-09-19 14:41:52,247  INFO SpiderRun:50 - Starting SpiderRun on chenhailongdeMacBook-Pro.local with PID 2846 (/Users/chenhailong/Desktop/LawSpider-va.jar started by chenhailong in /Users/chenhailong/Desktop)
2019-09-19 14:41:52,249  INFO SpiderRun:675 - No active profile set, falling back to default profiles: default
2019-09-19 14:41:53,373  INFO RepositoryConfigurationDelegate:244 - Multiple Spring Data modules found, entering strict repository configuration mode!
2019-09-19 14:41:53,379  INFO RepositoryConfigurationDelegate:126 - Bootstrapping Spring Data repositories in DEFAULT mode.
2019-09-19 14:41:53,434  INFO RepositoryConfigurationDelegate:182 - Finished Spring Data repository scanning in 35ms. Found 0 repository interfaces.
2019-09-19 14:41:53,876  INFO PostProcessorRegistrationDelegate$BeanPostProcessorChecker:330 - Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$7ffca964] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-09-19 14:41:54,361  INFO TomcatWebServer:90 - Tomcat initialized with port(s): 8080 (http)
九月 19, 2019 2:41:54 下午 org.apache.catalina.core.StandardService startInternal
信息: Starting service [Tomcat]
九月 19, 2019 2:41:54 下午 org.apache.catalina.core.StandardEngine startInternal
信息: Starting Servlet engine: [Apache Tomcat/9.0.16]
九月 19, 2019 2:41:54 下午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
信息: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/Users/chenhailong/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.]
九月 19, 2019 2:41:54 下午 org.apache.catalina.core.ApplicationContext log
信息: Initializing Spring embedded WebApplicationContext
2019-09-19 14:41:54,559  INFO ContextLoader:296 - Root WebApplicationContext: initialization completed in 2215 ms
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
2019-09-19 14:41:55,948  INFO ThreadPoolTaskExecutor:171 - Initializing ExecutorService 'applicationTaskExecutor'
2019-09-19 14:41:56,807  INFO TomcatWebServer:204 - Tomcat started on port(s): 8080 (http) with context path ''
2019-09-19 14:41:56,810  INFO SpiderRun:59 - Started SpiderRun in 5.208 seconds (JVM running for 5.991)


### 解决方案 当在浏览器环境中引入 `React Query` 并遇到 `'process is not defined'` 错误时,通常是因为某些依赖库或工具假定存在 Node.js 的全局变量 `process`,而这些变量在现代前端框架(如 Vite 或 Create React App)中可能未被定义。 以下是针对该问题的具体解决方案: #### 方法一:通过 polyfill 定义 `process` 可以在项目的入口文件中手动定义 `process` 变量。例如,在 `src/index.js` 文件顶部添加以下代码: ```javascript if (typeof window !== 'undefined') { window.process = window.process || {}; window.process.env = window.process.env || {}; } ``` 此方法适用于简单的场景,但如果项目中有多个地方需要访问 `process`,则建议采用更全面的方式[^1]。 --- #### 方法二:使用插件自动注入 `process` 对于基于 Vite 的项目,可以安装并配置 `vite-plugin-env-compatible` 插件来兼容 `process` 和其他 Node.js 全局对象。执行以下命令安装插件: ```bash npm install vite-plugin-env-compatible --save-dev ``` 随后,在 `vite.config.js` 中进行如下配置: ```javascript import envCompatible from 'vite-plugin-env-compatible'; export default { plugins: [ env Compatible() ] }; ``` 这样可以确保在构建过程中正确处理 `process` 环境变量[^2]。 --- #### 方法三:调整 Webpack 配置(如果适用) 如果是基于旧版 `create-react-app` 构建的项目,则可以通过自定义 Webpack 配置解决问题。具体操作括卸载当前版本的 `react-scripts` 并重新安装较早版本,以便能够通过 `eject` 曝露配置文件。之后修改 Webpack 配置以支持 `process` 聚合器[^3]。 示例配置片段如下: ```javascript const webpackConfig = { resolve: { fallback: { process: require.resolve('process/browser'), }, }, }; module.exports = webpackConfig; ``` 上述方式利用了 `process/browser` 提供的浏览器端实现替代默认行为。 --- #### 方法四:升级依赖项至最新版本 有时,错误的根本原因在于所使用的第三方库尚未完全适配现代化前端环境。因此,尝试将 `React Query` 升级到最新稳定版本,并确认其文档中是否有额外说明关于如何规避此类问题的信息。 运行以下命令完成更新: ```bash npm update react-query ``` 同时检查是否存在新的初始化选项允许禁用对 `process` 的依赖。 --- ### 总结 以上四种方法分别对应不同类型的项目架构和技术栈需求。推荐优先考虑 **方法二** 使用专门插件解决兼容性问题;而对于传统 CRA 工程可选用 **方法三** 自定义 Webpack 设置;简单快速修复可通过 **方法一** 实现临时补丁效果;最后不要忽略保持生态组件处于最佳状态的重要性即采取 **方法四** 更新策略。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值