Dieudonne - Posted April 23, 2019 Share Posted April 23, 2019 Someone have the same problem If the EMS is restarted, TEA is not able to update the status of BwAgent from Unreachable to Running. My configuration (BW, TEA, EMS) installed on 3 different servers to reproduce the bug. TEA 2.3 + last hotfix EMS 8.4 BWAgent (BW 6.5.1) register with TEA Agent EMS register with TEA Status at the test init ------- BWAgent (AX-ESB-BW1-DEV) ====> Running EMS Tea Agent ====> Running EMS ====> Running Action to reproduce the problem: 1 - Stop EMS Instance Logout from TEA and Login to TEA to check the new status of BWAgent. Status ------- BWAgent (my host) ====> From TEA i cannot have information about BWAgent - nothing to see - i can use API to confirm that Agent is stopped EMS Tea Agent ====> Running EMS Intance ====> Stopped 2- start EMS Instance after about 1 minute New Status ------- BWAgent (my host) ====> Unreachable EMS Tea Agent ====> Running EMS ====> Running Conclusion: The BWAgent is Running, but in the TEA the status is always Unreachable. Then I can conclude that TEA is not able to update the status of BwAgent from Unreachable to Running. I can see from result API that the agent is Running but, TEA [ { "name": "AX-ESB-BW-DEV", "state": "Running", "tibcoHome": "----------", "pid": "3268", "version": "6.5.1", "description": "TIBCO ActiveMatrix BusinessWorks version 6.5.1, build V9, 2019-02-06", "installationName": "---------------", "adminMode": "enterprise", "configState": "InSync", "machineName": "AX-ESB-BW-DEV", ----------- Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now