PI99759: SPECIFYING A VARIABLE AS THE HTTP PORT VALUE RESULTS IN A NUMBERFORMATEXCEPTION WHEN USING XSCMD -C SHOWMAPSIZES

APAR status

• Closed as program error.

Error description

• When using the command "xscmd -c showMapSizes", the following
  error message is returned when using a variable for the port
  value:
  
  Bad port number: "": java.lang.NumberFormatException: For input
  string: ""
  
  After activating the finest trace level for xscmd, the root
  exception is found in the resulting trace.log:
  
  [4/24/18 15:35:00:207 CEST] 0000001d id=
  com.ibm.ws.xs.admin.util.WXSAdminCatalogConnection 1
  unexpected2 trying the JMX address for the catalog server we
  connected to on the LocationService localhost:2809
  java.net.MalformedURLException: Bad port number: "":
  java.lang.NumberFormatException: For input string: ""
  at
  javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:
  222)
  at
  com.ibm.ws.xs.admin.util.WXSAdminCatalogConnection.getJMXConnect
  or(WXSAdminCatalogConnection.java:463)
  at
  com.ibm.ws.xs.admin.wxscli.WXSAdminCLI.main(WXSAdminCLI.java:451
  )
  at com.ibm.ws.xs.xscmd.Activator.start(Activator.java:130)
  at
  org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(Bund
  leContextImpl.java:774)
  at
  org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(Bund
  leContextImpl.java:1)
  at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:650)
  at
  org.eclipse.osgi.internal.framework.BundleContextImpl.startActiv
  ator(BundleContextImpl.java:767)
  at
  org.eclipse.osgi.internal.framework.BundleContextImpl.start(Bund
  leContextImpl.java:724)
  at
  org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(E
  quinoxBundle.java:932)
  at
  org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.
  startWorker(EquinoxBundle.java:309)
  at org.eclipse.osgi.container.Module.doStart(Module.java:566)
  at org.eclipse.osgi.container.Module.start(Module.java:434)
  at
  org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.i
  ncStartLevel(ModuleContainer.java:1582)
  at
  org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.i
  ncStartLevel(ModuleContainer.java:1562)
  at
  org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.d
  oContainerStartLevel(ModuleContainer.java:1533)
  at
  org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.d
  ispatchEvent(ModuleContainer.java:1476)
  at
  org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.d
  ispatchEvent(ModuleContainer.java:1)
  at
  org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(E
  ventManager.java:230)
  at
  org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run
  (EventManager.java:340)
  
  
  In the server.xml of the catalog, the http endpoints is defined
  as follows:
  <httpEndpoint host="*" httpPort="${http.port}"
  httpsPort="${https.port}" id="defaultHttpEndpoint"/>
  
  with "https.port" defined in the bootstrap.properties as:
  https.port=9443
  
  The problem does not occur when the https port is defined as
  httpsPort="9443", wich a hardcoded port value.
  

Local fix

• Define httpsPort as a hardcoded port value in the server.xml of
  the catalog server.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere eXtreme Scale Liberty    *
  *                  Deployment that use xscmd after setting     *
  *                  the httpsPort value via the                 *
  *                  bootstrap.properties file.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: An exception is thrown by               *
  *                      xscmd when httpsPort in the             *
  *                      catalog server server.xml references    *
  *                      a bootstrap.properties file value.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The existing code expected that httpsPort is set literally and
  attempts to parse the value as an integer.
  

Problem conclusion

• A change was made to the code to retrieve the value from the
  properties file when referenced. An interim fix is provided
  upon request.
  

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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels