PH16684: VALIDATION OF EJB TIMER TO SCHEDULER RELATIONSHIP

APAR status

• Closed as program error.

Error description

• If you choose to create a custom scheduler instance and choose
  the JNDI name of the scheduler that has been defined in the
  environment, the scheduler information will be saved in the
  server configuration. But later if you delete that particular
  scheduler from Resources ->  Scheduler list, after you save the
  change, the EJB Timer setting referencing the deleted scheduler
  won't be updated and changes won't be saved. Later you might see
   WSVR0111W + WSVR0040E messages in the log showing the EJB timer
   service cannot be started.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Complete validation is not performed    *
  *                      on EJB Timer and Scheduler              *
  *                      Configuration data elements.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Updates to the server configuration, using either the
  administrative console, or using the administrative command
  line interface, do not run complete validations on EJB Timer
  and Scheduler Configuration data elements.  In particular,
  updates which break required relationships between EJB Timer
  data elements or Scheduler Configuration data elements and
  other data elements are not validated.  Because the required
  relationships are not validated, a configuration update
  may delete a linked data element while showing no validation
  error.
  

Problem conclusion

• Server configuration validation was updated to add rules
  which
  validate relations relating to EJB Timer and Scheduler
  Configuration data elements.  These rules were added:
  
  * An EJB Container which has "Non-Persistent Timer Retry
  Count"
  set to zero may have behavior which is not specification
  compliant.
  
  * An EJB Timer must have an associated Java EE resource
  factory, which must be either a "Scheduler Configuration"
  type
  resource factory, or must be a "Data Source" type resource
  factory.
  
  * A Scheduler Configuration must have two associated Java EE
  resource factories, one which must be a "Data Source" type
  resource factory, and a second which must be a "Work Manager
  Information" type resource factory.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.18 and 9.0.5.4.  For more information, see
  'Recommended Updates for
  WebSphere Application Server':
  http://www.ibm.com/support/docview.wss?
  rs=180&uid=swg27004980
  

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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP