[JBoss JIRA] (JGRP-592) Pluggable policy for picking coordinator
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-592?page=com.atlassian.jira.plugin.s... ]
Bela Ban commented on JGRP-592:
-------------------------------
Implementing such a policy would be hard:
* The assumption that the first member of a view is the coordinator is a tenet of JGroups as had been in place for a long time
* Therefore, there is a lot of code which depends on this. Locating that code and changing it would be tedious
* Also, a lot of third party code depends on this as well
If we change this, the policy would therefore need to handle both the regular view change and a merge view change, but in both cases, the coordinator needs to be the first of the new view.
> Pluggable policy for picking coordinator
> ----------------------------------------
>
> Key: JGRP-592
> URL: https://issues.jboss.org/browse/JGRP-592
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4
>
>
> Make policy to pick coordinator pluggable. Pick new coordinator after existing coordinator crashes by calling this policy.
> Default policy is to pick the next in line.
> Other policies could pick the next in line from a set of pinned coordinator, so certain members can never become coordinators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (WFLY-1774) Determine if Jandex can be used to optimize CDI + Bean Validation integration for method validation
by Farah Juma (JIRA)
Farah Juma created WFLY-1774:
--------------------------------
Summary: Determine if Jandex can be used to optimize CDI + Bean Validation integration for method validation
Key: WFLY-1774
URL: https://issues.jboss.org/browse/WFLY-1774
Project: WildFly
Issue Type: Feature Request
Affects Versions: 8.0.0.Alpha3
Reporter: Farah Juma
Assignee: Farah Juma
For CDI + Bean Validation integration for method validation, we're making use of the Hibernate Validator CDI portable extension. We can try to optimize this portable extension by making use of the Jandex index. In particular, we can:
1) Determine if Jandex can be used for subtype retrieval to avoid having to specify @ValidateOnExecution(IMPLICIT)
2) Determine if Jandex can be used to speed up constraint metadata retrieval
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (WFLY-1769) 2 config updates for OpenJDK 8
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-1769?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-1769:
-----------------------------------
There are three different ways you can do the git remote.
First, you can use "git://github.com/org/repo.git" which I assume is what was blocked. Next you can use SSH via "git@github.com:org/repo.git", so if your firewall allows outbound SSH you should be OK. Finally, you can use HTTPS via "https://github.com/org/repo.git" which most firewalls should allow.
> 2 config updates for OpenJDK 8
> ------------------------------
>
> Key: WFLY-1769
> URL: https://issues.jboss.org/browse/WFLY-1769
> Project: WildFly
> Issue Type: Feature Request
> Components: EE
> Reporter: Juergen Zimmermann
> Assignee: David Lloyd
>
> JDK 8 uses the Javascript Engine Nashorn instead of Rhino in JDK 7 (and 6).
> Therefore, 2 additional config lines are required to support JDK 8 in addition to JDK 7:
> After making the following 2 config updates for bean validation my web app is running with WildFly and OpenJDK 8:
> 1) In modules/system/layers/base/sun/jdk/main/module.xml: add the following <path> declaration as the 2nd subtag inside <paths>, i.e. after the "com/sun/script/javascript" for JDK 7:
> {code}
> <path name="jdk/nashorn/api/scripting"/>
> {code}
> 2) In modules/system/layers/base/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory add the following line as the 2nd service, i.e. as a alternative service for JDK 7:
> {code}
> jdk.nashorn.api.scripting.NashornScriptEngineFactory
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (WFLY-1773) NPE in Host.unregisterDeployment
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1773?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-1773:
-----------------------------------
That would cause NPE only if deployment passed in would be null.
You can reproduce this always?
> NPE in Host.unregisterDeployment
> --------------------------------
>
> Key: WFLY-1773
> URL: https://issues.jboss.org/browse/WFLY-1773
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Thomas Diesler
> Assignee: Tomaz Cerar
>
> {code}
> 15:37:13,687 INFO [org.jboss.osgi.framework] (pool-1-thread-3) JBOSGI011003: Bundle stopped: bundle-c.wab:0.0.0
> 15:37:13,689 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./bundle-c: java.lang.NullPointerException
> at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:130)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (WFLY-1773) NPE in Host.unregisterDeployment
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1773?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1773:
------------------------------
Affects Version/s: 8.0.0.Alpha3
> NPE in Host.unregisterDeployment
> --------------------------------
>
> Key: WFLY-1773
> URL: https://issues.jboss.org/browse/WFLY-1773
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Thomas Diesler
> Assignee: Tomaz Cerar
>
> {code}
> 15:37:13,687 INFO [org.jboss.osgi.framework] (pool-1-thread-3) JBOSGI011003: Bundle stopped: bundle-c.wab:0.0.0
> 15:37:13,689 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./bundle-c: java.lang.NullPointerException
> at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:130)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (WFLY-1773) NPE in Host.unregisterDeployment
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1773?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-1773:
---------------------------------
Assignee: Tomaz Cerar (was: Stuart Douglas)
> NPE in Host.unregisterDeployment
> --------------------------------
>
> Key: WFLY-1773
> URL: https://issues.jboss.org/browse/WFLY-1773
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Thomas Diesler
> Assignee: Tomaz Cerar
>
> {code}
> 15:37:13,687 INFO [org.jboss.osgi.framework] (pool-1-thread-3) JBOSGI011003: Bundle stopped: bundle-c.wab:0.0.0
> 15:37:13,689 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./bundle-c: java.lang.NullPointerException
> at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:130)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months