IBM Support

PH33656: WSADMIN JYTHON COMMAND DOES NOT CHANGE STATUS OF SCHEDULER JNDI NAME

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • - When we ran this wsadmin command, the Scheduler JNDI name is
    not set and remains at None:
    
    AdminConfig.modify('(cells/TESTCell01/nodes/TESTNode01/servers/s
    erver1|server.xml#EJBTimer_1544523702297)', '[[schedulerJNDIName
     "wm/schel"]]')
    
    - The defect that causes this problem is PH19286:
    https://www.ibm.com/support/pages/apar/PH18268
    
    - They would have had the same problem in 8.5.5.17+
    
    - The defect violates the documentation (really) in that it
    places a non-null datasourceJNDIName property at a higher
    precedence than schedulerJNDIName which it shouldn't (see:
    https://www.ibm.com/support/knowledgecenter/en/SSEQTP_9.0.5/com.
    ibm.websphere.base.doc/ae/txml_ejbTimer_config.html )
    
    Specifically they moved the previously unconditional
    setSchedulerJNDIName() call into a block controlled by
    "(eJBTimer.getDatasourceJNDIName() == null ||
    eJBTimer.getDatasourceJNDIName().trim().length() == 0)" -- so it
    doesn't happen if this is set at all.  This is wrong relative to
    the documented precedence of properties.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server versions 8.5.5.17 to 8.5.5.19, and   *
    *                  9.0.5.3 to 9.0.5.7.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: EJB timer service configured to use a   *
    *                      custom scheduler nstance ithrough       *
    *                      wsadmin is not recognized correctly     *
    *                      by the admin console EJB timer          *
    *                      service settings panel.                 *
    *                      panel.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A custom scheduler instance provides more configuration
    options than the internal EJB timer service pre-configured
    scheduler instance. When running in a cluster environment, a
    custom scheduler allows all cluster members to run with a
    single scheduler instance.
    After a custom scheduler instance is configured to be used in
    the EJB timer service through wsadmin, the admin console EJB
    timer service panel recognizes that a customer scheduler is
    used but fails to identify which scheduler is used.
    

Problem conclusion

  • To workaround the problem, configure the custom scheduler
    instance through the admin console. In the EJB timer service
    settings panel, select the JNDI name of a custom scheduler
    instance from the drop down list and save the changes.
    
    The problem has been fixed to display the JNDI name of a custom
    scheduler instance correctly in the admin console EJB timer
    service settings panel.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.20 and 9.0.5.8. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH33656

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-21

  • Closed date

    2021-03-16

  • Last modified date

    2021-03-16

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 November 2021