[JBoss JIRA] (WFLY-11446) Bring consistency to use of TransactionSynchronizationRegistry in WildFly
by Scott Marlow (Jira)
Scott Marlow created WFLY-11446:
-----------------------------------
Summary: Bring consistency to use of TransactionSynchronizationRegistry in WildFly
Key: WFLY-11446
URL: https://issues.jboss.org/browse/WFLY-11446
Project: WildFly
Issue Type: Enhancement
Components: Transactions
Affects Versions: 15.0.0.Beta1
Reporter: Scott Marlow
Assignee: Tom Jenkinson
See [https://github.com/wildfly/wildfly/pull/11784#discussion_r237172364] discussion about JNDI lookup of "java:jboss/TransactionSynchronizationRegistry" returning org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper but other internal code sites (like EJB3, JPA container, JCA container) are directly using the org.wildfly.transaction.client.ContextTransactionSynchronizationRegistry.
My suggestion is that we consider taking steps to eliminate some of the duplicate classes, so that the same TSR is always used. I think some discussion is needed to get there, but wanted to have this tracking jira.
Somewhat related is that Hibernate ORM 5.3 now has direct references to org.wildfly.transaction.client.ContextTransactionManager + org.wildfly.transaction.client.LocalUserTransaction. Just mentioning in case its helpful to know for whomever looks at this jira.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11444) Remove unused dependencies from org.jboss.ejb3
by Yeray Borges (Jira)
Yeray Borges created WFLY-11444:
-----------------------------------
Summary: Remove unused dependencies from org.jboss.ejb3
Key: WFLY-11444
URL: https://issues.jboss.org/browse/WFLY-11444
Project: WildFly
Issue Type: Bug
Components: Server
Reporter: Yeray Borges
Assignee: Yeray Borges
{{org.jboss.ejb3}} module is exposing {{org.jboss.ejb3:jboss-ejb3-ext-api}} artifact which is only a bunch of interfaces that only depends on java.se.
That means all the module dependencies are unused and can be removed
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11416) Reports non_heap memory metrics
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFLY-11416?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda commented on WFLY-11416:
------------------------------------------
Thanks for fixing, non heap memory is exposed now
{code}
base:memory_committed_heap_bytes 2.16530944E8
base:memory_committed_non_heap_bytes 8.912896E7
base:memory_max_heap_bytes 4.77626368E8
base:memory_max_non_heap_bytes 7.80140544E8
base:memory_used_heap_bytes 1.59900312E8
base:memory_used_non_heap_bytes 7.7691544E7
{code}
> Reports non_heap memory metrics
> -------------------------------
>
> Key: WFLY-11416
> URL: https://issues.jboss.org/browse/WFLY-11416
> Project: WildFly
> Issue Type: Enhancement
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
> Fix For: 15.0.0.CR1
>
>
> Payara reports non_heap memory, WF doesn't
> {code}
> base:memory_committed_heap_bytes 5.0069504E8
> base:memory_committed_non_heap_bytes 1.65412864E8
> base:memory_max_heap_bytes 5.0069504E8
> base:memory_max_non_heap_bytes -1.0
> base:memory_used_heap_bytes 2.05958976E8
> base:memory_used_non_heap_bytes 1.48845312E8
> {code}
> WF reports
> {code}
> base:memory_committed_heap_bytes 1.06954752E8
> base:memory_max_heap_bytes 5.36870912E8
> base:memory_used_heap_bytes 6.4805664E7
> {code}
> It's also true that Helidon and OpenLiberty do not report non-heap space.
> Thorntail uses the same implementation as WF so it's irrelevant in this comparison.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11443) Explicitly exclude Netty dependencies
by Yeray Borges (Jira)
Yeray Borges created WFLY-11443:
-----------------------------------
Summary: Explicitly exclude Netty dependencies
Key: WFLY-11443
URL: https://issues.jboss.org/browse/WFLY-11443
Project: WildFly
Issue Type: Task
Reporter: Yeray Borges
Assignee: Yeray Borges
This issue was opened after discusing the changes in JBEAP-15938, it tries to avoid the possibility to include different Netty versions in product branches when they are comming from artemis dependncies.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11442) Remove unused dependencies from org.jboss.as.ejb3
by Yeray Borges (Jira)
Yeray Borges created WFLY-11442:
-----------------------------------
Summary: Remove unused dependencies from org.jboss.as.ejb3
Key: WFLY-11442
URL: https://issues.jboss.org/browse/WFLY-11442
Project: WildFly
Issue Type: Bug
Components: Server
Reporter: Yeray Borges
Assignee: Yeray Borges
Initial analisys checking only first level dependencies from the resource exposed by {{org.jboss.as.ejb3}} shows that these dependencies are being unused:
* org.jboss.jts
* org.wildfly.security.elytron-web.undertow-server
* org.jboss.as.weld
* org.wildfly.clustering.marshalling.spi
* org.wildfly.clustering.marshalling.api
* org.wildfly.client.config
* org.hibernate
The task here is verify that they are not used by any other machanism besides of being a first level dependency.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months