Getting WorkManager scheduleWork() to throw WorkRejected ?

Question

I'm writing a socket server to service persistent inbound TCP sockets. I would like scheduleWork() to throw an exception if no threads are available to service the work object parameter.
          There is an application scoped work manager with a max-threads constraint . I call scheduleWork() to queue a socket handling work object in the work manager. If all of the threads are in use in the work manager , the work requests are still accepted.
          However, if no threads are available at the time the work object is queued I would like the work manager to immediately throw a WORK_REJECTED exception from scheduleWork() . Currently, the queued work objects are dormant until a thread is made available in the work manager.
          I have tried using the capacity constraint w/o success. I have read what appears to be conflicting descriptions of capacity : One is that it should be equal to maxThreads + max queued threads, the other is that it should equal max queued threads. In my case, max queued is equal to 0.
          I have also tried using the WorkManager.IMMEDIATE timeout value, but that really depends upon system load. i.e. I may not be out of threads as much as being a little slow in moving the worker to the WORK_STARTED state.
          Does anybody know how I can get a work manager to throw an exception when there are no threads available right now ?
          Thanks,
          John

Answer 1

This seems to be callout issue.
can you try with default callout Exmaple first:
http://docs.oracle.com/cd/E23943_01/user.1111/e10229/callouts.htm#CHDEFBDG