[
https://issues.apache.org/jira/browse/IGNITE-22464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854423#comment-17854423
]
Ignite TC Bot commented on IGNITE-22464:
----------------------------------------
{panel:title=Branch: [pull/11387/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11387/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7911362]]
* {color:#013220}ClientTestSuite:
IgniteClientLifecycleEventListenerTest.testClientLifecycleEvents - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7910309&buildTypeId=IgniteTests24Java8_RunAll]
> Java thin client: Introduce events for start/stop of client
> -----------------------------------------------------------
>
> Key: IGNITE-22464
> URL: https://issues.apache.org/jira/browse/IGNITE-22464
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, we have events for connect/disconnect and for start/end of each
> request. Sometimes it's required to track start/stop of client (for example,
> some metrics can be exposed on client start), so it's nice to have an ability
> to listen start/stop client events.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
