Unit test failure "because of Create topic Chat_SimpleChatMessage"

[edhage]

Using the new commit that includes support for java version 13 I do a >>mvn package in the root directory. It fails at test with Chat_SimpleChatMessage.

The logging:
`[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.529 s -
in com.adlinktech.gateway.DdsEndpoint.DdsProducer_QosChange_Test
[INFO] Running com.adlinktech.gateway.DdsEndpoint.Regression_BB_149_Test
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 16.792 s
<<< FAILURE! - in com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test

[ERROR] testLatencyDurationChange(com.adlinktech.gateway.DdsEndpoint.DdsConsumer
_QosChange_Test) Time elapsed: 4.995 s <<< FAILURE!
java.lang.AssertionError: Error : org.apache.camel.FailedToCreateRouteException:
Failed to create route DdsTestRoute: Route(DdsTestRoute)[[From[dds://Chat_Simpl
eChatMessage:0/Cha... because of Create topic Chat_SimpleChatMessage(reason: Pre
condition not met: Failed to resolve Topic 'Chat_SimpleChatMessage'. - DomainPar
ticipantImpl.java:716)
at com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test.init(Dd
sConsumer_QosChange_Test.java:123)

[INFO] Running com.adlinktech.gateway.DdsEndpoint.ZZZ_OsplStop_AfterTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 s -
in com.adlinktech.gateway.DdsEndpoint.ZZZ_OsplStop_AfterTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.415 s -
in com.adlinktech.gateway.DdsEndpoint.DdsProducer_ErrorHandling_Test
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.237 s -
in com.adlinktech.gateway.DdsEndpoint.Regression_BB_149_Test
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] DdsConsumer_QosChange_Test.init:123 Error : org.apache.camel.FailedToC
reateRouteException: Failed to create route DdsTestRoute: Route(DdsTestRoute)[[F
rom[dds://Chat_SimpleChatMessage:0/Cha... because of Create topic Chat_SimpleCha
tMessage(reason: Precondition not met: Failed to resolve Topic 'Chat_SimpleChatM
essage'. - DomainParticipantImpl.java:716)
[INFO]
[ERROR] Tests run: 74, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Vortex Gateway 3.0.2-SNAPSHOT:
[INFO]
[INFO] Vortex Gateway ..................................... SUCCESS [ 0.011 s]
[INFO] Vortex Gateway: OpenSpliceDDS' idlpp Maven plugin .. SUCCESS [ 24.318 s]
[INFO] Vortex Gateway: Camel/OpenSpliceDDS component ...... FAILURE [ 29.704 s]
[INFO] Vortex Gateway examples (parent pom) ............... SKIPPED
[INFO] Vortex Gateway example: camel-example-dds .......... SKIPPED
[INFO] Vortex Gateway example: camel-example-dds-rest ..... SKIPPED
[INFO] Vortex Gateway example: camel-example-dds-websocket SKIPPED
[INFO] Vortex Gateway example: camel-example-dds-spring ... SKIPPED
[INFO] Vortex Gateway example: camel-messages-mode ........ SKIPPED
[INFO] Vortex Gateway example: pingpong ................... SKIPPED
[INFO] Gateway tests (parent pom) ......................... SKIPPED
[INFO] Gateway examples tests (parent pom) ................ SKIPPED
[INFO] Gateway tests: camel-example-dds ................... SKIPPED
[INFO] Vortex Gateway archetype for Maven ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 54.808 s
[INFO] Finished at: 2019-10-10T10:38:17+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
20:test (default-test) on project camel-ospl: There are test failures.
[ERROR]
[ERROR] Please refer to D:\Infraflex\vortex-gateway-master\camel-ospl\target\sur
efire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].
dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
eption
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command

[ERROR] mvn -rf :camel-ospl`

[edhage]

My java and maven data:

Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T17:06:
6+02:00)
Java version: 13, vendor: Oracle Corporation
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

[JEnoch]

Could you please do the following in your vortex-gateway\camel-ospl directory:

• delete the ospl-*.log files that might be present
• run the command: mvn -Dtest=com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test clean test

Then attach in this issue the ospl-*.log files that have been generated in vortex-gateway\camel-ospl, as well as the files in vortex-gateway\camel-ospl\target\surefire-reports.

Also, which version of OpenSpliceDDS are you using ?

[edhage]

The release I am using:
Vortex OpenSplice HDE Release 6.9.181127OSS For x86_64.win64, Date 2018-11-28
2019-10-17T08-26-53_658.dumpstream.txt
TEST-com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test.xml.txt

ospl-info.log

com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test-output.txt

com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test.txt

ospl-error.log

[JEnoch]

Looking at your TEST-com.adlinktech.gateway.DdsEndpoint.DdsConsumer_QosChange_Test.xml.txt file, it seems the test succeed this time.

It's either a random issue, either an issue related to the tests that are run previously (when compiling all).

Could you please try to reproduce the test failure running the same procedure I described above ?
If you can't reproduce it this way, then just run "mvn test" (without the -Dtest option) to try to reproduce it.
And attach the logs once you have a test failure.