Miscellaneous Troubleshooting

This topic describes troubleshooting issues that are either common to several areas or belong to an area separate from server configuration, Web Navigator, or ENOVIA Studio Modeling Platform Rich Clients.

Related Topics
Implementation Troubleshooting
Web Navigator Troubleshooting
ENOVIA Studio Modeling Platform Troubleshooting

FTP Connection Timeouts

All supported operating systems provide a TCP KeepAlive socket feature which ENOVIA Live Collaboration uses for all FTP connections. When ENOVIA Live Collaboration creates a socket for use in a FTP transfer (that is, for checkin/checkout operations with FTP stores or with FCS), the socket utilizes the TCP SO_KEEPALIVE option. If ENOVIA Live Collaboration is unable to set the SO_KEEPALIVE option on the socket(s), it will print a warning.

With the proper OS TCP stack configuration, large file transfer attempts through firewalls and other intermediary network devices, including proxies, no longer fail due to the FTP control connection time outs and termination.

Below are guidelines for enabling and configuring TCP KeepAlives on the various platforms.

Platform Relevant parameters Command to check Command to change
AIX
tcp_keepidle
tcp_keepintvl
no -o tcp_keepidle
no -o tcp_keepintvl
no -po  tcp_keepidle=14400 
no -po tcp_keepintvl=240
LINUX
tcp_keepalive_time
tcp_keepalive_intvl
tcp_keepalive_probes
cat /proc/sys/net/ipv4/tcp_keepalive_time
cat /proc/sys/net/ipv4/tcp_keepalive_intvl
cat /proc/sys/net/ipv4/tcp_keepalive_probes
In /etc/sysctl.conf
net.ipv4.tcp_keepalive_time = 7200 
net.ipv4.tcp_keepalive_intvl = 75
net.ipv4.tcp_keepalive_probes = 9 #sysctl -p
Solaris
tcp_keepalive_interval
ndd /dev/tcp 
tcp_keepalive_interval
ndd -set /dev/tcp 
tcp_keepalive_interval 290000
Windows
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
KeepAliveInterval
KeepAliveTime
regedit
Regedit or .reg file

Changing the keepalive interval is a server wide and not per connection/process setting. Before making changes to the TCP stack in a production system these changes must be qualified in a comparable test environment.

If you find you have long data transfers (replication) between stores on separate sides of a firewall that is configured to time out TCP connections that remain idle for a given interval, then you will want to configure your operating system's TCP stack to send KeepAlives at an interval smaller than the interval at which the firewall times out idle TCP connections. You should contact your IT infrastructure staff to determine what is the maximum time the infrastructure hardware will allow a connection to remain active. An industry standard is 300 seconds (5 minutes). You would be safe to set the keepalive interval to 290 seconds. If the hardware is not dedicated to ENOVIA Live Collaboration, then you must determine the impact of lowering the keepalive interval for any other application on the server.

Laptop Performance

Problem

From a laptop computer, opening ENOVIA Web pages, setting context and performing finds seem to take longer than should be necessary.

Solution

Check the following:

  1. Set your browser default page to a local file instead of the browser's default homepage of www.microsoft.com or http://www.mozilla.org. Browser initialization and host name resolution as well as anything using TCP/IP will all perform faster.
  2. Check that the hostname for the DNS settings is set to the machine's network name.
  3. Open the Network option from the Control Panel.
  4. Click the Protocols tab and choose TCP/IP protocol properties.
  5. Click the DNS tab and make sure the host field specifies the correct machine network name.

Open the \winnt\system32\drivers\etc\hosts file. Make sure your machine IP and name are listed. This helps resolve the host name more quickly.

Session Timed Out Error

Problem

The following error is received when performing any operation: java.lang.Exception: Session timed out

Solution

Timeout limits are set and enforced in the Web or application server. If a period of inactivity occurs that is greater than the limit set, for security reasons, users are forced to login again. Consult your Web server's documentation for information on setting this limit.

Tar Error When Unpacking Distributions

If you receive LongLink error(s) when attempting to untar an ENOVIA distribution file such as ENOVIALiveCollaborationServer-VERSION.tar, install GNU tar 1.14 or higher and unpack with gtar. The original POSIX format can only handle 100 characters for link names.

Problems with JSP Path for ENOVIA products

If you have problems with the path for the JSPs when using an ENOVIA product, make sure the following settings are defined as follows in the web.xml file.

ematrix.login.page=/ematrix/emxLogin.jsp
ematrix.home.page=/ematrix/emxHome.jsp