Forums » Interstage BPM Knowledgebase Articles

• admin admin

  
   

  October 6, 2011 10:14:06 AM PDT

  Interstage BPM Version: Any version of JBoss that supports clustering.
  
  
  Problem Description:
  JBoss Application Server comes with clustering support out of the box and it will automatically detect other instances of JBoss on the same network to form a cluster.  This is a good feature for load distribution across different servers and as a fail-over system but other times; a user may not want to enable this feature.  In this case, clustering may cause additional issues when an application is not setup for this configuration.  It is known that Interstage BPM will throw an error a “vServerProperties” error from the command prompt when launching the JBoss server or this error appears when trying to login to the console as an admin user on the console itself.  The other symptom is that a user is unable to log into the TenantManager.page with the correct credentials. 
  These issues occur when these criteria are met:
  1. Interstage BPM is not configured to support clustering.
  2. There is more than one instance of JBoss running on the same network.
  Another indicator of when JBoss is trying to form is cluster can be found from the server.log file from the JBoss <JBoss Installation>/server/ibpm/log/server.log.  If JBoss is trying to form a cluster, it would output the number of members similar to this:
  
  ====================================
  2011-10-06 10:13:08,796 INFO  [org.jboss.ha.framework.interfaces.HAPartition.ibpm_partition1] (JBoss System Threads(1)-3) Number of cluster members: 2
  ====================================
  
  In this example, the statement indicates that “2” cluster members are being formed in the cluster.  JBoss is trying to form a cluster when there is more than 1 cluster member.
  
  Solution:
  Majority of the time, these issues can be rectified by removing the other instance(s) of JBoss by shutting it down or by killing the additional server instances.  In other cases, it is needed to set/change the IBPM_CLUSTER_PARTITION_NAME and IBPM_MULTICAST_IP in order to rectify the conflict.  These properties can be found from the “runIBPM.bat” and this batch file can be found from <JBoss Installation>/bin.  Since these properties are set to variables, the change actually needs to be done in the “setEnv.cmd” file” from <JBoss Installation>/bin.  In the “setEnv.cmd” file, set the values for IBPM_CLUSTER_PARTITION_NAME and IBPM_MULTICAST_PI to be unique.   After the change, a restart of the JBoss server is required for the changes to go into effect.
  
  
  Attached is a word document copy of this article.
  
  

   

  Author: Marc Bui
  Attachment: How_to_ResolveJBoss_vServerProperties_Error.zip