Persistent JMS Messaging

Persistent JMS messaging allows the SIMULIA Execution Engine to recover running jobs from an unexpected server shutdown due to power loss, network connectivity interruption, etc.

  • Property name: fiper.station.jms.persistent

  • Command line argument: not available

Property file example:

fiper.station.jms.persistent=true

The SIMULIA Execution Engine often communicates with stations using a Java asynchronous messaging infrastructure known as JMS. By default, this infrustructure is configured to make a best effort at delivering every message to its intended recipients. The default value of true changes the station side of the infrastructure configuration such that it guarantees delivery of every message to its intended recipients. It does this by changing the message consumers to use Durable Subscriptions on the Topics to which the station is listening.

There are also corresponding configuration entries in the acs.properties file:

  • fiper.acs.jms.persistent. This property must also be left set to true to change the server side of the infrastructure configuration to guarantee delivery. It does this by changing the delivery mode on the message producers to Persistent.

  • fiper.acs.jms.ttl. This property sets the time-to-live value (in minutes) for persistent messages. The default value for this entry is 0, which means that the messages are kept in the cache until they are successfully delivered to all known recipients.