PI08932: DISABLE CHECKING FOR TIMERS FOR MODULES THAT CONTAIN MANAGED BEANS ONLY AND NO EJBS

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Using @ManagedBean annotation causes runtime application manager
  to invoke a manage bean component and it's looking for
  timer service. If the EJB timer service is misconfigured, the
  application fails to start.
  

Local fix

• Please follow the below instructions to disable time server.
  
  
  1) Login to console.
  2) Under Servers > Application servers > server_name > EJB
  Container
  settings > EJB timer service settings
  set "Number of timer threads" to "0"
  3) Restart the server .
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Serbver V8.5      *
  *                  users of javax.annotation.ManagedBean.      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Enterprise Java Bean (EJB) timer    *
  *                      database is checked even if a module    *
  *                      contains managed beans only and no      *
  *                      EJBs.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The implementation of javax.annotation.ManagedBean is shared
  with the EJB container.  When an EJB module is started, the
  EJB container needs to check the EJB timer database to see if
  any timers need to run.  Managed beans do not support timers,
  so this checking is unnecessary for modules that contain
  managed beans only and no EJBs.
  

Problem conclusion

• The logic is adjusted to avoid checking the EJB timer database
  for modules that contain managed beans only and no EJBs.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2.  Please refer to the Recommended Updates
  page for delivery information:
  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP