Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content

JMX Port Conflict


James Jennings

Recommended Posts

Hi all,

 

Running BusinessEvents 5.4.1 we are attempting to scale out our cache instances from 6 to 12 in order to alleviate thread congestion and poor throughput. We only have 6 physical machines on which to deploy the 12 instances. With two instances on each host we see a port already in use error at startup and that instance shuts down.

 

JMX port is defined for the Processing Unit. Is there a way to run two instances of the same PU in one host

 

Thanks for any insights.

Link to comment
Share on other sites

  • 3 weeks later...

Hi James,

To avoid the JMX port conflict when running multiple processing units on the same machine, you may use a global variable. In your TRA file (default is under $BE_HOME/5.4/bin/be-engine.tra), set..

java.property.be.engine.jmx.connector.port=%JmxPort%

..where 'JmxPort' is a global variable defined for this project.

Then in your CDD, set in the Properties for the processing unit..

tibco.clientVar.JmxPort=9001

..which would set the JmxPort value to 9001, which would in-turn set the java.property.be.engine.jmx.connector.port value in the TRA. You can do this for each Processing Unit in your CDD.

 

Regards,

Jim Mulcahey

TIBCO Support

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...