IBM Support

PH44389: IN WEBSPHERE APPLICATION SERVER V9.0.5.X, MODIFYSIBJMSACTIVATIONSPEC COMMAND SETS JNDI DESTINATION LOOKUP TO NULL

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

  • In WebSphere Application Server v9.0.5.x, MDB Activation
    Specification configured against the SIB JMS Provider is
    modified to update certain properties using the
    AdminTask.modifySIBJMSActivationSpec wsadmin command and the
    application server is restarted. During the restart, the
    application fails to start and throws the following error:
    
    J2CA0137E: The ActivationSpec validate() method failed with an
    InvalidPropertyException. The  ActivationSpec is jms/xxxActivat
    ionSpec(com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl),
    lusters/xxxcluster/resources.xml#J2CResourceAdapter_nnnand is as
    xxxApp#xxxModules.jar#xxxActivationSpec. See the following list
    of failed properties along with their values:
    
    
    destination null
    destination null. The exception is:
    javax.resource.spi.InvalidPropertyException: CWSJR1181E: The JMS
    activation specification has invalid values - the reason(s) for
    failing to validate the JMS activation specification are:
    [CWSJR1188E: The destination on a JMS activation specification
    must be given a value, CWSJR1192E: JMS activation specs using a
    destination type of queue must have a destination of type
    [com.ibm.websphere.sib.api.jms.JmsQueue] but the destination
    passed was of type [null]]
    	at com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl.vali
    date(JmsJcaActivationSpecImpl.java:1531)
    	at com.ibm.ejs.j2c.ActivationSpecWrapperImpl.validateActivatio
    nSpecInstance(ActivationSpecWrapperImpl.java:1467)
    	at com.ibm.ejs.j2c.ActivationSpecWrapperImpl.createAndInitiali
    zeActivationSpecInstance(ActivationSpecWrapperImpl.java:1416)
    	at com.ibm.ejs.j2c.ActivationSpecWrapperImpl.activateEndpoint(
    ActivationSpecWrapperImpl.java:318)
    	at com.ibm.ejs.j2c.RAWrapperImpl.activateEndpoint(RAWrapperImp
    l.java:1112)
    	at com.ibm.ejs.j2c.RALifeCycleManagerImpl.activateEndpoint(RAL
    ifeCycleManagerImpl.java:1825)
    	at com.ibm.ejs.container.MessageEndpointFactoryImpl.activateEn
    dpoint(MessageEndpointFactoryImpl.java:152)
    	at com.ibm.ws.runtime.component.EJBContainerImpl.startMDBs(EJB
    ContainerImpl.java:4394)
    	at com.ibm.ws.runtime.component.WASEJBRuntimeImpl.startMDBs(WA
    SEJBRuntimeImpl.java:659)
    	at com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.startMod
    ule(AbstractEJBRuntime.java:585)
    	at com.ibm.ws.ejbcontainer.runtime.SharedEJBRuntimeImpl.startM
    odule(SharedEJBRuntimeImpl.java:347)
    

Local fix

  • Explicitly specify the destinationJNDIName property in the
    modifySIBJMSActivationSpec command, which ensures it is
    persisted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When calling the                        *
    *                      modifySIBJMSActivationSpec command in   *
    *                      wsadmin, if no value is provided for    *
    *                      the destinationJndiName or              *
    *                      destinationLookup properties then an    *
    *                      Exception can be thrown                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The code attempts to make the destinationJndiName take
    precedence over destinationLookup, but always attempts to set
    a new value in the update, so if neither is set then the
    destinationLookup is set to null, which is not a valid value
    and so an Exception is thrown
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH44389

  • 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

    2022-02-23

  • Closed date

    2023-02-27

  • Last modified date

    2023-02-27

  • 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

[{"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:
28 February 2023