Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Clustering fails with WPS patched to 6.0.0.1 and WAS patched to 6.0.2.17

5 views
Skip to first unread message

leon.d...@nissan.co.uk

unread,
Jan 3, 2007, 4:24:01 AM1/3/07
to
Steps followed for installation:
1. Install WAS and WPS from WPS install binary
2. Path both of them to specified level
3. Migrate DB from cloudscape to oracle
4. Create Deployment manager profile in the same machine
5. Enable same security for Deployment manager
6. pre-federation script
7. addNode
8. post federation script
9. Check the operability of WPS in Dmgr
Everything seems to run as expected till here
10. Tried to create cluster by running cluster-setup [Got this error]
I tried this couple of times and it landed up in the same place.

Got the following error when running
/WPSconfig.sh cluster-setup

action-cluster-setup-wcm-caches:
Tue Jan 02 16:13:04 CST 2007
[logmsg] 2007.01.02 16:13:04.205 action-cluster-setup-wcm-caches
[logmsg] EJPCA3100I: Configuration task "action-cluster-setup-wcm-
caches" in progress
[wsadmin] WASX7209I: Connected to process "dmgr" on node
ezdwas01CellManager01 using SOAP connector; The type of process is:
DeploymentManager
[wsadmin] WASX7303I: The following options are passed to the
scripting environment and are available as argument that is stored in
the argv variable: "[/usr/WebSphere/PortalServer]"
[wsadmin] ---- ClusterName(s) ---------------------------------
[wsadmin] ' WPSCluster'
[wsadmin] ---- ClusterMember(s) ---------------------------
[wsadmin] 'WebSphere_Portal'
[wsadmin] -------------------------------------------------
[wsadmin] -----------------------------------------------------
[wsadmin] 2007.01.02 16:13:24.956 wcm_ClusterCacheSetup.jacl
[wsadmin] EJPCA3004E: ERROR: "/Cell:ezdwas01Cell02/Node:
ezdwas01Node01/Server:WebSphere_Portal/CacheProvider:
CacheProvider/CacheInstance:strategy/" not there
BUILD FAILED
file:../config/includes/wcm_cfg.xml:1400: Java returned: 1

Can anyone help me out?

Cheers,
Leon

byb...@sbcglobal.net

unread,
Jan 5, 2007, 2:15:21 AM1/5/07
to
I am getting the same error, I've tried serval times now. Perhaps its a bug intrduced in cf17? I'm going to open a PMR up tomorrow I guess.

leon.d...@nissan.co.uk

unread,
Jan 5, 2007, 6:30:27 AM1/5/07
to
This problem is fixed. I think there is something to do with 17 WAS version.

All I did is, if it failes in "action-create-scheduler-cleanup-daemon" then i do

WPSconfig.sh action-remove-scheduler-cleanup-daemon
WPSconfig.sh action-create-scheduler-cleanup-daemon

manually and then run cluster-setup.

That solves the problem. You can use the same logic if you get struck anywhere in cluster-setup script.

Cheers,
Leon

shah_m...@yahoo.com

unread,
Jan 5, 2007, 7:01:45 AM1/5/07
to
Hi LeonDJ,

I am also going to work on clustering for WPS 6.0 on windows in near future. I have gone through some of the docs available on the net. But still to find any proper documentation on it.

Can you just help me out in this. It would be fine if you can just point out some resources where I can get these details.

Waiting for your response. Thanks in advance.

Regards,
Dev

ka...@us.ibm.com

unread,
Jan 11, 2007, 7:26:27 AM1/11/07
to
I am facing the same problem (WPS patched to 6.0.0.2 and WAS patched to 6.0.2.17), I tried the following but get error:
WPSconfig.sh action-remove-scheduler-cleanup-daemon
WPSconfig.sh action-create-scheduler-cleanup-daemon

action-create-scheduler-cleanup-daemon:
Thu Jan 11 07:05:32 GMT-05:00 2007
[logmsg] 2007.01.11 07:05:32.852 action-create-scheduler-cleanup-daemon

[logmsg] EJPCA3100I: Configuration task "Create WPSTaskScheduler" in progre
ss

[wsadmin] WASX7209I: Connected to process "dmgr" on node ibc4hb09Dmgr using SO


AP connector; The type of process is: DeploymentManager
[wsadmin] WASX7303I: The following options are passed to the scripting environ

ment and are available as argument that is stored in the argv variable: "[/opt/W
ebSphere/PortalServer]"
[wsadmin] NodeName: 'ibc4hb10Node01'
[wsadmin] ServerName: 'WebSphere_Portal'
[wsadmin] DataSourceName: 'releaseDS'
[wsadmin] TablePrefix: 'release.WPS_SCD'
[wsadmin] ScdName 'WPSTaskScheduler'
[wsadmin] WmName: 'SchedulerWorkManager'
[wsadmin] 2007.01.11 07:05:49.889 SchedulerCreate.jacl
[wsadmin] EJPCA3004E: ERROR: "/Node:ibc4hb10Node01/WorkManagerProvider:WorkM
anagerProvider/WorkManagerInfo:SchedulerWorkManager/" not there

[wsadmin] 2007.01.11 07:05:49.937 SchedulerCreate.jacl
[wsadmin] EJPCA3006E: ERROR: "/Node:ibc4hb10Node01/Server:WebSphere_Portal/S
chedulerProvider:SchedulerProvider/SchedulerConfiguration:WPSTaskScheduler/" cou
ld not be created/modified


BUILD FAILED
file:../config/actions/was_cfg.xml:2157: Java returned: 1

Total time: 28 seconds

leon.d...@nissan.co.uk

unread,
Jan 11, 2007, 7:41:54 AM1/11/07
to
WPS 6.0.0.2???

leon.d...@nissan.co.uk

unread,
Jan 11, 2007, 7:41:12 AM1/11/07
to
Dev,

WPS 6.0 Infocenter will give you step by step procedure on installing Cluster. Please follow that.

Cheers,
Leon

namdev...@yahoo.com

unread,
Jan 12, 2007, 2:03:28 AM1/12/07
to
I ran both WPSconfig.sh action-remove-scheduler-cleanup-daemon and
WPSconfig.sh action-create-scheduler-cleanup-daemon but the latter failed. I have WP 6.0.0.0 and WAS/ND 6.0.2.15 running on a RHEL 4 systems. Will installing the cumulative fix to WP resolve the issue? I too get the same error code as you do.

Thanks,
NGS

ka...@us.ibm.com

unread,
Jan 12, 2007, 2:59:46 PM1/12/07
to
I tried it on Process Server 6.0.1.2 and applied WAS base FixPack 17.

Also tried on Process Server 6.0.2 (This has the WAS base FixPack 17).

In both cases, I get the

action-cluster-setup-wcm-caches:
Fri Jan 12 13:43:34 GMT-05:00 2007
[logmsg] 2007.01.12 13:43:34.299 action-cluster-setup-wcm-caches

[logmsg] EJPCA3100I: Configuration task "action-cluster-setup-wcm-caches" in progress

[wsadmin] WASX7209I: Connected to process "dmgr" on node ibc3hb05Dmgr using SOAP connector; The type of process is: DeploymentManager
[wsadmin] WASX7303I: The following options are passed to the scripting environment and are available as argument that is stored in the argv variable: "[/opt/WebSphere/PortalServer]"
[wsadmin] ---- ClusterName(s) ---------------------------------
[wsadmin] ' CSDPPortalCluster'


[wsadmin] ---- ClusterMember(s) ---------------------------
[wsadmin] 'WebSphere_Portal'
[wsadmin] -------------------------------------------------

[wsadmin] ' CSDPProcessCluster'
[wsadmin] ---- ClusterMember(s) ---------------------------
[wsadmin] 'ibc3hb05Node01_ProcServer01'
[wsadmin] -------------------------------------------------
[wsadmin] -----------------------------------------------------

[wsadmin] 2007.01.12 13:43:51.661 wcm_ClusterCacheSetup.jacl
[wsadmin] EJPCA3004E: ERROR: "/Cell:ibc3hb05Cell/Node:ibc3hb07Node01/Server:WebSphere_Portal/CacheProvider:CacheProvider/CacheInstance:strategy/" not there

I have opened a PMR

steve....@baesystems.com

unread,
Jan 19, 2007, 6:38:31 AM1/19/07
to
I get the same error.

I can't see any fixes on the IBM website for this problem so I can only assume its a configuration issue of some sort.

Did anyone have any progress on resolving this ?

namdev...@yahoo.com

unread,
Jan 26, 2007, 4:49:28 PM1/26/07
to
I rolled back to 6.0.2.9 and ran WPSconfig.sh action-create-wcm-dynacache-names followed by WPSconfig.sh action-cluster-setup-wcm-caches and that seemed to do the trick. I'm not sure if CFP 17 for WAS 6 supports WP 6.

NGS

ka...@us.ibm.com

unread,
Jan 28, 2007, 11:32:12 AM1/28/07
to
Here is the technote that mentions this problem, currently the only workaround seems to be to fallback to lower WAS base Fixpack.
http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg21254233

I switched to WAS base Fixpack 15 and the problem is not there.

0 new messages