Webmethods 8 cluster

, ,
21

IS Core Fix1 has been replaced by IS Core Fix2 for 8.2 SP2 (8.2.2).

But that was not the issue. Our IS are standing on VMware machines and there is a 5* on system requirements for this version of webMethods that says:

So forget coherence on VMs… for this wM version.

22

[URL]http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite8-2_sp2/SysReqs_Installation_and_Upgrade/8-2_System_Requirements.pdf[/URL]

Allways read the system requirements :crazy:

23

YES very true:

So you installed Core Fix2 as well? Any issues noticed?

24

Hi,

Just to update the information…

I too faced similar issue today in enabling clustering and issue is resolved as follows…

-------------------------------------- ERROR---------------------
2012-10-27 09:38:58 CEST [WmSharedCacheSC.impl.0200E] Failed to create/get distributed cache ‘ProcessEngine Step Lock Store’; reason: java.lang.RuntimeException: Failed to start Service “Cluster” (ServiceState=SERVICE_STOPPED, STATE_JOINING); – check configuration
2012-10-27 09:38:58 CEST [PRT.0101.0002E] ERROR: com.webMethods.sc.caching.CachingException
2012-10-27 09:38:58 CEST [PRT.0101.0003E] Failed to create/get distributed cache ‘ProcessEngine Step Lock Store’; reason: java.lang.RuntimeException: Failed to start Service “Cluster” (ServiceState=SERVICE_STOPPED, STATE_JOINING); – check configuration

  1. disabled clustering in both the integration servers ( clustering servers) and restarted the server…
  2. After the server restart again configured clustering in both the Integration servers.
  3. Again restarted both the integration servers…

Issue is resolved and clustering is enabled…

25

Did you updated/restarted one by one or together same time?

26

Hi

Clustering disabled first in IS01 and shutdown the server, then disabled in IS02 and shutdown the server.

After restarting both the servers, again configure the clustering in IS01 & IS02 and restarted one after another

27

Hi,
We are using IS version 7.1.3 which went to production very recently. IS are also facing same issue of clustering as mentioned in the chain.
Our IS is with Core Fix 24.

We have involved SAG support to help us fix this issue however the issue is still open.
Whenever the clustering error occur, server becomes unresponsive and finally we have to restart IS.

Sometime during restart also we faced same issue of tangosol. read timeout exception.

If there is any fix to this issue. please suggest… :frowning: :frowning:

Regards,
A

28

I would suggest better go with latest core fix (test thoroughly in a lower level environment first)

Also do you these fixes in place before applying SP3?

WSI_7.1.2_Cluster_Fix1

Did you check these files with the localhost/server ip information that is blocking or if anything related to your internal compliance which they haven’t report to you recently/past?

tangosol-coherence-override.xml
tangosol-coherence.xml

HTH,
RMG

29

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.