Client invocation problems

Program guide > (deprecated) Partitioning facility > Problem resolutions

Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.

Client invocation problems

Launchclient
Error:
launchclient c:\was\base51\installedApps\Cell\WPFKeyBasedPartitionSample.ear 
-CCproviderURL=corbaloc::localhost:9813

IBM WAS, Release 5.1
J2EE Application Client Tool
Copyright IBM Corp., 1997-2003
WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0035I: Initialization of the J2EE Application Client Environment 
has completed.
WSCL0014I: Invoking the Application Client class com.ibm.websphere.wpf.client.
WPFKeyBasedPartitionClient
WSCL0100E: Exception received: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
        (NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke
        (NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.ibm.websphere.client.applicationclient.launchClient.
createContainerAndLaunchApp(launchClient.java:638)
        at com.ibm.websphere.client.applicationclient.launchClient.
main(launchClient.java:425)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
        (NativeMethodAccessorImpl.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke
        (NativeMethodAccessorImpl.java:58)
        at sun.reflect.DelegatingMethodAccessorImpl.
invoke(DelegatingMethodAccessorImpl.java:60)
        at java.lang.reflect.Method.invoke(Method.java:391)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
Caused by: com.ibm.websphere.naming.CannotInstantiateObjectException: 
Exception occurred while the JNDI NamingManager was
processing a javax.naming.Reference object. 
[Root exception is javax.naming.CommunicationException: A communication 
failure occurred while attempting to obtain an initial context with the 
provider URL: "corbaloc::localhost:9813".  Make sure that any bootstrap address
information in the URL is correct and that the target name server is running.  
A bootstrap address with no port specification defaults to port 2809.  
Possible causes other than an incorrect bootstrap address or unavailable name server 
include the network environment and workstation network configuration. 
[Root exception is org.omg.CORBA.COMM_FAILURE: WRITE_ERROR_SEND_1  
vmcid: 0x49421000  minor code: 50  completed: No]]
        at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt
       (Helpers.java:931)
        at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup
(UrlContextHelper.java:152)
        at com.ibm.ws.naming.java.javaURLContextRoot.processBoundObjectForLookup
(javaURLContextRoot.java:398)
        at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup
        (UrlContextImpl.java:1278)
        at com.ibm.ws.naming.java.javaURLContextRoot.
        lookup(javaURLContextRoot.java:196)
        at com.ibm.ws.naming.java.javaURLContextRoot.
        lookup(javaURLContextRoot.java:137)
        at javax.naming.InitialContext.lookup(InitialContext.java:361)
        at com.ibm.websphere.wpf.client.WPFKeyBasedPartitionClient.main
(WPFKeyBasedPartitionClient.java:110)
        ... 13 more
Possible Causes

Cluster has not been made operational.

Incorrect port used when dispatching the request.

Cluster is starting, or started, but the partitions have not been activated to receive requests.

Explanation

In general it can take a few minutes for all partitions to enter the activated state. For the scenarios common in development scenarios, e.g. reasonably few in number, partitions will often be active and ready for work as soon as the server reports "Open for e-business".
However, as the partition numbers are larger, more cluster members are in the overall cluster, or production related work begins, it is important to note that large numbers of partitions may take several minutes to fully activate. Due to the possible number of partitions, even printing out trace lines for one partition for key scenarios could drastically affect performance; the default case is to not print out any specific messages that describe the status of a WPF partition.
Users can enable a trace spec, WPFSTATUS, though, without affecting performance. This will print out a message for each partition upon activation and other important life cycle events. For those preparing for production, this can be turned on and the general time to document the startup time expected for the particular implementation of the partitioning facility. It is suggested that for production scenarios this trace not be used, but rather for pre-production documentation generation or problems in production when it is not clear a partition is activated and it should be. Assuming you have a cluster named "cluster," the trace specification can be set for all nodes with the following command:
wpfadmin setTraceSpec perm WPFSTATUS=all=enabled -c cluster
The following is the example output to expect.
wsadmin -lang jython -f wpfadmin.pty setTraceSpec perm WPFSTATUS=all=enabled 
--c cluster
WASX7209I: Connected to process "Deployment Manager" on node CellManager 
using SOAP connector;  
The type of process is: DeploymentManager
WPFC0065I: Cluster set to cluster
WPFC0059I: Setting trace to WPFSTATUS=all=enabled 
for Server cluster_member_1
(cells/Cell/nodes/NodeA/servers/cluster_member_1:server.xml#Server_1)
WPFC0059I: Setting trace to WPFSTATUS=all=enabled for Server cluster_member_2
(cells/Cell/nodes/NodeA/servers/cluster_member_2:server.xml#Server_1)
WPFC0059I: Setting trace to WPFSTATUS=all=enabled for Server cluster_member_3
(cells/Cell/nodes/NodeA/servers/cluster_member_3:server.xml#Server_1)
After the trace is enabled on the cluster members, trace entries will appear in the log directory for each partition (with other information; this text was filtered). The trace snapshot below is an example:
[10/14/04 11:53:53:287 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000002 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:53:647 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000001 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:54:639 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000004 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:55:600 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000008 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:56:041 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000003 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:56:091 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000005 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:56:241 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000010 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:56:411 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000006 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:56:692 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000007 is successfully created and open for e-Business at 
this server.
[10/14/04 11:53:56:732 CDT] 1f3052f7 XDClusterAdap I WPFR0002I: Partition routing 
cluster for partition PK000009 is successfully created and open for e-Business at 
this server.
In this case, the last partition started at 11:53:56, as compared to the server's own log entry:
10/14/04 11:53:47:649 CDT] 719092f5 WsServer      A WSVR0001I: 
Server cluster_member_2 open for e-business
Consequently, in this case, it took approximately from 11:53:47 when the application server started until 11:53:56 when the last partition was activated and enrolled in the cluster to receive requests. This is about 9 seconds for 10 partitions. This is not a general rule as startup policies can affect this a great deal, and the startup sequence can vary depending on server start order and timing, but the general point is that client requests will be rejected until partitions are accessible from the client viewpoint.

Parent topic:
Problem resolutions

Related reference

Problem resolutions

+
Search Tips | Advanced Search