This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[14:41:08] * ChanServ sets mode: +o temporalfox [15:49:00] * ChanServ sets mode: +o temporalfox

[16:52:10] * ChanServ sets mode: +o temporalfox [18:15:52] <joem86> when I use groovy's vertx.createDatagramSocket(…) listening on port 1234, I can deploy multiple verticle instances and they all claim to `listen` successfully. When I replicate the code in Java and deploy multiple instances only one binds to port 1234, the rest throw a BindException: Address already in use. I'm looking at the source for DatagramSocketOptions currently, but I'm wondering, *should* it be possible to deploy multiple verticles [18:15:52] <joem86> with datagrams listening on the same udp port? [18:38:25] <cescoffier> joem86 : only if it's instance of the same verticle I think [18:39:44] <joem86> I actually just figured it out. Calling new DatagramSocketOptions([:]) in groovy sets reuseAddress = true. Calling new DatagramSocketOptions() in java defaults it to false. [19:49:43] * ChanServ sets mode: +o temporalfox

[22:30:07] *** ChanServ sets mode: +o temporalfox

[23:24:06] <AlexLehm> temporalfox: do you have time to talk about the mail issue?

[23:24:15] <temporalfox> soon

[23:24:23] <AlexLehm> or rather I have 2 issues, one direct and one indirect

[23:24:26] <AlexLehm> ok

[23:31:25] <temporalfox> hi AlexLehm I'm available now

[23:38:16] <AlexLehm> ok, hi Julien

[23:38:55] <temporalfox> hi

[23:38:57] <temporalfox> how arey ou ?

[23:39:14] <AlexLehm> fine, hope you are too

[23:40:16] <AlexLehm> yesterday I tried to run the unit tests for the mail project and found that one test was failing which was not run in maven due to wrong filename of the test class

[23:40:53] <AlexLehm> i changed that and fixed the issue, which is in the checking of the ssl cert when using starttls

[23:41:06] <AlexLehm> this was rather simple and the test now works

[23:41:56] <AlexLehm> however, I have two test classes that do not work when being run in the same test session, e.g. with maven, because they use a default SSLSocketFactory, which I was setting with a security property and that doesn't work

[23:42:28] <AlexLehm> the first test gets to set the factory and the 2nd uses the wrong factory since it the object is only created once

[23:43:33] <AlexLehm> this is broken since the implementation of the ticket about improving ssl, but I didn't notice that either since one of the tests was called *Test2

[23:47:00] <AlexLehm> I think I know how to fix the test issue, but this might require rewriting a class from the wiser project which i use as test server and that might require a ip check from Eclipse

[23:48:26] <temporalfox> ok

[23:48:50] <temporalfox> perhaps we can run them using integration test ?

[23:48:58] <temporalfox> this allow to run tests with different JVM settings

[23:49:04] <temporalfox> i.e different system properties

[23:49:09] <AlexLehm> that will probably work

[23:49:15] <temporalfox> we have done that in vertx core

[23:49:58] <temporalfox> because we needed to test different settings for javaalpn agent and classpath

[23:50:05] <temporalfox> (testing alpn / openssl)

[23:50:47] <AlexLehm> ah yes, you're right

[23:51:37] <AlexLehm> not sure how that works, does that mean that maven starts a new java for each test?

[23:52:49] <temporalfox> I'm not fan of doing integration tests

[23:53:03] <temporalfox> but if you want to use different JVM settings or classpath settings

[23:53:07] <temporalfox> that's probably the best way

[23:53:18] <temporalfox> actually we could have done that for testing the proxy jar stuff

[23:53:26] <temporalfox> yes means that

[23:53:30] <AlexLehm> ok

[23:53:35] <temporalfox> and you can have a different classpath if needed

[23:55:30] <AlexLehm> ok, i will try that now