[JBoss JIRA] (ELY-474) Add @FunctionalInterface and other lambda-oriented enhancements
by David Lloyd (JIRA)
David Lloyd created ELY-474:
-------------------------------
Summary: Add @FunctionalInterface and other lambda-oriented enhancements
Key: ELY-474
URL: https://issues.jboss.org/browse/ELY-474
Project: WildFly Elytron
Issue Type: Enhancement
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.1.0.Beta5
Many of our interfaces are missing {@FunctionalInterface}. Also, many of our functional interfaces actually reflect lambda functions. At the least, review these to see if functional types are a better fit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2035) Util class tries to locate resource bundles using TCCL, which fails
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/JGRP-2035?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated JGRP-2035:
-------------------------------
Fix Version/s: 3.6.9
4.0
> Util class tries to locate resource bundles using TCCL, which fails
> -------------------------------------------------------------------
>
> Key: JGRP-2035
> URL: https://issues.jboss.org/browse/JGRP-2035
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.8
> Reporter: Jan Martiska
> Assignee: Paul Ferraro
> Priority: Blocker
> Fix For: 3.6.9, 4.0
>
>
> {{org.jgroups.util.Util}} class tries to locate jg-messages bundle using the TCCL, not its own class loader. In a Java SE environment, this typically doesn't matter, because the class loaders are the same, but in EAP, this means that jg-messages is sought by the class loader of the application rather than the class loader of JGroups module, which is obviously wrong. This is the offending line: https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util....
> The call to getBundle fails with a MissingResourceException (see http://docs.oracle.com/javase/6/docs/api/java/util/ResourceBundle.html#ge...) and because this code is in a static initializer, the Util class becomes unusable.
> This causes Hibernate applications with 2LC infinispan clustering backend to not work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ]
Jesper Pedersen updated JBJCA-1318:
-----------------------------------
Fix Version/s: WildFly/IronJacamar 1.3.4.Final
1.0.37.Final
> list driven ExceptionSorter, StaleConnectionChecker
> ---------------------------------------------------
>
> Key: JBJCA-1318
> URL: https://issues.jboss.org/browse/JBJCA-1318
> Project: IronJacamar
> Issue Type: Task
> Components: JDBC
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
> Priority: Minor
> Fix For: WildFly/IronJacamar 1.3.4.Final, 1.0.37.Final, 1.2.8.Final
>
>
> Configuration defined ExceptionSorter, StaleConnectionChecker.
> Using an externally (from the implementation) defined "," separated list.
> Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
> ie:
> set via <config-property name="FatalExceptions">10099,10100,10101</>
> set via <config-property name="StaleExceptions">10099,10100,10101</>
> Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6294) Session draining always takes maximum configured timeout
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6294?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-6294:
--------------------------------------
Needs mod_cluster-core 1.3.3.Final (unreleased) upgrade.
> Session draining always takes maximum configured timeout
> --------------------------------------------------------
>
> Key: WFLY-6294
> URL: https://issues.jboss.org/browse/WFLY-6294
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Minor
>
> The mod_cluster session drain wait is not ending as expected. mod_cluster adds a session listener to be notified of session destruction. That is fired appropriately, but when the listener is invoked, the infinispan session manager still reports the session as active. Thus, this drain loop doesn't end after the notify because it still sees the active session:
> {code}
> while ((remainingSessions > 0) && (noTimeout || (timeout > 0))) {
> ModClusterLogger.LOGGER.drainSessions(remainingSessions, context.getHost(), context);
> listener.wait(noTimeout ? 0 : timeout);
> current = System.currentTimeMillis();
> timeout = end - current;
> remainingSessions = context.getActiveSessionCount();
> }
> {code}
> Can the listeners be invoked when the session is fully removed and no longer considered active?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1451) Unify/add unwrap methods to most of AttributeDefinition classes
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1451?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1451:
------------------------------------------
This JIRA was partly sparked by a comment I made on https://github.com/wildfly/wildfly-core/pull/1470, where a newly introduced unwrap method didn't return null.
Tomaz replied mentioning that we already have some unwrap methods that don't return null, and the he'd filed this JIRA.
I think the goals of this JIRA are fine; i.e. that having unwrap functionality in other places sounds good, and that supporting null vs empty lists is good too.
I'm fine though with having existing methods retaining their current behavior (i.e. not returning null.) Really, changing that behavior should only be done with great care, as it's very likely an API break. Probably an overloaded or differently named method for the null/empty list/normal list 3 way behavior is better.
> Unify/add unwrap methods to most of AttributeDefinition classes
> ---------------------------------------------------------------
>
> Key: WFCORE-1451
> URL: https://issues.jboss.org/browse/WFCORE-1451
> Project: WildFly Core
> Issue Type: Feature Request
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> we now have unwrap method only on StringListAD and PropertiesAD. but there are handful of others that should have it to if possible.
> Thing to keep in mind is to make sure collection attributes can also return null as introduced in WFCORE-1448
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6420) 30secs delay on consumer.receive() in spite of shorter timeout
by Tomohisa igarashi (JIRA)
[ https://issues.jboss.org/browse/WFLY-6420?page=com.atlassian.jira.plugin.... ]
Tomohisa igarashi commented on WFLY-6420:
-----------------------------------------
OK you are right... I'm sorry for the confusion, client API doesn't matter. If TransportConstants.HTTP_UPGRADE_ENDPOINT_PROP_NAME is not set then delay occurs. It just reproduced if I commented out that property setting in your testcases.
> 30secs delay on consumer.receive() in spite of shorter timeout
> --------------------------------------------------------------
>
> Key: WFLY-6420
> URL: https://issues.jboss.org/browse/WFLY-6420
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Tomohisa igarashi
> Assignee: Jeff Mesnil
> Fix For: 10.1.0.Final
>
> Attachments: artemis-hornetq-client.tgz, artemis-hornetq-client.tgz, artemis-hornetq-client.tgz
>
>
> consumer.receive() is blocked 30secs even if shorter timeout is specified. Attached a maven project including testcases.
> The ArtemisStandaloneTest do same against embedded server, but this in contrast works fine. So the issue seems to happen only on WildFly via http upgrade connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months