Post Cloning Of WCS12C, All POST Calls Are Getting 504 Gateway Timeout Error (Doc ID 3006754.1)

Last updated on MARCH 14, 2024

Applies to:

Goal

1. After cloning the environment timeout 504 error appears whenever is being performed any POST methods (ex: saving an asset or removing assigned sites to an app);

2. After one deleted everything and redone from the start the cloning process, the issue was fixed after redoing the cloning process;

3. A timeout error appeared whenever ones tried to delete a publishing destination;

4. Timeout value from WLS console was increased to 30 mins;

5. After this change, some of the publishing destinations could be deleted in almost 25 mins;

6. It is needed a faster way for deleting the publishing destinations data like manually from tables:

- ApprovalQueue: cs_target
- ApprovedAssetDeps: targetid
- ApprovedAssets: targetid
- AssetExportData: targetid
- FW_PUBDATASTORE: pubsession-> id from pubsession table
- FW_PubTarget_ApprovalRoles: cs_ownerid
- FW_PubTarget_PublishRoles: cs_ownerid
- PubContext: cs_target
- PubMessage: cs_sessionid-->id from pubsession table
- PubKeyTable: targetid
- PubSession: id -> pubcontext.cs_sessionid
- PubTarget: id
- PubTarget_Sites: ownerid
- PublishedAssetRevisions: targetid
- PublishedTags: targetid


 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.