JR31987: INFORMATION SERVICES DIRECTOR 801: WISD JOB IS NOT SPAWNING NEW JOBS WHEN ADDITIONAL REQUESTS ARE BUILDING UP.

APAR status

• Closed as program error.

Error description

• We are in process of doing performance testing of the Web
  Services. When the service requests queue up, the WISD job is
  expected to spawn new jobs based on the minimum number of jobs,
  number of requests in the queue and Delay. It seems like since
  day before yesterday, WISD is not able to spawn new jobs on
  DataStage. It does start new jobs if I increase the minimum
  number of Active jobs manually.
  
  Looking at the Webshpere SystemOut.log sent I see the error:
  
  Queue Limit of 0 Exceeded.
  
  That is embedded in the following error:
  
  WSWS3228E: Error: Exception: WebServicesFault faultCode:
  {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
  on
  faultString: javax.ejb.EJBException: nested exception is:
  javax.transaction.TransactionRolledbackException: CORBA
  TRANSACTION_ROLLEDBACK 0x0 No; nested exception is:
  org.omg.CORBA.TRANSACTION_ROLLEDBACK:
  javax.transaction.TransactionRolledbackException: ; nested
  exception is:
  javax.ejb.EJBException: nested exception is:
  javax.resource.ResourceException: Queue Limit of 0 Exceeded.
  vmcid: 0x0
  minor code: 0 completed: No faultActor: null ...
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Any user of Information Services Director.
  ****************************************************************
  PROBLEM DESCRIPTION:
  When the ASBAgent is restarted it queries the IS Server for the
  agent's current configuration. An incorrect query is being
  performed and some of the configuration data is not filled in.
  In particular, the Max Queue Size of the operation queue is
  returned as 0. This causes requests that cannot be handled
  immediately by a provider instance to not be queued and an
  exception is thrown (QueueLimitExceededException).  This also
  causes prevents the new job threshold from being reached which
  means that no new jobs are started when a load is present.
  ****************************************************************
  RECOMMENDATION:
  Apply patch JR31987
  ****************************************************************
  

Problem conclusion

• This was previously fixed for 8.1.  A patch has been created for
  8.0.1 (patch JR31987) to fix the incorrect query.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• AGENT
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSY

     UP