WebSphere ND 18.104.22.168
We have a case where the endpoint's port was created as 9089 and then changed to 11089.
The Scheduler still uses the original port (9089) for the endpoint instead of 11089.
Which resource does the Scheduler uses to determine the endpoints and the ports?
sajan 0100003PRR42 Posts
Re: Endpoint PORT2012-05-02T11:50:31ZThis is the accepted answer. This is the accepted answer.Linda, could you explain your topology (like if you are using an ND cell with separate server for scheduler and endpoint) and how you changed the port number for the endpoint (on the dmgr and sync'ed the nodes)?
Re: Endpoint PORT2012-05-02T12:01:09ZThis is the accepted answer. This is the accepted answer.Hello Sajan,
The scheduler are on server 1 (SchedulerSrv01) and server 2 (SchedulerSrv02), which is in a cluster (SchedulerCLS01).
The endpoint (THS) has server THSSrv01 and THSSrv02, which is in a cluster (THSBtchCLS01).
Both the Srv01's are on the same LPAR (pS01).
Both the Srv02's are on the same LPAR (pN01), but different from the one above.
I haven't created the server, because it is production, I do not have access to production. What I understand is that the endpoints got created with port 9089 and then changed after the fact to 11089. I've got the people responsible for the production environment to do a scan for port 9089 on the deployment manager.
The only place they could find it was in a template: /config/templates/clusters/THSBtchCLS01/serverindex.xml
I don't know if the nodes were synchronized but the people responsible for the production environment usually do when the create new servers. I've asked them to re-synchronize.
sajan 0100003PRR42 Posts
Re: Endpoint PORT2012-05-02T14:16:48ZThis is the accepted answer. This is the accepted answer.If the dmgr config has the correct port information, and if the node sync worked as expected, all the nodes should have the correct port information. Could you force node sync one more time from the dmgr to all nodes and bounce the entire cell?
Re: Endpoint PORT2012-05-03T11:12:38ZThis is the accepted answer. This is the accepted answer.So which resource does the CG Scheduler use to determine the port?
Does the Scheduler by any chance cache the ports?
Re-synchronize didn't help. Bouncing the Deployment Manager didn't help. Cannot bounce the cell, will affect the other apps in the cell.
Will still bounce the Scheduler, one node at a time as this is production and we cannot affect the already executing jobs.