Troubleshooting

P6 Compression Server users are receiving "Socket Error #10054…" messages:

Java offers the Socket.setSoLinger method to control how long a socket lingers, that is, the amount of time a socket waits to close when there is still unsent data. P6 Compression Server uses this setSoLinger method. The value is controlled via the P6 Compression Server Administrator Application, under the /Configurations/Custom/Primavera P6 Professional Configuration/Compression Server/SocketLingerTime setting.

Note: See Configuring the P6 Compression Server Administrator Application for more information on the Administrator Application.

By default, the SocketLingerTime value is 2s (2000ms). For noisy networks, 2s might not be sufficient, resulting in the socket closing before the data is fully read. Users will then receive the following error message:

Error: Socket Error #10054 Connection reset by peer. Received data is invalid!

To avoid this error, Oracle recommends that you adjust the SocketLingerTime setting to a higher value and restart P6 Compression Server from the services dialog. You will need to set the value according to how noisy your network is. For example, during in-house testing, increasing the SocketLingerTime setting to 10s on a network with a 5% packet loss eliminated the error messages and loss of data.

Note: Since sockets tend to be open longer with higher settings in this parameter, there could be a slight loss of performance.

For more information on the Socket.setSoLinger method, go to http://mindprod.com/jgloss/socket.html.

P6 Compression Server does not start:

You might see errors like Error occurred during initialization of VM -- Could not reserve enough space for object heap.

In this case, the administrator should edit -Xms and -Xmx parameters in the setDomainEnv.cmd file in the \<DOMAIN_HOME>\bin directory. See Configuring setDomainEnv.cmd for more information.

Note: Oracle recommends that you use a value be no greater than 1024 kilobytes for the -Xss (-Xss1024k). The default maximum stack size used by C code is sufficient for the native implementation of the compression library.

For more information, refer the following:



Legal Notices
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved.

Last Published Tuesday, February 21, 2017