In a situation where you have removed the breakpoint in a route between two components and it shows as removed in the Event Process, whereas it stays back in the backend server due to some issue, you need to remove routes in FES Route Manager in Server Connections (eStudio). If this does not work, you need to invoke "disconnectClient" operation in FES Admin Service in Server Connections (eStudio).

Removing Routes

If an Event Process is running in eStudio with unclosed breakpoint (E.g. Simple Chat EP running with breakpoint set in route2), resolve this by removing the route. Steps are mentioned below.


Figure 1: Sample EP with unclosed Breakpoint (in route2)
 

After opening Connection Management perspective in eStuido, perform the following actions in Server Connections panel:

1. Log into FES-JMX and navigate to JMX Connection > Fiorano > etc > RouteManager > RouteManager node.
2. Right click RouteManager node and click View Operations.
   
   
   Figure 2: Navigating to RouteManager node and opeing the dialog box of operations
    
3. In the RouteManager dialog box, select listAllRoutes operation in the left navigation bar and then click the listAllRoutes button under the Invoke Operation section to list all the routes with breakpoints.
4. The routes with breakpoint appear in the format "<EventProcessName>_<Version>_<RouteName>_DEBUG" under the Result tab. Double-click the value(s) or click the button next to it and copy the value(s).
   
   
   Figure 3: Copying the route name that appears in the list under Result tab
    
5. Now click removeRoute(routeGUID) operation in the left navigation panel and replace the routeGUID value "null" (under the Invoke Operation section) with the route name copied in the previous step. Then, click the removeRoute button to remove the route.
   
   
   Figure 4: Invoking removeRoute operation
    
6. A pop-up appears with a confirm message "Operation invoked succefully"; click OK.
   
   
   Figure 5: Dialog box with Confirmation message
    
7. Ideally, this operation resolves the issue. In case, removing routes does not fix it, move to the next section to understand how to disconnect clients.

Disconnecting Clients

When an event process runs with Breakpoint, the route with breakpoint appears in the Dashboard as PTP (Point-to-Point) connections under Enterprise Server (Server Status > Connections). Copy the client IDs and disconnect these from Admin Service utility under FES-JMX in Server Connections panel present in Connection Management perspective. (FES-JMX > JMX Connection > Fiorano > etc > AdminService > AdminService > View Operations). This disconnects the route. Below-mentioned are the elaborate steps for the same scenario of Simple Chat EP running with breakpoint set in route2.

Step 1: Login to Fiorano Web Console (ESB Dashboard) and copy the Client IDs

Perform the following actions in the Dashboard to complete Step 1:

1. Under the Server Status node, select fes (Enterprise Server), and then select Connections.
2. Check for Connection Type : PTP, related to unclosed break points. The connection names will have the pattern <CLIENT_ID>,<Number> . Client IDs will be of the format as mentioned below:
   • ESBX_SYSTEM<Event Process Name><Version><RouteName>_C
   • ESBX_SYSTEM<EventProcessName><Version><COMPONENT_NAME>_<RouteName>
3. Double-click the ClientIDs and copy it one after the other. Note: Ignore the route number suffixed to the Client ID.
   
   
   Figure 6: Copying the Client IDs from the Connections section in Dashboard

Step 2: Open Connection Management perspective in eStudio and disconnect the PTP Client Connection identified by the Client IDs

After opening Connection Management perspective in eStuido, perform the following actions in Server Connections panel:

1. Log into FES-JMX and navigate to JMX Connection > Fiorano > etc > AdminService > AdminService node.
   
   
   Figure 7: Navigating to AdminService node
    
2. Right click AdminService node and click View Operations.
3. In the AdminService dialog box, select disconnectClient(clientID) operation on the left navigation bar and paste the Client IDs (copied in Step 2) in the clientID field under Operation tab. Note: Paste the Client IDs one after the other, that is, disconnect one at a time.
4. Click disconnectClient button to invoke operation to disconnect the PTP client connection.
   
   
   Figure 8: Invoking operation to disconnect client
    
5. The result in the Result tab appears as 'true' if the client is disconnected and else it will be 'false'.
   
   
   Figure 9: The result appearing in the Result tab

The result gets reflected in the Dashboard and you may verify that the client IDs which are disconnected from AdminService no more appear in the Dashboard.
Similarly, client connections to peers can be disconnected from FPS-JMX following similar steps in the corresponding sections in FPS.