Batch Controller Failed to Lock Configured Socket
(Doc ID 2177125.1)
Last updated on MAY 16, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Batch Scheduler
After upgraded from 7.4 PS20 to 7.5 PS14, it was noticed that starting batch controller did not work when it was done by pin_ctl.
The newest (7.5 PS14) batch controller did not lock socket configured under "batch.lock.socket.addr" in Infranet.properties. Due to this pin_ctl was unable to recognize whether service has started using netstat command and this particular port. And it was working just fine after replaced the batch.jar to the one before PS14 (i.e. batch.jar.22191910.bak).
No error message has been generated in .pinlog nor .log file of batch_controller. The port was also open and not taken by any other service, as another instance of BRM (7.4) could start Batch Controller using the same port in parallel with 7.5 instance, despite of it was being located on the same machine.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document