lianjunwei opened a new issue #2754:
URL: https://github.com/apache/incubator-shenyu/issues/2754


   ### Is there an existing issue for this?
   
   - [X] I have searched the existing issues
   
   ### Current Behavior
   
   After the backend microservice is started, the selector handler of the 
divide plug-in is empty.
   
![image](https://user-images.githubusercontent.com/13819823/149070329-e6f99033-e3fb-4414-8d50-e3e70ac816a7.png)
   
   
   ### Expected Behavior
   
   the selector handler of the divide plug-in is not empty.
   
   ### Steps To Reproduce
   
   1.At first, I used Shenyu version 2.4.0. There was a micro service started, 
and the URI was automatically registered normally.
   2.After running for a period of time, the micro service went offline.
   3.Shenyu upgraded to 2.4.1
   4.Start this service, but fail to register URI all the time. For a long 
time, I had to maintain URIs manually.
   
   ### Environment
   
   ```markdown
   ShenYu version(s):2.4.1
   ```
   
   
   ### Debug logs
   
   The reason for the final location is that the handler field in the select 
table of Shenyu database is stored as []. As shown below:
   
![image](https://user-images.githubusercontent.com/13819823/149072331-801a3dd7-726c-414a-8401-73fa1cc97035.png)
   
   1.The first way to fix this bug:fix code
   
![image](https://user-images.githubusercontent.com/13819823/149080163-824326a1-06b6-4703-9487-e3dcbdeae8aa.png)
   
   2.The second way to fix this bug: modify the database.
   3.The third way to fix this bug: delete the registration of the service in 
the divide selector and re register.
   
   
   ### Anything else?
   
   I fixed the code in my project using Shenyu. Which repair method is better? 
If the code repair scheme is better, I mention pr.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to