ConnectionProbe.onConnectEvent() is relevant to the client side only.
The close event should be invoked. If you don't mind sharing your test
case, we can take a closer look to see why it's not.
> Zack Manning <mailto:zack.manning_at_vevo.com>
> March 8, 2017 at 16:02
>
> Hey All,
>
> Not sure if this list is active anymore, but I am having trouble using
> monitoring probes to meter connect events through Grizzly. On my
> connection probe I get ACCEPT, READ, and WRITE events, but no
> CONNECTED, or CLOSE. Is there a secret to getting these events to
> show up?
>
> This is inside a test utilizing a vanilla Jersey setup with an empty
> resource returning a simple constant. Any pointers there would be
> much appreciated!
>
> Zack
>