IBM Support

PI80971: ALLOW MODIFICATION OF MESSAGE DRIVEN BEAN BINDINGS IN OSGI APPLICATIONS TO BIND TO LISTENER PORTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Binding a Message Driven Bean in an OSGi application to a
    listener port can be configured in the application's extended
    deployment descriptor.  However, there is no administrative
    mechanism to configure such a binding once the application has
    been installed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of OSGi  *
    *                  applications                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message Driven Beans packaged in OSGi   *
    *                      applications cannot be bound to         *
    *                      listener ports using wsadmin.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Message Driven Beans that are packaged in OSGi applications
    may be bound to either listener ports or activation
    specifications by specifying the binding in the packaged
    ibm-ejb-jar-bnd.xml file.  Both types of bindings are
    supported by the runtime however there is no administrative
    mechanism to add or modify a binding to a listener port.
    

Problem conclusion

  • The MDBBindingsStep was modified to take an additional
    optional parameter to allow specification of a listener port.
    
    Below is an example of the editCompUnit command specifying an
    MDB to be bound to a listener port with name
    "MyListenerPortName":
    
    AdminTask.editCompUnit('[-blaID WebSphere:blaname=MyBLA -cuID
    WebSphere:cuname=componenttest.mdb_0001.eba -MDBBindingsStep
    [[componenttest.mdb.cba_1.0.0/componenttest.mdb.cba.bundle
    1.0.0 META-INF/ejb-jar.xml/CBAMessagingMDB "" "" ""
    "MyListenerPortName"]]]')
    
    In the event that both an activation specification name and a
    listener port name are specified in the MDBBindingsStep then
    the activation specification will be used and the listener
    port binding will be ignored.
    
    The administrative console will not display bindings to
    listener ports but will not discard the listener port binding
    unless a new activation specification binding is set.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.13 and 9.0.0.6.  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 number

    PI80971

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-04

  • Closed date

    2017-09-13

  • Last modified date

    2017-09-13

  • 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

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021