IT20533: MQSICHANGEBLUEMIXREPORTING FAILING WITH SOCKETEXCEPTION

APAR status

• Closed as program error.

Error description

• When running the mqsichangebluemixreporting command to
  configure an IIB instance for Bluemix Logmet reporting by
  providing Bluemix credentials,
  for example:
  
  mqsichangebluemixreporting {node} -g -l active -r us-south -o
   {org} -a {space} -u {user} -p {password} -d
  
  The command fails reporting BIP8075E "java.net.SocketException:
  Connection reset".
  
  
  Additional Symptom(s) Search Keyword(s):BIP8075E,
  mqsichangebluemixreporting, Bluemix Logmet
  

Local fix

• The issue can be avoided by using the alternative steps to
  manually obtain the required Bluemix space and logging tokens
  and then using the mqsichangebluemixreporting command with the
  following options
  
     mqsichangebluemixreporting {node} -g -l active -x   -i
  {spaceIdentifier} -t {loggingToken}
  
  As detailed in Knowledge Center topic:
  ?Configuring an integration server and loading the IBM
  Integration Bus Kibana dashboard manually?
  https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ib
  m.etools.mft.doc/bz91188_.htm
  
  Note: The topic and command usage message BIP8372 incorrectly
  show a "-f" flag, please use correct syntax as show above with
  -x -i -t.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V10.0 who use Bluemix Logmet
  reporting.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When running the mqsichangebluemixreporting command to configure
  an IBM Integration Bus instance for Bluemix Logmet reporting by
  providing Bluemix credentials, for example:
  
  mqsichangebluemixreporting {node} -g -l active -r us-south -o
  {org} -a {space} -u {user} -p {password} -d
  
  The command fails reporting BIP8075E "java.net.SocketException:
  Connection reset".
  

Problem conclusion

• The mqsichangebluemixreporting command has been corrected to go
  directly to the required SSL protocol when connecting to Bluemix
  to acquire Logmet logging tokens.
  
  The  command usage message BIP8372 and Knowledge Center topic
  bz91188_ will also be updated to show the required flags when
  using the alternate manual setup.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.9
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels

• RA00 PSY

     UP