Software testing technology exchange group: 429183023
2
A service of the test environment, which was good last week, suddenly couldn’t get up this week. I’m very puzzled.
But because of the test environment, the development was not very attentive, so I decided to solve it by myself. After observing the Catalina log, it is found that an error is reported
Tomcat start error ERROR:transport error 202:bind failed:Address already
So check it out start.sh File to see if there is a wrong address. When you see the remote debugging, you add a listening port, and the remote debugging of another service is also listening to this port before, so this port conflicts. The service can’t get up all the time. Delete – Xdebug- Xrunjdwp:transport=dt_ Socket, suspend = n, server = y, address = * * * *, perfect solution.
This admonishes us, because there are many services, when debugging a service remotely, we must restore the scene after debugging it!!! Because the test environment is shared, if someone else also uses this port for remote debugging, it will be GG
Read More:
- Tomcat start error ERROR:transport error 202:bind failed:Address already
- Error: transport error 202: bind failed: address already in use
- Zeppelin starts successfully, but an error is reported
- Zeppelin starts successfully, but an error is reported
- Exception record. When eclipse starts, an error is reported when workspace is opened
- zookeeper_ An error is reported when the exporter starts
- An error is reported when springboot starts: error creating bean with name ‘XXXX’
- nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
- The Vue project is packaged and deployed to tomcat, and an Error 404 is reported as soon as it is refreshed
- Elasticsearch startup process error: org.elasticsearch.transport .BindTransportException: Failed to bind to [9300-9400
- When angular4.0 starts the project, an error is reported: the “@ angular / compiler cli” package was not properly installed
- Interrupted function call accept failed when idea starts Tomcat
- Error running ‘Tomcat 9‘: Address localhost:1099 is already in use
- When docker starts tomcat, the access port of the container displays 404, and the source server fails to find the representation of the target resource or is unwilling to disclose an existing one
- Solution to the problem that listen TCP 0.0.0.0:3306: bind: address already in use port is occupied in Linux centos7
- [exception] address already in use: bind
- Apache2 cannot be started and an error is reported for apache2.service failed because the control process exited with error code.
- After the eclipse Android virtual machine starts, an error will be reported: similar to SDK manager devices.xml Solution
- During the development of vue, v-for reported an error [vue/require-v-for-key] Elements in iteration expect to have’v-bind:key’ directives.
- An error is reported when an android phone visits the app webpage: net::ERR_PROXY_CONNECTION_FAILED