Read XTAG events from Nomis and send to the AWS prison events topic.
By default queue health is not displayed since retrieving queue depth and DLQ depth suspected to be an intensive operation for Oracle
However this variation of the /info endpoint will show queue details: /info?show-queue-details=true
The integration tests require a running instance of Oracle-XE and a running instance of AWS SQS localstack. Start these using:
docker-compose -f docker-compose-test.yml up
The Oracle docker image will not run in docker desktop under an M1 processor, so an intel VM is required - Colima. Also for now testContainers is not working under Colima until a better 'already up' test is found.
Given testContainer startup under colima is very slow you can just set the DOCKER_HOST to colima just for starting the required containers
Hint: If colima does not start, try shutdown Docker Desktop and trying again (Docker Desktop can be started after colima if required)
brew install colima
colima start --arch x86_64 --memory 4 --network-address
export DOCKER_HOST="unix://${HOME}/.colima/docker.sock"
docker-compose -f docker-compose-test.yml up
or if colima is already running
export DOCKER_HOST="unix://${HOME}/.colima/docker.sock"
docker compose -f docker-compose-test.yml up
Based on the instructions here: https://blog.jdriven.com/2022/07/running-oracle-xe-with-testcontainers-on-apple-silicon, add these lines to your .zshrc or similar:
export TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE=/var/run/docker.sock # in case testContainers is used in future
export DOCKER_HOST="unix://${HOME}/.colima/docker.sock"
Then install and start Colima (including an extra network parameter not mentioned in the site above):
brew install colima
colima start --arch x86_64 --memory 4 --network-address
Next run
docker compose -f docker-compose-test.yml up
Now, integration tests will run with these existing docker containers .
Testcontainers will not start new containers on Mac as the port technique to detect an already running instance does not work under colima.
Ensure you include this property setting which prevents errors accessing non-existent javax classes:
-Doracle.jakarta.jms.useEmulatedXA=false
Occasionally an upgrade to Colima (brew upgrade colima) will cause failure on Macs, to solve the issue revert to a previous working version.
Whilst quite old, V0.5.6 works on M1 Macs.
If Colima is running, stop it and uninstall the current version:
colima stop
brew uninstall colima
Install an old Colima (not currently possible via brew - but may be in future)
sudo curl -L -o /usr/local/bin/colima https://github.com/abiosoft/colima/releases/download/v0.5.6/colima-Darwin-arm64 && sudo chmod +x /usr/local/bin/colima
If missing lima or qemu when attempting to start the older version of Colima (error messages will state missing dependences) they can be easily installed via brew
If Colima still fails to start (eg ...colima/default/daemon/daemon.pid: no such file or directory) reinstall qemu.