tomcat报错：java.net.SocketException: Permission denied["http-nio-80"]

最新推荐文章于 2022-05-24 22:09:10 发布
转载 最新推荐文章于 2022-05-24 22:09:10 发布 · 139 阅读 · 0 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/reblue520/p/6239707.html
文章标签：

#java #网络 #开发工具

本文介绍了在CentOS环境下使用非root用户启动Tomcat遇到的端口权限问题及解决办法。通过修改Tomcat配置文件中的端口号或使用iptables进行端口重定向，可以有效避免因端口权限不足导致的服务启动失败。
tomcat报错：java.net.SocketException: Permission denied["http-nio-80"]


问题：使用非root账户tomcat启动tomcat报错：


19-Sep-2016 15:08:27.168 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]
19-Sep-2016 15:08:27.179 SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["http-nio-80"]
 java.net.SocketException: Permission denied
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:339)
        at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:737)
        at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:457)
        at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:120)
        at org.apache.catalina.connector.Connector.initInternal(Connector.java:960)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.core.StandardService.initInternal(StandardService.java:567)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:851)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:576)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:599)
        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.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)


19-Sep-2016 15:08:27.180 SEVERE [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[HTTP/1.1-80]]


 org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-80]]
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
        at org.apache.catalina.core.StandardService.initInternal(StandardService.java:567)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:851)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:576)
        at org.apache.catalina.startup.Catalina.load(Catalina.java:599)
        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.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
        at org.apache.catalina.connector.Connector.initInternal(Connector.java:962)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        ... 12 more
Caused by: java.net.SocketException: Permission denied
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:339)
        at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:737)
        at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:457)
        at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:120)
        at org.apache.catalina.connector.Connector.initInternal(Connector.java:960)
        ... 13 more


问题分析：在centos上只有root用户才可以使用1024以下的端口号，其余用户不能


2.解决方案


方法①修改Tomcat的server.xml配置文件，将端口修改为8081（或者其他1024以上的端口号，不能与本机上的其它Tomcat端口冲突）


vim /usr/local/apache-tomcat-8.0.52/conf/server.xml
    <Connector port="8081" protocol="HTTP/1.1" 
               connectionTimeout="30000" 
               maxThreads="2000"
               acceptCount="2000"
               URIEncoding="UTF-8"
               redirectPort="9143" />
    <!-- A "Connector" using the shared thread pool-->


方法②修改端口后，使用root用户登录服务器，执行端口重定向命令：iptables -t nat -A PREROUTING -p tcp –dport 80 -j REDIRECT –to-port 8081


意思就是当访问80端口时重定向到8081端口，这样，我们可以改成任何我们需要的端口啦。


iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8081


切换到tomcat账号，启动tomcat服务

转载于:https://www.cnblogs.com/reblue520/p/6239707.html

GateWay Caused by: java.net.SocketException: Network is unreachable: no further information
zjy660358的专栏
04-26 4914
2022-04-26 14:42:19.042 ERROR 5568 --- [reactor-http-nio-21] a.w.r.e.AbstractErrorWebExceptionHandler : [f44edf68-3769] 500 Server Error for HTTP GET "/yt-common/personal/basicAuth/getPcPermissionsByPid?pid=167" io.netty.channel.AbstractChannel$Annotate.
Elasticsearch启动报错：java.security.AccessControlException: access denied (“javax.management.MBeanTrustP
有问题请发邮箱dengyifanlittle@163.com进行讨论
04-27 3298
ES启动报错： java.security.AccessControlException: access denied ("javax.management.MBeanTrustPermission" "register") at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472) at java.lang.SecurityManager.ch...
Tomcat踩坑之------java.net.SocketException: Permission denied
peanut的博客
08-31 2503
Linux 通过bin文件夹下的./startup.sh启动无报错，奈何就是无法访问 一、问题出现的原因： 1、我把默认的Tomcat访问端口修改成为了80 2、我用的非root用户启动的Tomcat 二、解决思路 1、单凭bin文件夹下的./startup.sh启动无法查看完整的tomcat启动日志，误认为启动过程无错误 2、进入tomcat文件夹下logs目录，通过命令tail -f catalina.out实时监控日志输出 3、然后启动tomcat，发现tomcat启动异常 java.net.Sock
idea 重启tomcat报错 到底是哪里的错
fen_qing的博客
03-14 1258
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[AJP/1.3-8010]] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:113) at org.apache.catalina.core.Stan...
Ubuntu 运行tomcat报错：java.net.SocketException: Permission denied
小木头的专栏
01-14 1219
在Ubuntu系统中，使用非root用户开启tomcat时报错：    java.net.SocketException: Permission denied at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:433) at sun.nio.ch.Net.bind(Net.java:425) ...
java.net.SocketException: Permission denied
yuanlanjun
07-27 351
java.net.SocketException: Permission denied 05-18 01:34:48.549: WARN/System.err(406):java.net.SocketException: Permission denied05-18 01:34:48.558: WARN/System.err(406): at org.apache.harmo...
Internal error java.net.SocketException: Permission denied: bind at java.base/sun.nio.ch.UnixDomainSockets.bind0(Native Method) at java.base/sun.nio.ch.UnixDomainSockets.bind(UnixDomainSockets.java:129) at java.base/sun.nio.ch.ServerSocketChannelImpl.unixBind(ServerSocketChannelImpl.java:326) at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:299) at java.base/java.nio.channels.ServerSocketChannel.bind(ServerSocketChannel.java:224) at com.intellij.platform.ide.bootstrap.DirectoryLock.tryListen(DirectoryLock.java:273) at com.intellij.platform.ide.bootstrap.DirectoryLock.lockOrActivate(DirectoryLock.java:214) at com.intellij.platform.ide.bootstrap.StartupUtil.lockSystemDirs(startup.kt:492) at com.intellij.platform.ide.bootstrap.StartupUtil.access$lockSystemDirs(startup.kt:1) at com.intellij.platform.ide.bootstrap.StartupUtil$startApplication$lockSystemDirsJob$1$1.invokeSuspend(startup.kt:112) at com.intellij.platform.ide.bootstrap.StartupUtil$startApplication$lockSystemDirsJob$1$1.invoke(startup.kt) at com.intellij.platform.ide.bootstrap.StartupUtil$startApplication$lockSystemDirsJob$1$1.invoke(startup.kt) at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:44) at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:166) at kotlinx.coroutines.BuildersKt.withContext(Unknown Source) at com.intellij.platform.diagnostic.telemetry.impl.TracerKt.span(tracer.kt:56) at com.intellij.platform.diagnostic.telemetry.impl.TracerKt.span$default(tracer.kt:48) at com.intellij.platform.ide.bootstrap.StartupUtil$startApplication$lockSystemDirsJob$1.invokeSuspend(startup.kt:111) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:613) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:1189) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:778) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:765) Suppressed: java.net.SocketException: Permission denied: bind at java.base/sun.nio.ch.UnixDomainSockets.bind0(Native Method) at java.base/sun.nio.ch.UnixDomainSockets.bind(UnixDomainSockets.java:129) at java.base/sun.nio.ch.ServerSocketChannelImpl.unixBind(ServerSocketChannelImpl.java:326) at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:299) at java.base/java.nio.channels.ServerSocketChannel.bind(ServerSocketChannel.java:224) at com.intellij.platform.ide.bootstrap.DirectoryLock.tryListen(DirectoryLock.java:273) at com.intellij.platform.ide.bootstrap.DirectoryLock.lockOrActivate(DirectoryLock.java:163) ... 17 more Suppressed: java.net.ConnectException: Connection refused: connect at java.base/sun.nio.ch.UnixDomainSockets.connect0(Native Method) at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:166) at java.base/sun.nio.ch.UnixDomainSockets.connect(UnixDomainSockets.java:162) at java.base/sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:878) at com.intellij.platform.ide.bootstrap.DirectoryLock.tryConnect(DirectoryLock.java:315) at com.intellij.platform.ide.bootstrap.DirectoryLock.lockOrActivate(DirectoryLock.java:171) ... 17 more Suppressed: java.nio.file.NoSuchFileException: C:\Users\lenovo\AppData\Roaming\JetBrains\IdeaIC2025.2\.lock at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:87) at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:106) at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:112) at java.base/sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:234) at com.intellij.platform.core.nio.fs.DelegatingFileSystemProvider.newByteChannel(DelegatingFileSystemProvider.java:145) at java.base/java.nio.file.Files.newByteChannel(Files.java:380) at java.base/java.nio.file.Files.newByteChannel(Files.java:432) at java.base/java.nio.file.Files.readAllBytes(Files.java:3281) at java.base/java.nio.file.Files.readString(Files.java:3359) at java.base/java.nio.file.Files.readString(Files.java:3318) at com.intellij.platform.ide.bootstrap.DirectoryLock.remotePID(DirectoryLock.java:408) at com.intellij.platform.ide.bootstrap.DirectoryLock.lockOrActivate(DirectoryLock.java:179) ... 17 more ----- JRE: 21.0.9+1-b1038.76 amd64 (JetBrains s.r.o.) D:\RUANJIAN\IntelliJ IDEA Community Edition 2025.2.5\jbr
最新发布
12-06
我们正在解决的是Java程序在IntelliJ IDEA Community Edition 2025.2.5中运行时出现的"java.net.SocketException: Permission denied: bind"错误。根据提供的引用信息，我们可以分析可能的原因和解决方案。 引用[2...
org.springframework.data.redis.RedisConnectionFailureException: Unable to connect to Redis; nested exception is io.lettuce.core.RedisConnectionException: Unable to connect to 127.0.0.1:6379 at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$SharedConnection.getNativeConnection(LettuceConnectionFactory.java:966) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$SharedConnection.getConnection(LettuceConnectionFactory.java:934) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getSharedConnection(LettuceConnectionFactory.java:786) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getConnection(LettuceConnectionFactory.java:300) at org.springframework.data.redis.core.RedisConnectionUtils.doGetConnection(RedisConnectionUtils.java:132) at org.springframework.data.redis.core.RedisConnectionUtils.getConnection(RedisConnectionUtils.java:95) at org.springframework.data.redis.core.RedisConnectionUtils.getConnection(RedisConnectionUtils.java:82) at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:211) at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:184) at org.springframework.data.redis.core.AbstractOperations.execute(AbstractOperations.java:95) at org.springframework.data.redis.core.DefaultSetOperations.members(DefaultSetOperations.java:158) at org.springframework.data.redis.core.DefaultBoundSetOperations.members(DefaultBoundSetOperations.java:152) at org.springframework.session.data.redis.RedisSessionExpirationPolicy.cleanExpiredSessions(RedisSessionExpirationPolicy.java:132) at org.springframework.session.data.redis.RedisOperationsSessionRepository.cleanupExpiredSessions(RedisOperationsSessionRepository.java:430) at org.springframework.session.data.redis.config.annotation.web.http.RedisHttpSessionConfiguration.lambda$configureTasks$0(RedisHttpSessionConfiguration.java:248) at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:93) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) at java.util.concurrent.FutureTask.run(FutureTask.java) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Caused by: io.lettuce.core.RedisConnectionException: Unable to connect to 127.0.0.1:6379 at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56) at io.lettuce.core.AbstractRedisClient.getConnection(AbstractRedisClient.java:233) at io.lettuce.core.RedisClient.connectStandalone(RedisClient.java:253) at io.lettuce.core.RedisClient.connect(RedisClient.java:202) at org.springframework.data.redis.connection.lettuce.StandaloneConnectionProvider.getConnection(StandaloneConnectionProvider.java:56) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory$SharedConnection.getNativeConnection(LettuceConnectionFactory.java:959) ... 24 common frames omitted Caused by: io.netty.channel.AbstractChannel$AnnotatedSocketException: Permission denied: no further information: /127.0.0.1:6379 at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:715) at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:327) at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:665) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:612) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:529) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:491) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:905) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ... 1 common frames omitted Caused by: java.net.SocketException: Permission denied: no further information ... 11 common frames omitted 2025-07-22 15:04:02.693 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-3] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:02.693 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-3] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:07.708 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-4] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:07.708 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-4] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:12.724 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-5] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:12.724 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-5] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:17.732 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-6] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:17.732 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-6] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:22.749 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-7] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:22.749 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-7] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:27.756 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-8] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:27.756 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-8] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:32.762 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-9] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:32.762 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-9] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:37.791 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-10] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:37.791 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-10] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:42.802 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-11] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:42.802 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-11] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:47.811 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-12] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:47.811 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-12] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:52.821 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-13] Connection failure occurred. Restarting subscription task after 5000 ms 2025-07-22 15:04:52.821 E [org.springframework.data.redis.listener.RedisMessageListenerContainer] [redisMessageListenerContainer-13] Connection failure occurred. Restarting subscription task after 5000 ms
07-23
在使用Spring Boot集成Redis时，遇到`RedisConnectionFailureException: Unable to connect to Redis 127.0.0.1:6379 (Permission denied)`错误，通常意味着Spring Boot应用无法成功连接到本地或远程的Redis服务器。...
tomcat8.5、9.0配置ssl证书(阿里免费证书)
开花的洋葱
05-15 3858
环境说明： tomcat8.5、9.0 ssl证书为pfx格式 操作系统为windows10和ubuntu 配置tomcat 这里以9.0为例。一开始我是在服务器上配的8.5，问题很多，而且不知道怎么看异常信息。但是后来好了之后才清楚。这里8.5，9.0的配置可以一样，8.5一下版本的配置网上也很多，我也借鉴很多，主要碰到的问题是各种细节，不是配置本身。 1.先把证书解压放到toumcat的con...
java.net.SocketException: Permission denied（将80端口重定向到8080端口）
为无为，事无事，味无味。
08-22 7076
在Linux的下面部署了apache，为了安全我们使用非root用户进行启动， 但是在域名绑定时无法直接访问80端口号。众所周知，在unix下，非root用户不能监听1024以下的端口号， 这个apache服务器就没办法绑定在80端口下。所以这里需要使用linux的端口转发机制，把到80端口的服务请求都转到8080端口上。  在root账户下面运行一下命令： iptables -t nat
tomcat报：java.net.BindException: Permission denied <null>:80
Bonnenults浅时光的博客
11-09 1605
前段时间遇到一个情况，官网的服务器reboot之后，发现输入官网连接打不开了，最后去查了一下日志发现：tomcat报权限不够的错误，如下：服务器重启后，tomcat报错：SEVERE: Error starting endpoint java.net.BindException: Permission denied <null>:80 at org.apache.tomcat.util.ne
信息[http-nio-80-exec-9] org. apache. coyote. http11. Httpl1Processor.service解析注意:HTTP请求解析错误的进--步发生将记录
m0_64895976的博客
01-11 3994
这种情况一般情况是浏览器将前台的json数据拦截了，无法反馈给后台所导致的 出现这个问题可以直接用data传值 也可以用url进行拼接
spring事务传播机制
qq_32999113的博客
03-08 999
spring的事务传播类型定义在org.springframework.transaction.annotation.Propagation这个枚举类中 类型 说明 REQUIRED 默认的级别，如果当前事务存在，则加入到当前事务中，否则创建新的事务 SUPPORTS 如果当前事务存在，则加入到当前事务中，否则以非事务的方式执行 MANDATORY 如果当前事务存在，则加入...
Day627.HTTP调用常见问题 --Java业务开发常见错误
阿昌爱Java
05-24 1603
HTTP调用常见问题 Hi，这里是阿昌! 今天学习记录的是HTTP调用过程中需要考虑的问题：超时、重试、并发 Spring Cloud 是 Java 微服务架构的代表性框架。如果使用 Spring Cloud 进行微服务开发，就会使用 Feign 进行声明式的服务调用。 如果不使用 Spring Cloud，而直接使用 Spring Boot 进行微服务开发的话，可能会直接使用 Java 中最常用的 HTTP 客户端 Apache HttpClient 进行服务调用。 接下来，使用 Feign 和 Apac
Tomcat源码学习--servlet请求处理
d15143231539的博客
03-30 695
当前tomcat 8.5.20中已经不再使用bio模型，默认支持NIO实现的org.apache.coyote.http11.Http11NioProtocol，当前tomcat支持的io模型如下： 在Tomcat启动时会启用一个端口来监听请求，并且会启动多个线程来处理相关的请求操作，如下图：相关线程介绍：（1）http-nio-8080-Acceptor为请求接收器，其只接收请求，不会对请求做任...
严重: 子容器启动失败 java.util.concurrent.ExecutionException 信息: 正在摧毁协议处理器 ["http-nio-80"]WARNING: An illegal
热门推荐
qq_44675204的博客
04-12 1万+
话不多说直接上错误 解决方案： 由于一开始以为是tomcat和eclipseEE出现故障，将两个软件重新下载并配置环境但错误没有解决，然后又检查了JDK版本也没问题，最后肯定了是代码的问题，仔细检查后发现是servlet映射地址写重了，后来又发现不写映射地址前没写“/”也会导致这样的错误！ 以此篇博客提醒自己不要再因为这样的**错误花那么多时间下软件配环境，也为犯同样错误的正在看的你踩...
ftpClient.changeWorkingDirectory报错：java.net.SocketException: Connection reset by peer: socket write error
10-14
当 `ftpClient.changeWorkingDirectory` 报错 `java.net.SocketException: Connection reset by peer: socket write error` 时，可以参考以下解决办法： - **检查连接关闭情况**：确保连接使用完毕后及时关闭，先调用 `logout` 方法，再调用 `disconnection` 方法关闭连接。示例代码如下： ```java import org.apache.commons.net.ftp.FTPClient; import java.io.IOException; public class FTPExample { public static void main(String[] args) { FTPClient ftpClient = new FTPClient(); try { // 连接到 FTP 服务器 ftpClient.connect("ftp.example.com", 21); ftpClient.login("username", "password"); // 执行操作 boolean success = ftpClient.changeWorkingDirectory("/path/to/directory"); if (success) { System.out.println("Changed working directory successfully."); } else { System.out.println("Failed to change working directory."); } // 关闭连接 ftpClient.logout(); ftpClient.disconnect(); } catch (IOException e) { e.printStackTrace(); } } } ``` - **检查磁盘空间**：磁盘空间已满可能导致该异常，需要检查服务器磁盘使用情况，清理磁盘空间或者进行磁盘扩容操作 [^2]。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值