launchclient c:\was\base51\installedApps\Cell\WPFKeyBasedPartitionSample.ear -CCproviderURL=corbaloc::localhost:9813 IBM WebSphere Application Server, 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 wa s 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
일반적으로 모든 파티션이 활성화된 상태가 되려면 몇 분이 걸릴 수 있습니다. 개발 시나리오에서 공통된 시나리오의 경우(예: 적당히 적은 수) 서버가 "Open for e-business"를 보고하면 즉시 파티션이 활성화되고 작업을 준비합니다.
그러나 파티션 수가 더 커지거나 전체 클러스터에 클러스터 구성원 수가 많아지거나 프로덕션 관련 작업이 시작되면 많아진 파티션 수 때문에 완전히 활성화하는 데 몇 분이 걸릴 수도 있음을 참고하는 것이 중요합니다. 가능한 파티션 수 때문에 키 시나리오에 대한 하나의 파티션 추적 행을 인쇄하는 작업도 성능에 큰 영향을 줄 수 있으므로 기본적으로 WPF 파티션 상태를 설명하는 특정 메시지는 인쇄하지 않습니다.
wpfadmin setTraceSpec perm WPFSTATUS=all=enabled -c cluster다음은 예상하는 출력 예입니다.
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)클러스터 구성원에서 추적을 사용 가능하게 하면 각 파티션의 로그 디렉토리에 추적 항목이 표시됩니다(다른 정보와 함께 이 텍스트가 필터됨). 아래의 추적 스냅샷이 한 예입니다.
[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.이 경우 서버의 자체 로그 항목과 비교할 때 마지막 파티션은 11:53:56에 시작되었습니다.
10/14/04 11:53:47:649 CDT] 719092f5 WsServer A WSVR0001I: Server cluster_member_2 open for e-business따라서 이 경우 대략 Application Server가 시작된 11:53:47부터 마지막 파티션이 활성화되어 요청을 수신하도록 클러스터에 등록된 11:53:56까지 시간이 걸립니다. 10개의 파티션에 대해 약 9초입니다. 시작 정책이 상당한 영향을 줄 수 있으며 시작 순서가 서버 시작 순서 및 타이밍에 따라 다양할 수 있으므로 일반 규칙에 속하지는 않지만 일반적으로 클라이언트의 관점에서 파티션에 액세스할 수 있을 때까지 클라이언트 요청은 거부됩니다.
Related reference
문제점 해결