netty5

andreacavalli/netty5

Fork 0

Commit Graph

Author	SHA1	Message	Date
Vladimir Kostyukov	0a0da67f43	Introduce SingleThreadEventLoop.registeredChannels (#8428 ) Motivation: Systems depending on Netty may benefit (telemetry, alternative even loop scheduling algorithms) from knowing the number of channels assigned to each EventLoop. Modification: Expose the number of channels registered in the EventLoop via SingleThreadEventLoop.registeredChannels. Result: Fixes #8276.	2019-03-28 11:33:12 +00:00
Norman Maurer	d133bf06a4	Allow to schedule tasks up to Long.MAX_VALUE (#7972 ) Motivation: We should allow to schedule tasks with a delay up to Long.MAX_VALUE as we did pre 4.1.25.Final. Modifications: Just ensure we not overflow and put the correct max limits in place when schedule a timer. At worse we will get a wakeup to early and then schedule a new timeout. Result: Fixes https://github.com/netty/netty/issues/7970.	2018-05-30 11:11:42 +02:00
Norman Maurer	b47fb81799	EventLoop.schedule with big delay fails (#7402 ) Motivation: Using a very huge delay when calling schedule(...) may cause an Selector error when calling select(...) later on. We should gaurd against such a big value. Modifications: - Add guard against a very huge value. - Added tests. Result: Fixes [#7365]	2018-04-24 11:15:20 +02:00

Author

SHA1

Message

Date

Vladimir Kostyukov

0a0da67f43

Introduce SingleThreadEventLoop.registeredChannels (#8428 )

Motivation:

Systems depending on Netty may benefit (telemetry, alternative even loop scheduling algorithms) from knowing the number of channels assigned to each EventLoop.

Modification:

Expose the number of channels registered in the EventLoop via SingleThreadEventLoop.registeredChannels.

Result:

Fixes #8276.

2019-03-28 11:33:12 +00:00

Norman Maurer

d133bf06a4

Allow to schedule tasks up to Long.MAX_VALUE (#7972 )

Motivation:

We should allow to schedule tasks with a delay up to Long.MAX_VALUE as we did pre 4.1.25.Final.

Modifications:

Just ensure we not overflow and put the correct max limits in place when schedule a timer. At worse we will get a wakeup to early and then schedule a new timeout.

Result:

Fixes https://github.com/netty/netty/issues/7970.

2018-05-30 11:11:42 +02:00

Norman Maurer

b47fb81799

EventLoop.schedule with big delay fails (#7402 )

Motivation:

Using a very huge delay when calling schedule(...) may cause an Selector error when calling select(...) later on. We should gaurd against such a big value.

Modifications:

- Add guard against a very huge value.
- Added tests.

Result:

Fixes [#7365]

2018-04-24 11:15:20 +02:00

3 Commits