Dubbo error reporting
When I started the project today, I turned off the custom service
<dubbo:consumer check="false"/>
And turned off spring’s elastic job
<!--<import resource="cloud-elastic-job.xml"/>-->
But I still reported an error. I looked at the error code because
The Dubbo service of dev IP needs to occupy port 12500, but my local port 12500 is occupied. An error is reported when mapping to my local port 12500. Just kill it
Find which process is using the local 12500 port
lsof -i tcp:12500
> lsof -i tcp:12500
>>
>>
Similar Posts:
- driver failed programming external connectivity on endpoint inspiring_mayer
- Linux transport error 202: bind failed: Address already in use
- [Solved] Dubbo Error: No provider available for the service xxx from registry localhost:9090
- [Solved] ADB Connect Error: failed to start daemon
- [Solved] activemq Startup Error: Address already in use: JVM_Bind
- [Solved] Nginx: [emerg] bind() to 0.0.0.0:443 failed (98：Address already in use)
- Elasticsearch + kibana set user name and password to log in
- Apache : Error: Apache shutdown unexpectedly [How to Solve]
- Idea Error: No provider available from registry 127.0.0.1:2181 for service
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code. See …