de.griefed.serverpackcreator.spring.task

Class ArtemisConfig

java.lang.Object

de.griefed.serverpackcreator.spring.task.ArtemisConfig

All Implemented Interfaces:

org.springframework.boot.autoconfigure.jms.artemis.ArtemisConfigurationCustomizer

@Configuration
public class ArtemisConfig
extends java.lang.Object
implements org.springframework.boot.autoconfigure.jms.artemis.ArtemisConfigurationCustomizer

How to implement a task queue using Apache Artemis and Spring Boot
Huge Thank You to Gauthier for writing the above guide on how to implement a JMS. Without it this implementation of Artemis would have either taken way longer or never happened at all. I managed to translate their Kotlin-code to Java and make the necessary changes to fully implement it in ServerPackCreator.
Configuration for our Artemis JMS.

Constructor Summary

Constructors

Constructor and Description
ArtemisConfig(ApplicationProperties injectedApplicationProperties) Constructor responsible for our DI.

Method Summary

Modifier and Type

Method and Description

void

customize(org.apache.activemq.artemis.core.config.Configuration configuration) Customize our configuration. Set the default consumer windows size to 0. Set the maximum disk usage from our property de.griefed.serverpackcreator.spring.artemis.queue.max_disk_usage. Set the address to tasks.background. Set the queue configuration to tasks.background. Set the name to tasks.background. Set the last value key to unique_id. Set the routing type to RoutingType.ANYCAST. Add our queue configuration.. All of this ensures that any message added will be deduplicated and worked on one by one.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ArtemisConfig

@Autowired
public ArtemisConfig(ApplicationProperties injectedApplicationProperties)

Constructor responsible for our DI.

Parameters:

injectedApplicationProperties - Instance of ApplicationProperties.

Method Detail

customize

public void customize(org.apache.activemq.artemis.core.config.Configuration configuration)

Customize our configuration.
Set the default consumer windows size to 0.
Set the maximum disk usage from our property de.griefed.serverpackcreator.spring.artemis.queue.max_disk_usage.
Set the address to tasks.background.
Set the queue configuration to tasks.background.
Set the name to tasks.background.
Set the last value key to unique_id.
Set the routing type to RoutingType.ANYCAST.
Add our queue configuration..
All of this ensures that any message added will be deduplicated and worked on one by one. No messages should, at any time, be processed in parallel. Whilst working on them in parallel would increase the speed at which multiple serer packs are generated, we want to make sure neither the CurseForge API, nor the system our webservice is running on receives a heavy load. Economically speaking, we are trying to be nice neighbours and not claim too many resources for ourselves.

Specified by:

customize in interface org.springframework.boot.autoconfigure.jms.artemis.ArtemisConfigurationCustomizer

Parameters:

configuration - Artemis configuration.