IT05251: A WEBSPHERE MQ FTE AGENT ABENDS WITH A JAVA.LANG.NULLPOINTEREXCEPTION

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.5

APAR status

• Closed as program error.

Error description

• A WebSphere MQ File Transfer Edition agent that is a source
  agent for a transfer ABENDs with a
  java.lang.NullPointerException. An ABEND.FTE file is generated
  containing the following information:
  
  Level: f704-FP3-20130429-1711
  Time: 29/10/2014 14:46:43:340 GMT
  Thread: 26
  (TransferSender[414d5120514d434f524344315520202043e79a5374e30020
  ])
  Class: com.ibm.wmqfte.thread.FTEThread
  Instance: 20d620d6
  Method: uncaughtException
  Probe: ABEND_001
  Cause: java.lang.NullPointerException
  java.lang.NullPointerException
   at
  com.ibm.wmqfte.transfer.impl.TransferSenderRunnable.run(Transfer
  SenderRunnable.java:640)
   at java.lang.Thread.run(Thread.java:761)
   at com.ibm.wmqfte.thread.FTEThread.run(FTEThread.java:64)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects all users of WebSphere MQ File Transfer
  Edition and WebSphere MQ Managed File Transfer.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A WebSphere MQ File Transfer Edition (FTE) agent that was acting
  as a source agent for a transfer used an object, known as a
  TransferFrame, to maintain state information regarding the
  amount of source file data that it transmitted as part of a file
  transfer. If the WebSphere MQ FTE agent was unable to initialise
  this TransferFrame object at the start of processing a file
  transfer request, for example because it could not read the
  source file for the transfer, then it would put this transfer
  into recovery. Such a case would occur if a WebSphere MQ FTE
  protocol bridge agent was used to transfer a file from a source
  FTP file server and the protocol bridge agent was unable to
  connect to the file server, for example.
  
  Since APAR IC89838, the agent could attempt to access the
  TransferFrame object that, in the case above, would not have
  been initialised; i.e., would be null. As a result a
  java.lang.NullPointerException exception occurred. This resulted
  in the WebSphere MQ FTE agent generating an ABEND file,
  reporting the issue before stopping.
  

Problem conclusion

• The WebSphere MQ File Transfer Edition code has been updated to
  guard against a null TransferFrame object in the case where the
  TransferFrame object could not be initialised successfully.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.4.5
  v7.5       7.5.0.5
  v8.0       8.0.0.2
  
  The latest available FTE maintenance can be obtained from
  'Fix List for WebSphere MQ File Transfer Edition 7.0'
  http://www-01.ibm.com/support/docview.wss?uid=swg27015313
  
  The latest available MQ 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 FILE TRANSF

• Fixed component ID

  5724R1000

Applicable component levels

• R704 PSY

     UP