[
https://issues.apache.org/jira/browse/TOMEE-4560?focusedWorklogId=1000408&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1000408
]
ASF GitHub Bot logged work on TOMEE-4560:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jan/26 07:25
Start Date: 16/Jan/26 07:25
Worklog Time Spent: 10m
Work Description: rzo1 commented on PR #2408:
URL: https://github.com/apache/tomee/pull/2408#issuecomment-3758539934
> I do not understand the specs/codebase much but would be happy to
contribute...
@kartiksirigeri Great to hear! Please feel free to join the dev mailing list
(mailto:[email protected]) and start a new thread about the
registry. We truly welcome all contributions - so thank you for taking the
initiative and opening this PR.
There has been some prior discussion on the topic
[here](https://lists.apache.org/thread/p6qht01wjtqfjrywzfkdbk492xkd4ol6), but I
agree that continuing the conversation in a new thread makes sense. In short
(to summarize @dblevins from the other thread), we would need to (at least
attempt to) run the EJB TCK of EE 9.1. Happy to share more details on the
mailing list.
Issue Time Tracking
-------------------
Worklog Id: (was: 1000408)
Time Spent: 1.5h (was: 1h 20m)
> Memory leak for EJB3 stateful bean
> ----------------------------------
>
> Key: TOMEE-4560
> URL: https://issues.apache.org/jira/browse/TOMEE-4560
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
> Affects Versions: 8.0.16
> Reporter: Kartik Sirigeri
> Priority: Major
> Attachments: EjbProxyHandler_EJB2.png, EjbProxyHandler_EJB3.png,
> test_project.zip
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The bean references are not getting removed from
> ProxyRegistry.liveHandleRegistry map when the the method annotated wtih
> '@Remove' annotation for EJB3 stateful bean is invoked. While the call for
> remove method on EJB2 stateful beans removes the entry from
> ProxyRegistry.liveHandleRegistry map immmediately. It seems the
> EjbObjectProxyHandler._invoke method checks for EJB_OBJECT, EJB_LOCAL type
> along with the operation type, this check fails for EJB3 beans and the beans
> are not removed from the ProxyRegistry.liveHandleRegistry map unless any
> business methods are invoked which would invaldiate the map due to
> InvalidateReferenceException. This causes a memory leak unless any business
> method is called after the invocation of @Remove method in EJB3.
>
> Snapshot of the debug flow attached along with the test code
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
