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

9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

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 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