java socket 权限管理_java.net.SocketException: 权限不够

最新推荐文章于 2024-03-16 10:30:00 发布
最新推荐文章于 2024-03-16 10:30:00 发布
阅读量229 收藏
点赞数
文章标签： java socket 权限管理
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_39917811/article/details/114556295
版权

12-12 19:44:58.792|INFO|c.netflix.discovery.DiscoveryClient:813|DiscoveryClient-InstanceInfoReplicator-0||DiscoveryClient_TPP-ZUUL-PRE/10.90.6.95:80 - registration status: 204

12-12 19:44:58.795|INFO|o.s.b.a.e.jmx.EndpointMBeanExporter:678|main||Located managed bean 'configurationPropertiesReportEndpoint': registering with JMX server as MBean [org.springframework.boot:type=Endpoint,name=configurationPropertiesReportEndpoint]

12-12 19:44:58.797|INFO|o.s.c.s.DefaultLifecycleProcessor:343|main||Starting beans in phase 2147483647

12-12 19:44:58.801|INFO|o.s.c.n.h.HystrixCircuitBreakerConfiguration$HystrixMetricsPollerConfiguration:138|main||Starting poller

12-12 19:44:58.816|INFO|o.s.s.a.ScheduledAnnotationBeanPostProcessor:262|main||No TaskScheduler/ScheduledExecutorService bean found for scheduled processing

12-12 19:44:58.825|INFO|o.a.coyote.http11.Http11NioProtocol:179|main||Initializing ProtocolHandler ["http-nio-80"]

12-12 19:44:58.836|INFO|o.a.coyote.http11.Http11NioProtocol:179|main||Starting ProtocolHandler ["http-nio-80"]

12-12 19:44:58.839|ERROR|o.a.coyote.http11.Http11NioProtocol:181|main||Failed to start end point associated with ProtocolHandler ["http-nio-80"]

java.net.SocketException: 权限不够

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:210)

at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:990)

at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:635)

at org.apache.catalina.connector.Connector.startInternal(Connector.java:1022)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

at org.apache.catalina.core.StandardService.addConnector(StandardService.java:225)

at org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer.addPreviouslyRemovedConnectors(TomcatEmbeddedServletContainer.java:250)

at org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer.start(TomcatEmbeddedServletContainer.java:193)

at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.startEmbeddedServletContainer(EmbeddedWebApplicationContext.java:297)

at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.finishRefresh(EmbeddedWebApplicationContext.java:145)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)

at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)

at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)

at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)

at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)

at com.pci.tpp.gateway.GatewayApplication.main(GatewayApplication.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.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)

at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)

12-12 19:44:58.840|ERROR|o.a.catalina.core.StandardService:181|main||Failed to start connector [Connector[HTTP/1.1-80]]

org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-80]]

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)

at org.apache.catalina.core.StandardService.addConnector(StandardService.java:225)

at org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer.addPreviouslyRemovedConnectors(TomcatEmbeddedServletContainer.java:250)

at org.springframework.boot.context.embedded.tomcat.TomcatEmbeddedServletContainer.start(TomcatEmbeddedServletContainer.java:193)

at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.startEmbeddedServletContainer(EmbeddedWebApplicationContext.java:297)

at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.finishRefresh(EmbeddedWebApplicationContext.java:145)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)

at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)

at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)

at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)

at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)

at com.pci.tpp.gateway.GatewayApplication.main(GatewayApplication.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.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)

at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)

at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)

Caused by: org.apache.catalina.LifecycleException: service.getName(): "Tomcat"; Protocol handler start failed

at org.apache.catalina.connector.Connector.startInternal(Connector.java:1031)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

... 19 common frames omitted

Caused by: java.net.SocketException: 权限不够

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:210)

at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:990)

at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:635)

at org.apache.catalina.connector.Connector.startInternal(Connector.java:1022)

... 20 common frames omitted

12-12 19:44:58.847|INFO|o.a.coyote.http11.Http11NioProtocol:179|main||Pausing ProtocolHandler ["http-nio-80"]

12-12 19:44:58.848|INFO|o.a.catalina.core.StandardService:179|main||Stopping service [Tomcat]

12-12 19:44:58.852|WARN|o.a.c.loader.WebappClassLoaderBase:179|localhost-startStop-1||The web application [ROOT] appears to have started a thread named [spring.cloud.inetutils] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

sun.misc.Unsafe.park(Native Method)

java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)

java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)

java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

java.lang.Thread.run(Thread.java:748)

12-12 19:44:58.855|INFO|o.apache.catalina.util.LifecycleBase:179|main||The stop() method was called on component [StandardServer[-1]] after stop() had already been called. The second call will be ignored.

12-12 19:44:58.855|INFO|o.a.coyote.http11.Http11NioProtocol:179|main||Stopping ProtocolHandler ["http-nio-80"]

12-12 19:44:58.855|INFO|o.a.coyote.http11.Http11NioProtocol:179|main||Destroying ProtocolHandler ["http-nio-80"]

12-12 19:44:58.857|INFO|o.s.b.a.l.AutoConfigurationReportLoggingInitializer:101|main||

Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.

12-12 19:44:58.860|ERROR|o.s.b.d.LoggingFailureAnalysisReporter:42|main||

weixin_39917811
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
java.net.SocketException Connection reset 解决方法
07-11
java.net.SocketException Connection reset 解决方法
在Win7系统下抛出java.net.SocketException的解决办法
04-19
java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address associated with interface 本文提供了在Win7或Vista系统下解决这个异常信息的办法。
修复 Java 错误 Java.Net.SocketException: Permission Denied
最新发布
迹忆客
03-16 691
本篇文章介绍了 Java 中的错误。
JAVA.NET.SOCKETEXCEPTION TOO MANY OPEN FILES解决方法
03-18
JAVA.NET.SOCKETEXCEPTION TOO MANY OPEN FILES解决方法，三种方案，临时，永久，根治
java.net.SocketException: No route to host 异常原因
04-01
NULL 博文链接：https://zhoudan241.iteye.com/blog/1432014
Caused by: java.net.SocketException: 权限不够
Nick
10-29 1994
出现问题原因：我在用Ubuntu18.04系统开发SpringBoot程序，用的编译器是IDEA，我在application.properties里面修改了端口号，便出现了上述的错误。原因即 非root用户没有权限修改1024以下的端口。 解决方案： 1、(推荐，最简单的)修改桌面IDEA的配置文件，用root权限运行IDEA 注意：这个方法有一个核心问题便是，当你加入了sudo指令后，没有输密码的位置，因此需要加入sudo免密码操纵，这一步是核心，请参考我的另一个博客。如果你不想加sudo指令.
Caused by: java.nio.channels.NotYetConnectedException: null
u011734144的专栏
12-29 7100
15:04:12.004 [CuratorFramework-0] ERROR org.apache.curator.ConnectionState - Connection timed out for connection string (10.241.81.35:2181,10.241.81.36:2181,10.241.81.37:2181,10.241.81.38:2181,10.241.
java.net.SocketException: 权限不够
m0_72167535的博客
12-07 908
java.net.SocketException: 权限不够
【报错记录】ZooKeeper报java.net.SocketException: Socket is not connected无法连接上
DCTANT的博客
07-09 4985
由于我在学习ZooKeeper的阶段中，ZooKeeper都部署在虚拟机里了，心想着我就不配hosts了吧，反正虚拟机早晚要删掉。然后用java连接ZooKeeper就报错了，报： ava.net.SocketException: Socket is not connected at sun.nio.ch.Net.translateToSocketException(Net.java:123) at sun.nio.ch.Net.translateException(Net.java:157) a
java.net.SocketException: Socket closed 解决方式
imyLove7的博客
04-05 4万+
问题背景：客户端连接服务器，发送一个请求，捕获响应信息。 // 建立连接 Socket socket = new Socket(); socket.connect(new InetSocketAddress(InetAddress.getLocalHost(),9999),10000); // 将输入、输出流包装成数据输入、输出流 DataInputStream dis2 = new DataInputStream(socket.getInputStream()); DataOutputStream
java.net.SocketException: Connection reset 解决方法
09-05
最近纠结致死的一个java报错java.net.SocketException: Connection reset 终于得到解决
java.net.SocketException四大异常解决方案
热门推荐
hzp666的博客
07-22 7万+
转载：点击打开链接 第1个异常是 java.net.BindException:Address already in use: JVM_Bind。 该异常发生在服务器端进行new ServerSocket(port)（port是一个0，65536的整型值）操作时。异常的原因是以为与port一样的一个端口已经被启动，并进行监听。此时用netstat –an命令，可以看到一个Listending状...
Linux下报 java.net.SocketException权限不够 异常解决
qq_38472465的博客
05-18 207
Linux下报 java.net.SocketException权限不够 异常解决
zookeeper连接客户端操作数据时报错Socket is not connected
江哈哈的博客
10-17 1519
zookeeper客户端连接报错：org.apache.zookeeper.ClientCnxnSocketNIO - Ignoring exception during shutdown input java.net.SocketException: Socket is not connected
linux java.net.SocketException: 权限不够
kevin的博客
12-16 359
今天在Linux下用启动springCloud的一个微服务，端口是83，然后启动后一直报错：java.net.SocketException: 权限不够 查询下才知道：原因其实是因为在linux下，如果使用1024以下的端口则需要root权限，所以因为我当前使用的不是root权限，所以权限不足而无法使用80端口，所以会报权限不够异常。 资料来源：https://www.cnblogs.com/dongxiao-yang/p/4410371.html ...
zookpeer链接报错Socket is not connected
我思故我在
10-28 1349
再zookeeper回调event的时候收不到，当打开debug的时候爆。JDK版本选的15 zk当前版本不支持。1 查看zk是否启动成功。2 查看端口以及防火墙。
Session.connect: java.net.SocketException: Socket closed Session.connect: java.net.SocketTimeoutException: Read timed out
03-06
Session.connect是一个方法，用于建立与远程服务器的连接。在Java中，它是通过Socket类实现的。根据你提供的错误信息，有两种可能的异常情况：java.net.SocketException: Socket closed和java.net.SocketTimeoutException: Read timed out。 1. java.net.SocketException: Socket closed：这个异常表示Socket已关闭。可能的原因是在连接建立之后，Socket被意外关闭了。这可能是由于网络连接中断、服务器端关闭了连接或者其他原因导致的。要解决这个问题，你可以检查网络连接是否正常，确保服务器端没有主动关闭连接，并且在使用Socket之前确保它处于打开状态。 2. java.net.SocketTimeoutException: Read timed out：这个异常表示读取数据超时。当在指定的时间内没有从Socket中读取到数据时，就会抛出这个异常。可能的原因是网络延迟、服务器响应时间过长或者其他原因导致的。要解决这个问题，你可以尝试增加读取超时时间，或者检查网络连接是否正常。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值