Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 4.1.0.Final, 4.0.24.Final
Affects Version/s: None
Labels:
- downstream_dependency

Git Pull Request:
https://github.com/wildfly/jboss-ejb-client/pull/421, https://github.com/wildfly/jboss-ejb-client/pull/425

We need to try to share channels created via ClientServiceHandle and/or make sure that all channels are closed on redeploy and undeploy.
Or else the limit of open outbound channels in Remoting is eventually reached.

is blocked by

REM3-350 Add API for closing the channel at ClientServiceHandle

Resolved

is cloned by

JBEAP-18322 [GSS](7.3.z) EJBCLIENT-347 / REM3-350 - Remoting outbound channels are not closed

Closed

is incorporated by

WFCORE-4777 Upgrade JBoss Remoting from 5.0.16 to 5.0.17

Closed

WFLY-12615 Upgrade jboss-ejb-client to 4.0.25.Final

Closed

WFLY-12879 Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final

Closed

is related to

EJBCLIENT-370 EJBTransportProvider should provide a default implementation of its close method

Resolved

JBEAP-17475 [GSS](7.2.z) EJBCLIENT-347 / REM3-350 - Remoting outbound channels are not closed

Closed

WFLY-12911 Upgrade jboss-ejb-client to 4.0.28.Final

Closed

relates to

REM3-346 Remote channels config for max outbound and inbound channels must be equal to min value of both ends

Resolved

EJBCLIENT-348 Add trace logging for EJBClientContext creation and channel opening

Resolved

REM3-345 Add trace logging for ClientServiceHandle opening and closing channels

Resolved

(3 is related to, 3 relates to)

Assignee:: Tomasz Adamski

Reporter:: Flavia Rainone

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019/08/28 5:15 PM

Updated:: 2021/09/23 3:51 PM

Resolved:: 2020/03/24 7:28 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates