10 Performing Maintenance and Troubleshooting

After you install MSS in an IPv6 environment, you may receive the following error in the AppServerLog.xml file:

Error initializing the MetaSolv Solution Sender:
javax.naming.CommunicationException:
t3:// 2606:b400:2010:484b:f13b:4672:38b7:5af9:9065:
Destination 2606:b400:2010:484b:f13b:4672:38b7:5af9,
9065 unreachable; nested exception is:
java.net.ConnectException: Connection refused: no further information;
No available router to destination [Root exception is java.net.ConnectException:
t3:// 2606:b400:2010:484b:f13b:4672:38b7:5af9:9065:
Destination 2606:b400:2010:484b:f13b:4672:38b7:5af9,
9065 unreachable; nested exception is:
java.net.ConnectException: Connection refused: no further information;
No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.
toNamingException(ExceptionTranslator.java:40)

This message is thrown if the Integration Server, Event Server and System Task Server are enabled. If this error repeatedly occurs (even after the server is up and running successfully), you must enable the HTTP Tunneling option through the WebLogic administrative console. To enable HTTP Tunneling perform the following:

1. Login to the WebLogic administrative console.

2. Select Home, Summary of Services, and then Summary of Servers.

3. Select AdminServer.

4. Enable the Tunneling option.

Once the tunneling option is set, you can ignore the single issuance of the error message.

During the installation of MSS, you may have an issue on the creation of the NameService.ior file and no error messages existing in the log files. To resolve this issue, you need to ensure that the following permissions are on the directories and files within the MSS home directory structure.

Another error can occur when starting the server with any one of the CORBA servers enabled, and the server can throw the following error in the mss.log file:

Tried and failed to open file: MSLV_HOME/m63domain/appserver/ior/NameService.ior
SEVERE Exception while converting string to objectorg.omg.CORBA.BAD_PARAM:
Invalid or unreadable URL/IOR: file:///MSLV_HOME/m63domain/appserver/ior/NameService.ior
vmcid: 0x0  minor code: 0  completed: No

Table 10-1 lists the directories and permissions that you need to address where MSLV_Home is the directory for the MSS home directory and MSS_Server_Name is the appropriate MSS server name.

These problems can occur because of the existing permissions on the files and directories in the environment. Once you set the permissions correctly, restart your server, the IOR file should exist in the MSLV_Home/MSS_Server_Name/appserver/ior directory, and no open file error should exist in the mss.log file.

You can ignore the following warning message that appears in the appserver.mss.log file during Web Service deployment:

<Warning> <com.sun.xml.ws.wsdl.PayloadQNameBasedOperationFinder> <BEA-000000> <Non unique body parts! In a port, as per BP 1.1 R2710 operations must have unique operation signature on the wire for successful dispatch. Methods [getServiceLocationRequest, getEntityByKeyRequest] have the same request body block {http://www.openuri.org/}getEntityByKeyRequest. Method dispatching may fail, runtime will try to dispatch using SOAPAction. Another option is to enable AddressingFeature to enabled runtime to uniquely identify WSDL operation using wsa:Action header.>

This Warning message is related to getServiceLocationRequest and getEntityByKeyRequest APIs, because both the APIs use the same request structure. Because customers have used these two APIs on their integrations in prior versions of MSS, such as 6.2.1, these two APIs are also available in MSS 6.3.0, for customers migrating to the MSS 6.3.0 release.

After you create the domain and install the MSS application using IPv6 address, you may encounter the following issues:

• You are unable to access the WebLogic Server Administration Console using Internet Explorer and the following error message appears:

  The proxy could not connect to the destination in time. Please verify the site you are attempting to access and retry.
  

• You are unable to log in to the MSS application and the following error message appears:

  The user ID you entered is not valid. Please use a valid User ID or ask your manager for assistance.
  

To resolve both the issues, do the following:

1. Start Internet Explorer.

2. From the Tools menu, select Internet Options.

   The Internet Options window appears.

3. Click the Connections tab, and then click LAN Settings.

   The Local Area Network (LAN) Settings window appears.

4. Under the Automatic configuration section and the Proxy server section, deselect all the check boxes.

5. Click OK, which returns you to the Internet Options window.

6. Click OK.

The Runtime Information Page is not displayed and the following error message appears:

Error 500--Internal Server Error
From RFC 2068 HyperText Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.

And the MSS error log reflects the following:

javax.servlet.jsp.JspException: No collection found
at org.apache.struts.taglib.logic.IterateTag.doStartTag(IterateTag.java:281)
at jsp_servlet.__runtimeinfo._jspService(__runtimeinfo.java:594)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
Truncated. see log file for complete stacktrace

To resolve this issue, you must enable HTTP tunneling in the WebLogic Server Administration Console.

If you try to connect to the WebLogic Server by specifying an IPv6 address in the Admin Host field of the MSS installer, the check box to select the server name is not displayed under the domain tree.

Figure 10-1 Check Box to Select the Server Name

Description of "Figure 10-1 Check Box to Select the Server Name"

To resolve this issue, ensure that the IPv6 address of the Admin Host is added in the hosts file of the Operating System, as follows:

2606:b400:2010:484b:f13b:4672:38b7:5af9  slc04wro.example.com  slc04wrolocalhost

On Windows, the hosts file is typically located at C:\Windows\System32\drivers\etc\. On Unix and Solaris, the hosts file is located at /etc/hosts.

If you install and deploy MSS on a single server using IPv6 address with SSL enabled, the My Desktop page is not displayed in the MSS application.

To resolve this issue, you must enable HTTP tunneling in the WebLogic Server Administration Console. See "Enabling HTTP Tunneling" for more information.

When starting the proxy server, you may receive the following number format exception:

java.lang.NumberFormatException: For input string: "b400:2010:484b:f13b:4672:38b7:5af9"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at weblogic.servlet.proxy.HttpClusterServlet$Server.parsePorts
(HttpClusterServlet.java:2042)
at weblogic.servlet.proxy.HttpClusterServlet$Server.<init>
(HttpClusterServlet.java:1898)
at weblogic.servlet.proxy.HttpClusterServlet$ServerList.<init>
(HttpClusterServlet.java:2078)
at weblogic.servlet.proxy.HttpClusterServlet.init
(HttpClusterServlet.java:141)

To resolve this issue, ensure that you specify the IPv6 addresses within [] (brackets) in the WebLogicCluster init parameter of the HttpClusterServlet in the web.xml of the proxy server.

For example:

<init-param>
  <param-name>WebLogicCluster</param-name>
  <param-value> [IPv6_address1]:port1|[IPv6_adrress2]:port2</param-value>
</init-param>

When logging in to the MSS application, you may receive the following error:

Unable to communicate with application server selected.

To resolve this issue, do the following:

• If you are connecting to an IPv6 proxy server for accessing MSS client application, ensure that you specify the proxy server's IPv6 address in the client machine's etc/hosts file, as follows:

  IPv6address                 ipv6machine@example.com    ipv6machine
  

• Install the self-signed certificate on the client machine. See "Installing the Self-Signed Certificate on the Client Machine" for more information.

Your updates are not reflected in the web.xml file of the proxy server.

To resolve this issue, do the following before starting the proxy server for the first time:

• Make your changes in the web.xml file

• Specify the IPv6 addresses within [] (brackets) in the WebLogicCluster init parameter of the HttpClusterServlet in the web.xml file

• Add the SecureProxy init parameter to the HttpClusterServlet in the web.xml file for a cluster that has SSL enabled

If you have already started the proxy server and still unable to see your changes in the web.xml file, redeploy the Oracle Cluster Proxy web application using the WebLogic Server Administration Console.

If you create a domain using SSL on an AIX platform, you must make additional updates to the orb.properties file. Ensure the following property values are set:

1. Open the file MSLV_Home\mslv01\jacORB\orb.properties

   where:

   • MSLV_Home is the directory in which the MSS software is installed

   • mslv01 is the server home directory

2. Provide the appropriate values for the following properties:

   jacorb.security.jsse.server.key_manager_algorithm=IbmX509 
   jacorb.security.jsse.server.trust_manager_algorithm=IbmX509 
   jacorb.security.jsse.client.key_manager_algorithm=IbmX509 
   jacorb.security.jsse.client.trust_manager_algorithm=IbmX509
   

When the admin server and the managed server are on different machines, a warning can occur during a cluster installation. You can encounter the following warning when trying to start the managed server:

####<Warning> <DeploymentService> <BEA-290074> <Deployment service servlet received file download request for file>

To resolve this issue, you add the following java option:

-Dweblogic.data.canTransferAnyFile=true

to the startWeblogic.sh file on the managed server.

A DLL error can occur if an incorrect version of the Oracle Database Client was installed and you run any of the following applications:

• Location and Routing Gateway

• NPA Split Utility

• Data Selection

• Pre-Migration Analysis Tool

• MetaSolv Solution Utilities

The DLL error is the following:

Cannot make a connection to the database.
Oracle library OCI.DLL or ORAC803.DLL could not be loaded.

This error can occur if the 64-bit version of the Oracle Database Client was installed instead of the 32-bit version. See MSS Planning Guide for more information on software version requirements.

When running MSS in an SSL environment, it is possible to experience a response delay when moving outside the application and then returning back to MSS. If you leave the MSS application for a few minutes (with no activity), and then later attempt to move to a new MSS window, then there can be a delay of few seconds before it responds. Also, the window header title can include “Not Responding" for few seconds.

This issue occurs due to the idle connection time-out set in the Oracle WebLogic console. To resolve this issue, log in to the WebLogic console, and under Server->Protocol->General, set the option for the idle connection time-out to a higher number. The default is 60 seconds, and after 60 seconds of no activity, it drops the connection to the client. Increase the idle connection time-out value to the appropriate value for your requirements.

During the integration between MSS and Network Integrity, when a connection is made to the MSS application from Network Integrity through the CORBA server, Network Integrity returns the following error message:

Can't establish Corba connection with MSS
IDL:omg.org/CosNaming/NamingContext/NotFound1.0.

To resolve this issue, do the following:

1. Navigate to the MSLV_Home/appserver/gateway directory and edit the gateway.ini file.

2. Uncomment the INFRASTRUCTURESERVER entry in the [Servers] section.