Error Message :
log4j:ERROR Failed to flush writer,
java.io.IOException: Bad file descriptor
Note: This article is meant for a CCB administrator only.
A CCB batch job gets stuck with the thread pool workers and is unable to proceed. The following messages will be seen in the job report:
- 2016-12-15 22:40:09,064 [pool-1-thread-4] INFO (support.cluster.MemberLeftThread) Removing member id: 46 from cache because it left cluster
- 2016-12-15 22:40:09,066 [pool-1-thread-4] INFO (support.cluster.ClusteredNode) Removing member 46 from the cluster cache
- 2016-12-15 22:41:58,998 [pool-1-thread-1] INFO (support.cluster.MemberLeftThread) Removing member id: 106 from cache because it left cluster
- 2016-12-15 22:41:59,000 [pool-1-thread-1] INFO (support.cluster.ClusteredNode) Removing member 106 from the cluster cache
- 2016-12-15 00:02:33,153 [Main Thread] INFO (api.batch.BatchRunStatusHelper) Ending BRT values - batch nbr: 225, rerun nbr: 0, status: 40
- 2016-12-15 00:02:33,155 [Main Thread] INFO (api.batch.BatchRunStatusHelper) Batch Number: 225
- 2016-12-15 00:02:34,167 [Main Thread] INFO (api.batch.SubmitBatch) Run ended successfully with exit code 0
Return Code 0
Check to ensure the job is running through the thread pool worker by following these steps:
ps -ef | grep submit
This will check to ensure there are TPW processes running.
Oracle Resources for Best Practices:
Batch Best Practices for Oracle Utilities Application Framework based products (Doc Id: 836362.1)
Production Environment Configuration Guidelines (Doc Id: 1068958.1)
Within Automic: Kill the thread pool workers and restart it.
Outside of Automic: Submit the job from the CCB front end.
Root Cause: This is not an Automic issue. It is an issue with Oracle Utilities Customer Care and Billing.
Fix Status: No Fix