IV89948: XMS .NET code does not throw an exception while using a disposedsession object

APAR status

• Closed as program error.

Error description

• XMS.NET Application was able to use a Session object to create
  resources, even after the Session object is disposed. When a
  disposed Session object is used, XMS.NET should throw an
  exception,but it wasn't throwing any exception.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All XMS.NET Application users who depend on "using" block to
  dispose the Session Object.
  
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a XMS.NET Session object is created within a using block,at
  the end of the using block, .NET disposes all the objects which
  where created as part of that block.Similarly Session is also
  disposed. But as part of this dispose,XMS.NET doesn't close all
  the resources.While using a disposed session object to create
  new XMS objects, XMS should throw an exception,which wasn't the
  case in this particular scenario rather XMS is allowing to
  create new objects but the objects which were created using a
  disposed session object weren't working as expected because few
  resources which were dependent on the Session were already
  closed as part of the "Dispose" which was called by .NET at the
  end of using block.
  

Problem conclusion

• XMS.NET should close all the resources when
  IDisposable.Dispose() is called on a Session object.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.8
  v8.0       8.0.0.6
  v9.0 LTS   9.0.0.1
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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

  WMQ XMS V 8.0

• Fixed component ID

  5724H7257

Applicable component levels

• R800 PSY

     UP