[JBoss JIRA] (WFCORE-2780) Improve buffer-pool model description
by Romain Pelisse (Jira)
[ https://issues.jboss.org/browse/WFCORE-2780?page=com.atlassian.jira.plugi... ]
Romain Pelisse reassigned WFCORE-2780:
--------------------------------------
Assignee: Jeff Mesnil (was: Romain Pelisse)
> Improve buffer-pool model description
> -------------------------------------
>
> Key: WFCORE-2780
> URL: https://issues.jboss.org/browse/WFCORE-2780
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Romain Pelisse
> Assignee: Jeff Mesnil
> Priority: Minor
>
> Current state of buffer-pool model description:
> {code}
> [standalone@localhost:9990 /] /subsystem=io/buffer-pool=foo:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "Defines buffer pool",
> "capabilities" => [{
> "name" => "org.wildfly.io.buffer-pool",
> "dynamic" => true
> }],
> "attributes" => {
> "buffer-size" => {
> "type" => INT,
> "description" => "The size of each buffer slice in bytes, if not set optimal value is calculated based on available RAM resources in your system.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> "buffers-per-slice" => {
> "type" => INT,
> "description" => "How many buffers per slice, if not set optimal value is calculated based on available RAM resources in your system.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> "direct-buffers" => {
> "type" => BOOLEAN,
> "description" => "Does the buffer pool use direct buffers, some platforms don't support direct buffers",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> {code}
> Following improvements should be done to it:
> * In {{buffer-size}} and {{buffers-per-slice}} description there is mentioned something called 'slice'. Nowhere is described what it is. Suggested improvement: Explain what slice is, preferably in buffer-pool model description.
> * In {{buffer-size}} and {{buffers-per-slice}} description there is this sentence: ''...if not set optimal value is calculated based on available RAM resources in your system" - how it is calculated? Is there any default fixed value? User would like to know this. Suggestion: Add explanation about default value.
> * In {{direct-buffers}} description there is mentioned that some platforms don't support direct buffers? Is there mentioned which one or what determines whether direct buffers are supported on given platform? Suggested improvement: Explain what element determines whether direct buffers are supported.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-2620) Add ability to read computed runtime values of IO subsystem buffer-pool attributes
by Romain Pelisse (Jira)
[ https://issues.jboss.org/browse/WFCORE-2620?page=com.atlassian.jira.plugi... ]
Romain Pelisse reassigned WFCORE-2620:
--------------------------------------
Assignee: Jeff Mesnil (was: Romain Pelisse)
> Add ability to read computed runtime values of IO subsystem buffer-pool attributes
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-2620
> URL: https://issues.jboss.org/browse/WFCORE-2620
> Project: WildFly Core
> Issue Type: Enhancement
> Affects Versions: 3.0.0.Beta13
> Reporter: Romain Pelisse
> Assignee: Jeff Mesnil
> Priority: Minor
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> In IO subsystem there are some attributes which are calculated based on available system resources if not explicitly specified. These attributes are:
> * worker
> ** io-threads
> ** task-max-threads
> * buffer-pool
> ** buffer-size
> ** buffers-per-slice
> ** direct-buffers
> Currently these computed values are not visible for user in the subsystem configuration even with include-runtime=true.
> To show these runtime values would definitely improve UX.
> Worker attributes are covered by EAP7-616 .
> This issue is about buffer-pool attributes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-12063:
-------------------------------------
Oh, then that is fine then! :) I did run a lot of WF unit tests locally already as well [https://issues.jboss.org/browse/WFLY-12063?focusedCommentId=13757425&page...]
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12063:
-----------------------------------------
https://github.com/wildfly/wildfly/pull/12532
It's a Draft; it's got the 'hold' label on it. It's not going to get merged. I just want to see what happens with CI. I agree the real thing should come in via a Hibernate update, or at least with the update applied and tested in the Hibernate 5.3 branch.
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-8124) Unify arquillian defaultProtocol in TS
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-8124?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-8124:
-----------------------------------
Component/s: XTS
> Unify arquillian defaultProtocol in TS
> --------------------------------------
>
> Key: WFLY-8124
> URL: https://issues.jboss.org/browse/WFLY-8124
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite, XTS
> Reporter: Marek Kopecky
> Priority: Major
>
> Unify arquillian defaultProtocol in TS
> xts a rts module use servlet protocol. Jmx protocol is standard protocol:
> {noformat}
> [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -i servlet
> testsuite/integration/rts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" />
> testsuite/integration/xts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" />
> [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -iv servlet | wc -l
> 13
> [mkopecky@dhcp-10-40-5-170 base] (7.x)$
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (ELY-1862) Fix infinite loop in SecurityEventVisitor#handleSyslogAuditEvent
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1862?page=com.atlassian.jira.plugin.s... ]
Farah Juma reassigned ELY-1862:
-------------------------------
Assignee: Ashley Abdel-Sayed (was: Farah Juma)
> Fix infinite loop in SecurityEventVisitor#handleSyslogAuditEvent
> ----------------------------------------------------------------
>
> Key: ELY-1862
> URL: https://issues.jboss.org/browse/ELY-1862
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Farah Juma
> Assignee: Ashley Abdel-Sayed
> Priority: Blocker
> Fix For: 1.10.0.CR6
>
>
> Found during QE's coverity scan:
> {code}
> *** CID 1485949: SpotBugs: Correctness (FB.IL_INFINITE_RECURSIVE_LOOP)
> /auth/server/base/src/main/java/org/wildfly/security/auth/server/event/SecurityEventVisitor.java:
> 129 in org.wildfly.security.auth.server.event.SecurityEventVisitor.handleSyslogAuditEvent(org.wildfly.security.auth.server.event.SyslogAuditEvent,
> java.lang.Object)()
> 123 *
> 124 * @param event the security event
> 125 * @param param the visitor parameter
> 126 * @return the visitor return value
> 127 */
> 128 public R handleSyslogAuditEvent(final SyslogAuditEvent
> event, final P param) {
> >>> CID 1485949: SpotBugs: Correctness (FB.IL_INFINITE_RECURSIVE_LOOP)
> >>> There is an apparent infinite recursive loop.
> 129 return handleSyslogAuditEvent(event, param);
> 130 }
> 131
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-6008) Clustering API leaks its classloader to applications
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-6008?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-6008:
-------------------------------
Description:
The following callbacks leak the org.wildfly.clustering.server classloader to applications:
* CommandDispatcher command execution
* CommandDispatcherFactory cluster membership listener
* Cache topology membership listener
* Registry listener
* ServiceProviderRegistry listener
was:This should be as simple as leveraging the ContextService to create serializable contextual proxies of the submitted command instance.
> Clustering API leaks its classloader to applications
> ----------------------------------------------------
>
> Key: WFLY-6008
> URL: https://issues.jboss.org/browse/WFLY-6008
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> The following callbacks leak the org.wildfly.clustering.server classloader to applications:
> * CommandDispatcher command execution
> * CommandDispatcherFactory cluster membership listener
> * Cache topology membership listener
> * Registry listener
> * ServiceProviderRegistry listener
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-12063:
-------------------------------------
[~brian.stansberry] imo, we could do the upgrade in WildFly but that sort of goes against our "upstream first" rule. As, we could get stuck if for some reason, the Hibernate team doesn't update the ORM 5.3.x branch to work with the ByteBuddy upgrade.
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months