APAR status
Closed as program error.
Error description
Calls to the .NET Client Connect() API will generate this error in the SystemFirstFailure log when 1) multiple catalog servers are passed to the Connect() API, and 2) the calling thread belongs to a Single Thread Apartment (STA). The following exception is contained in the SystemFirstFailure log. [08/30/13 12:56:12.970214-04:00] 00000008 Common.Logging.FirstFailureLogger T LocationServiceFactory.bootstrap unexpected error pinging LDCXSCACP6:2809, LDCXSCACP7:2809 - System.NotSupportedException: WaitAll for multiple handles on a STA thread is not supported. at System.Threading.WaitHandle.WaitMultiple(WaitHandle[] waitHandles, Int32 millisecondsTimeout, Boolean exitContext, Boolean WaitAll) at System.Threading.WaitHandle.WaitAll(WaitHandle[] waitHandles, Int32 millisecondsTimeout, Boolean exitContext) at System.Threading.WaitHandle.WaitAll(WaitHandle[] waitHandles) at IBM.Ws.Caching.Xio.DetermineTransport.retreiveProbeInfo(String[] hostPortList) in C:\build\sourceRoot2\WXSDEV\XSNET\ws\code\Client.XIO\src\Catalog \DetermineTransport.cs:line 131 at IBM.Ws.Caching.Xio.LocationServiceFactory.getTransport(String hostList, Boolean isClient, Boolean catalogServer) in C:\build\sourceRoot2\WXSDEV\XSNET\ws\code\Client.XIO\src\Catalog \LocationServiceFactory.cs:line 577 at IBM.Ws.Caching.Xio.LocationServiceFactory.bootstrap(String hostList, ClientSecurityContext clientSC, Boolean checkCache, XsTransportType transportType) in C:\build\sourceRoot2\WXSDEV\XSNET\ws\code\Client.XIO\src\Catalog \LocationServiceFactory.cs:line 139
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere eXtreme Scale Client for .NET * * users * **************************************************************** * PROBLEM DESCRIPTION: The SystemFirstFailure.log * * file contains the error: WaitAll for * * multiple handles on an STA thread is * * not supported. * **************************************************************** * RECOMMENDATION: This failure can be ignored as the * * subsequent connection to the catalog * * server fails if the client and server * * configurations are incompatible. However, * * the error information provided in this * * scenario is more generic compared to * * the error information reported during the * * connection probe. To remove this entry * * from the SystemFirstFailure.log file and * * receive more detailed error information * * about incompatible client-server connection * * configurations, apply this fix. * **************************************************************** Calls to the .NET Client Connect() API generate this error in the SystemFirstFailure log when 1) multiple catalog servers are passed to the Connect() API, and 2) the calling thread belongs to a Single Thread Apartment (STA).
Problem conclusion
The transport probe logic has been updated to support STA threads.
Temporary fix
Comments
APAR Information
APAR number
PM96586
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-06
Closed date
2013-09-10
Last modified date
2013-09-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 September 2013