Unexpected failure detected: NestedException shows in GMS logs.
This document (7002694) is provided subject to the disclaimer at the end of this document.
Novell GroupWise 7
GroupWise Mobile Server Windows edition
Micosoft SQL Server
Unexpected failure detected: PIMDBException
com.sync.db.PIMDBException: java.sql.SQLException: Network error IOException: Address already in use: connect
In paralel to a time you see those errors in above log, there are similar errors visible in other logs, for instance in a GroupWise_Translator_<date> (if enabled):
GWEvents exception occured: HTTP transport error: java.net.SocketException: No buffer space available (maximum connections reached?): connect; nested exception is:
HTTP transport error: java.net.SocketException: No buffer space available (maximum connections reached?): connect
The "java.sql.SQLException: Network error IOException" tells about application connection problems that originate from a TCP layer.
Default TCP protocol stack configured on Windows servers is not very suitable for environments that might have connection problems or face higher traffic load. If a Windows server faces any connection problem to another host, it keeps a connection locked for longer time period. Consequently if next opened connection hits the same problem, it will be locked and the target host can easily run out of available TCP connections. Once the host reaches out the max available connections, you can start seeing problems reported by any application like in case of GMS server complains over unable to connect to MS SQL databases.
There are several resources in the Internet that deals with a tuning TCP stack on Windows server. You can have a look at following TID 3724926 Slow performance of GMS on Windows.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7002694
- Creation Date:19-FEB-09
- Modified Date:10-DEC-13
- NovellGroupWiseEnd of Life
Did this document solve your problem? Provide Feedback