- Apr 23, 2013
-
-
Denis Bazhenov authored
-
- Apr 19, 2013
-
-
Denis Bazhenov authored
-
Ceki Gulcu authored
correct ThreadPoolFactoryBean link to javadocs, correct typo in name of fieldsToCascade field in ComponentDelegate, added receiver function in ConfigurationDelegate (incomplete)
-
- Apr 18, 2013
-
-
Ceki Gulcu authored
make sure that all the 'view as groovy' links work, Gaffer does not support <receiver> at this stage, nor does the translator
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Carl Harris authored
-
Carl Harris authored
This should resolve LOGBACK-749.
-
Tim Clemons authored
-
Tim Clemons authored
-
Tim Clemons authored
throws an exception, attempt to provide the IP address instead. This is useful on those systems without a hostname explicitly defined.
-
Ceki Gulcu authored
-
- Apr 17, 2013
-
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
made FileAppenderResilienceTest more tolerant, added code wait for compression job in TimeBasedRollingPolicy
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
- Apr 16, 2013
-
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Ceki Gulcu authored
-
Carl Harris authored
-
Carl Harris authored
In the receiveMessage and receiveWithContext tests, only ten milliseconds were allowed for the appender to dispatch the message over the socket. Practical experience suggests that on the build system, the actual latency is on the order of hundreds of milliseconds. I changed the allowed wait time to 1000 milliseconds. This should have little impact on test duration, as the test will finish as soon as the latch we're awaiting is updated. The number of iterations for the loop in lateServerLaunch was derived from the delay allowed for the appender latch. The new value for the delay resulted in an iteration count of one. I changed this test to simply use a fixed iteration count.
-
Carl Harris authored
-
Carl Harris authored
testConnectionFails was expecting the connector thread to exit after being interrupted, with latency no greater than the configured delay between connection attempts. However, the call to SocketFactory.createSocket may not return immediately on interrupt. Now, we allow 4 * DELAY for the thread to exit. This commit should allow more than enough tolerance, but (as it generally has no effect on the run duration of the test) we could increase the allowed delay even further if it proves too sensitive to timing variations on the build system.
-
Ceki Gulcu authored
-