-
Notifications
You must be signed in to change notification settings - Fork 15
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
For native broker currently we have some ENV vars being set in the code, but these variables do not do anything right now, because we use static config. Here:
blazingmq-sdk-java/bmq-sdk/src/test/java/com/bloomberg/bmq/it/util/BmqBrokerTestServer.java
Lines 145 to 155 in 7a89c71
| Map<String, String> env = pb.environment(); | |
| env.put("BMQ_PREFIX", envPath); | |
| env.put("BMQ_STORAGE", storagePath.toString()); | |
| logger.info("BlazingMQ Broker storage directory: {}", storagePath); | |
| outputFile = new File(tmpFolder.resolve("output").toString()); | |
| // Common environment vars | |
| env.put("BMQ_PORT", String.valueOf(sessionOptions.brokerUri().getPort())); | |
| env.put("BMQ_HOSTTAGS_FILE", "/bb/bin/bbcpu.lst"); | |
| env.put("PYTHONPATH", envPath + "/python"); |
This means that currently we can use params listed in static config only, so storage path, logs path, broker port are the same for each launched broker. The last means that native IT brokers could only be launched on a default 30114 port, and no parallel ITs execution possible.
We create a TMP folder which should contain storage, logs etc, but we are not able to use it with a static config:
blazingmq-sdk-java/bmq-sdk/src/test/java/com/bloomberg/bmq/it/util/BmqBrokerTestServer.java
Line 139 in 7a89c71
| tmpFolder = makeTempDir(envPath, "localBMQ_"); |
Expected Behavior
Native brokers in ITs should be able to use TMP folders and non-default parameters.
Steps To Reproduce
Launch ITs with -Dit.brokerDir=/path/to/native/broker
BlazingMQ Java SDK Version
0.0.10
Anything else?
No response