IBM FileNet P8 does not support TCP/IP Offloading Engine (TOE)

Content

IBM FileNet P8 does not support TCP/IP Offloading Engine (TOE)

Issue: An error "Software caused connection abort: recv failed" occurs intermittently when you attempt to check in, check out, view, or search for a document.

Cause: IBM FileNet P8 does not support the TOE network card hardware enhancement on any FileNet P8 core component, such as: Content Engine, Process Engine, Application Engine, the FileNet P8 LDAP directory server, or database server that is used by FileNet P8. This technology can be enabled by using software and hardware settings, as described in the documentation for the network cards and operating systems involved.

Solution: Disable TOE on all servers that are running FileNet P8 core components or the LDAP directory server. For instructions on disabling TOE technology refer to the operating system vendor documentation and the network card documentation.

TCP Chimney Offload settings, nomenclature, and defaults vary for each network adapter. Check the documentation for your adapter for TCP Offload capabilities and settings.

For more information about how to diagnose the issue, see the IBM technote titled ‘Connection abort: recv failed intermittently when attempting to check in, checkout, view, or performing a search on documents’ at: http://www-01.ibm.com/support/docview.wss?uid=swg21578088

Beginning with Windows 2003, Microsoft TOE technology, also called TCP Chimney Offload, was added to Microsoft operating systems. TOE is enabled by default on Windows Server 2003 Service Pack 2, and is disabled by default in Windows 2008. You must disable TOE on every server that is running a FileNet P8 core component as listed in the 'Cause' section, regardless of whether it was enabled intentionally.

The following articles in the Microsoft Support Knowledge Base offer information about this issue:

· For the procedure to disable TCP Chimney Offload support, refer to Article 948496 in the Microsoft Knowledge Base titled: ‘An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers’ at: http://support.microsoft.com/kb/948496/
· For other workarounds from Microsoft, see Article 924681 titled: ‘Error message when an application connects to SQL Server on a server that is running Windows Server 2003: "General Network error," "Communication link failure," or "A transport-level error"’ at: http://support.microsoft.com/kb/942861
· Windows 2008 requires additional configuration. See the Windows Server TechCenter tech note titled 'Using TCP Chimney Offload' (Applies To: Windows Server 2008 R2) for details on this isssue:
http://technet.microsoft.com/en-us/library/gg162709%28WS.10%29.aspx

In some instances, more than one of the Microsoft Knowledge Base fixes need to be implemented for the issue to be resolved.