JR53781: INFORMATION SERVER PATCH INSTALLATION FAILS WITH ERROR JAVAX.MANAGEMENT.REFLECTIONEXCEPTION

IBM InfoSphere Information Server, Version 11.5.0.1 (Fix Pack 1)

APAR status

• Closed as program error.

Error description

• InfoSphere Information Server patch or fix pack installation on
  the engine tier fails with an error similar to:
  CDIIN5123E: ExecuteScriptAction failed: the process returned
  error code 1.:
   Error The following exception has occurred:
  null; nested exception is:
      javax.management.ReflectionException
  
  If you look at the installation log in
  
  Windows: %TEMP%\ibm_is_logs
  Unix or Linux: /tmp/ibm_is_logs
  
  You find:
  2015-06-26T09:35:39.200, INFO: CDIIN2753I:Command Array: /bin/sh
  /opt/IBM/InformationServer/ASBNode/bin/AgentConfig.sh -user
  isadmin -password ******** -install
  /opt/IBM/InformationServer/logs/agent_config/<name varies>.xml,
  env = null, workingDir =c
  2015-06-26T09:35:42.579, WARNING:
  com.ibm.is.install.core.CommonProcess  Exit Code: 1,  Error The
  following exception has occurred:
  null; nested exception is:
  javax.management.ReflectionException
  2015-06-26T09:35:42.582, SEVERE:
  com.ibm.is.install.engine.runtime.InstallEngine
  
  com.ibm.is.install.exception.ActionException: CDIIN5123E:
  ExecuteScriptAction failed: the process returned error code 1.:
   Error The following exception has occurred:
  null; nested exception is:
      javax.management.ReflectionException
  
  CDIIN5106I: Details:
  InstallAction (_id =
  enable.cas.handlers.with.agent.config.service,
  _installUnitModelId = <name varies>)
      at
  com.ibm.is.install.engine.action.builtin.AbstractExecuteAction.e
  xecute(AbstractExecuteAction.java:319)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.executeAction(In
  stallEngine.java:1430)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.processInstallAc
  tionStep(InstallEngine.java:1370)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.processActionSte
  p(InstallEngine.java:1254)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.processInstallSt
  ep(InstallEngine.java:419)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.processAllSteps(
  InstallEngine.java:399)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.run(InstallEngin
  e.java:235)
      at
  com.ibm.is.install.engine.runtime.InstallEngine.execute(InstallE
  ngine.java:715)
      at
  com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonito
  r.execute(InstallEngineMonitor.java:368)
      at
  com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonito
  r.beginInstall(InstallEngineMonitor.java:252)
      at
  com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonito
  r.access$100(InstallEngineMonitor.java:40)
      at
  com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonito
  r$1.run(InstallEngineMonitor.java:119)
      at java.lang.Thread.run(Thread.java:853)
  

Local fix

• This error is typically caused by connectivity issues between
  the services tier and the engine tier.
  
  You can get more information as to the cause by turning on the
  following trace:
  turn on the WebSphere tracing, go to the Troubleshooting twisty:
  
  Logging and tracing > "running app servers" > Change log detail
  levels, select Runtime tab
  
  The default tracing is:
  *=info: com.ibm.iis.xmeta.*=warning: com.ibm.xmeta.*=warning
  
  Add log detail levels as below (one line, wrapped):
  
  *=info: com.ibm.iis.xmeta.*=warning: com.ibm.xmeta.*=warning:
  com.ibm.iis.isf.agent.*=all:
  com.ibm.is.isf.j2ee.security=all:com.ascential.acs.security.*=al
  l:com.ibm.iis.isf.security.*=all:
  
  Click apply
  
  You do not have to restart WebSphere.  Note this setting only
  applies to the current application server, so if you are using
  multiple nodes, you have to repeat for each or temporarily shut
  down all but one.
  
  After Clicking Apply, wait about 10 seconds, then run the
  failing AgentConfig command from the install log.  For example,
  for the above log entry:
  
  
  Change to the workingDir:
  > cd /opt/IBM/InformationServer/ASBNode/bin
  Run the command:
  > /opt/IBM/InformationServer/ASBNode/bin/AgentConfig.sh -user
  isadmin -password ******** -install
  /opt/IBM/InformationServer/logs/agent_config/<name varies>.xml
  
  After running the command, go back into the Change log detail
  levels and change it back to the default tracing and select
  Apply.  On all application servers where you enabled the trace,
  under the application server profile/logs/<app server name>
  there should be at least one trace file.
  
  
  In the trace file, look for two messages.  The first will be
  like the following:
  [7/2/15 10:42:59:059 CST] 00001758 AgentConfigur 2   Enter:
  AgentConfigurationImpl.getAgentMetaData(''<agent hostname>'',
  <agent port>)
  
  The second message will be similar to this:
  
  [7/2/15 10:42:59:131 CST] 00001758 AdapterConfig 1   Uncaught
  Exception: {Connection refused to host: 127.0.0.1; nested
  exception is:
      java.net.ConnectException: Connection refused}
                                   java.rmi.ConnectException:
  Connection refused to host: 127.0.0.1; nested exception is:
      java.net.ConnectException: Connection refused
      at
  sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631
  )
      at
  sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.jav
  a:228)
      at
  sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:2
  14)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:140)
      at
  java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod
  (RemoteObjectInvocationHandler.java:205)
      at
  java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjec
  tInvocationHandler.java:159)
      at com.sun.proxy.$Proxy81.registerHandlerTypeAgent(Unknown
  Source)
      at
  com.ibm.iis.isf.agent.ra.impl.AdapterConfigurationImpl.enableHan
  dlerTypeAgent(AdapterConfigurationImpl.java:371)
      at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown
  Source)
      at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:55)
      at java.lang.reflect.Method.invoke(Method.java:613)
      at
  com.ibm.iis.isf.agent.config.server.impl.AgentConfigurationBean.
  invoke(AgentConfigurationBean.java:560)
      at
  com.ibm.iis.isf.agent.config.server.impl.AgentConfigurationImpl.
  enableHandlerTypeAgentInternal(AgentConfigurationImpl.java:1155)
  ....
  
  If the IP address in the "Connection refused to host:
  ###.###.###.###" is 127.0.0.1, the most probable cause is that
  the services tier is not correctly resolving the IP address for
  the agent hostname in the first message.
  
  If the IP address is the correct IP address for the engine tier,
  then the most probably cause is a firewall issue.  The services
  tier need to be able to communicate to the engine tier on two
  ports for this interface, the port <agent port> in the message
  above, and a random port number greater than 1024
  
  Instead of using a random port number, you can fix this to a
  specific port by specifying agent.objectport=# in the
  IS_install_path/ASBNode/conf/agent.properties file after you
  complete the installation. After designating a specific port,
  restart the ASB agent so that the change takes effect.  Ensure
  the static port is accessible through your fire wall.
  
  Run the AgentConfig command again to confirm that it is now
  working. If it is not working, contact IBM Customer Support.
  

Problem summary

• InfoSphere Information Server patch or fix pack installation on
  the engine tier fails with an error similar to:
  CDIIN5123E: ExecuteScriptAction failed: the process returned
  error code 1.:
   Error The following exception has occurred: null; nested
  exception is:
      javax.management.ReflectionException
  

Problem conclusion

• Changed the wording and logging level of error messages, and
  added checks for when they are reported.
  

Temporary fix

• Turn on trace to get more information about the cause of the
  error in SystemOut.log.
  If the IP address in the "Connection refused to host:
  ###.###.###.###" is 127.0.0.1, the most probable cause is that
  the services tier is not correctly resolving the IP address for
  the agent hostname in the first message.
  If the IP address is the correct IP address for the engine tier,
  then the most probable cause is a firewall issue.
  The services tier need to be able to communicate to the engine
  tier on two ports for this interface, the port <agent port> in
  the message above, and a random port number greater than 1024.
  Instead of using a random port number, you can fix this to a
  specific port by specifying agent.objectport=# in the
  IS_install_path/ASBNode/conf/agent.properties file after you
  complete the installation. After designating a specific port,
  restart the ASB agent so that the change takes effect.&#160; Ensure
  the static port is accessible through your fire wall.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• RB50 PSY

     UP