Messaging Configuration

broadleaf.messaging.clusterServiceImplementationType

Specify which camel cluster service implementation to support. Supported values are: file, zookeeper, kubernetes, and none. none is useful to disable out-of-the-box config, presumably so you can manually add different or new cluster service implementation support. Default is file. file is suitable for local development, but in a real-world production environment, zookeeper or kubernetes should be used instead in order to support proper cluster service establishment across multiple instances of a given service.

broadleaf.messaging.clusterK8sAppLabel

If using kubernetes cluster service implementation type, this is the name of the pod label used to group common service instances. The default value is k8s-app.

broadleaf.messaging.clusterK8sAppLabelValue

If using kubernetes cluster service implementation type, this is the value for the pod label. The default is unknown and this value must be set (generally as a environment variable on a pod definition) in order to inform the camel support running in that pod.

broadleaf.persistence.notification.*

See com.broadleafcommerce.common.messaging.notification.NotificationProperties for full list of options.

broadleaf.persistence.retry.*

See com.broadleafcommerce.common.messaging.notification.RetryProperties for full list of options.

broadleaf.resource.lock.defaultStagnationThreshold

The time, once elapsed, in which the system will consider a lock abandoned and allow another requester to acquire the lock. The default value is 15 (seconds).

broadleaf.resource.lock.lockPurgePageSize

The number of lock records to purge in a single page. Default value is 1000.