[JBoss JIRA] (WFLY-11784) App classloader leaked by IIOP WorkCacheManager cache
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11784?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11784:
------------------------------------
Priority: Critical (was: Major)
> App classloader leaked by IIOP WorkCacheManager cache
> -----------------------------------------------------
>
> Key: WFLY-11784
> URL: https://issues.jboss.org/browse/WFLY-11784
> Project: WildFly
> Issue Type: Bug
> Components: IIOP
> Affects Versions: 16.0.0.Beta1
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Priority: Critical
> Fix For: 17.0.0.Beta1
>
>
> After redeploys, application ear module classloaders are left in org.wildfly.iiop.openjdk.rmi.WorkCacheManager's classesByLoader map:
> {code}
> com.sun.corba.se.impl.transport.SelectorImpl @ 0xc12234b8 SelectorThread Thread
> '- contextClassLoader org.jboss.modules.ModuleClassLoader @ 0xc075bea0
> '- classes java.util.Vector @ 0xc075c4a8
> '- elementData java.lang.Object[160] @ 0xc1afb200
> '- [58] class org.wildfly.iiop.openjdk.rmi.ValueAnalysis @ 0xc180e4b0 |
> '- cache org.wildfly.iiop.openjdk.rmi.WorkCacheManager @ 0xc180e520
> |- classesByLoader java.util.HashMap @ 0xc180e730
> | '- table java.util.HashMap$Node[16] @ 0xc1ba2ff8
> | |- [14] java.util.HashMap$Node @ 0xc37b01e0
> | | '- key org.jboss.modules.ModuleClassLoader @ 0xc3677958
> {code}
> This was previously a weak map, but we switched to strong caching with explicit clean up on undeploy. It looks like that clean up is missed in some case.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11898) Add ability to group distributed session attributes to avoid cost of SESSION granularity
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-11898:
-----------------------------------
Summary: Add ability to group distributed session attributes to avoid cost of SESSION granularity
Key: WFLY-11898
URL: https://issues.jboss.org/browse/WFLY-11898
Project: WildFly
Issue Type: Feature Request
Components: Clustering
Affects Versions: 16.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Since SESSION granularity requires the replication of *all* session attribute if *any* attribute was modified in a given request, most distributed web applications should leverage ATTRIBUTE granularity whenever to possible to reduce the replication payload costs per request.
However, if session attribute contains any reference to another session attribute, they are forced to use SESSION granularity to avoid losing referential integrity on failover and duplication of serialized data.
The proposal is to allow users the ability to annotate their session attribute classes such that they can group specific attribute together, while still being able to leverage ATTRIBUTE granularity for the remainder of their session attributes.
>From the user's perspective, I envision something like this:
@SessionAttributeGroup("order")
public class Order implements Serializable {
List<OrderItem> items;
}
@SessionAttributeGroup("order")
public class OrderItem implements Serializable {
//...
}
Thus the code:
session.setAttribute("order", order);
session.setAttribute("customized-item", item);
will result in both attributes being store within a single cache entry.
Internally, we use the @SessionAttributeGroup as the attribute name, and a Map<String, Object> as the attribute value, keyed by the actual attribute name.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11897) SFSB expiration can fail
by Dennis Reed (Jira)
[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ]
Dennis Reed commented on WFLY-11897:
------------------------------------
One simple fix: add a retry in org.wildfly.clustering.ejb.infinispan.BeanExpirationScheduler$ExpirationTask#run instead of just logging the error.
But I suspect that could cause other issues with constant retries if there was a different problem that wasn't just from bad timing.
> SFSB expiration can fail
> ------------------------
>
> Key: WFLY-11897
> URL: https://issues.jboss.org/browse/WFLY-11897
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Dennis Reed
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: WFLY-11897.btm, test.ear
>
>
> There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11897) SFSB expiration can fail
by Dennis Reed (Jira)
[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ]
Dennis Reed updated WFLY-11897:
-------------------------------
Steps to Reproduce:
Configure attached Byteman script that triggers the bug.
Attached reproducer contains a simple EJB and a jsp (http://localhost:8080/test to run) that calls the EJB to trigger the bug, waits to give expiration a chance to run, then tries to call the EJB again. The JSP logs "PASS" or "FAIL" to stdout.
Note: SFSB in reproducer has a 1 minute timeout in order to trigger the bug somewhat quickly, and the byteman script waits accordingly. The wait would need to be increased for a longer SFSB timeout.
was:
Configure attached Byteman script that triggers the bug.
Attached reproducer contains a simple EJB and a jsp (http://localhost:8080/test to run) that calls the EJB to trigger the bug, waits to give expiration a chance to run, then tries to call the EJB again.
Note: SFSB in reproducer has a 1 minute timeout in order to trigger the bug somewhat quickly, and the byteman script waits accordingly. The wait would need to be increased for a longer SFSB timeout.
> SFSB expiration can fail
> ------------------------
>
> Key: WFLY-11897
> URL: https://issues.jboss.org/browse/WFLY-11897
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Dennis Reed
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: WFLY-11897.btm, test.ear
>
>
> There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11897) SFSB expiration can fail
by Dennis Reed (Jira)
[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ]
Dennis Reed moved JBEAP-16602 to WFLY-11897:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11897 (was: JBEAP-16602)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: EJB)
Affects Version/s: 11.0.0.Final
(was: 7.1.6.GA)
> SFSB expiration can fail
> ------------------------
>
> Key: WFLY-11897
> URL: https://issues.jboss.org/browse/WFLY-11897
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Dennis Reed
> Assignee: Flavia Rainone
> Priority: Major
>
> There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month