1. Home
  2. Support
Article - CS119775

Replication and configuration issues with cluster setup when slaves use distinct URL's in Windchill

Modified: 17-Nov-2015   


Applies To

  • Windchill PDMLink 9.1 to 10.1

Description

  • Replication and configuration issues with cluster setup when slaves use distinct URL's
  • Each slave having distinct URL, for example to serve external and internal users
  • Dual protocol URL setup (HTTP/HTTPS)
  • Replication issue: File Server pings the external URL, below a possible excerpt of such stack trace error:
"wt.fv.replica  - currKey = https://HOSTNAME/Windchill/servlet/WindchillGW
 ERROR [ajp-bio-8010-exec-2] wt.fv.replica  - Vault XXX from site https://<External_URL>/Windchill/servlet/WindchillGW not found in findFolderToSaveFile
 ERROR [ajp-bio-8010-exec-2] wt.fv.replica  - Configuration Update Needed from https://<External_URL>/Windchill/servlet/WindchillGW
 ERROR [ajp-bio-8010-exec-2] wt.fv.replica  - This can be accomplished by stopping and starting the replica method server.
 ERROR [ajp-bio-8010-exec-2] wt.fv.replica  - ERROR while storing content
wt.fv.FvFileCanNotBeStored
at wt.fv.replica.StandardReplicaService.findFolderToSaveFile(StandardReplicaService.java:1621)
at wt.fv.replica.StandardReplicaService.storeStreamOnReplicaInternal(StandardReplicaService.java:1660)
at wt.fv.replica.StandardReplicaService.remotePullAndStoreStream(StandardReplicaService.java:2053)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)"
 
 
  • Configuration issue:  at startup master URL switches to external slave URL  in File Server Administration > Site Administration
This is a printer-friendly version of Article 119775 and may be out of date. For the latest version click CS119775