May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1745) The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1745?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1745: ---------------------------------- Fix Version/s: 1.9.0.CR6 (was: 1.9.0.CR5) > The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1745 > URL: https://issues.jboss.org/browse/ELY-1745 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Justin Cook > Priority: Major > Fix For: 1.9.0.CR6 > > > The NPE is due to the following code: - > {noformat} > } else if (callback instanceof AvailableRealmsCallback) { > Collection<String> names = stateRef.get().getMechanismConfiguration().getMechanismRealmNames(); > if (log.isTraceEnabled()) { > log.tracef("Handling AvailableRealmsCallback: realms = [%s]", String.join(", ", names)); > } > if (! names.isEmpty()) { > ((AvailableRealmsCallback) callback).setRealmNames(names.toArray(new String[names.size()])); > } > handleOne(callbacks, idx + 1); > {noformat} > If mechanism configuration is mandatory this should report an appropriate error, if not it should fallback to specifying an empty list. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1803) Release WildFly Elytron 1.9.0.CR5

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1803?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1803. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.9.0.CR5 > --------------------------------- > > Key: ELY-1803 > URL: https://issues.jboss.org/browse/ELY-1803 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR5 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4464) Upgrade WildFly Elytron to 1.9.0.CR5

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4464: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.9.0.CR5 Key: WFCORE-4464 URL: https://issues.jboss.org/browse/WFCORE-4464 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.Beta5 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1803) Release WildFly Elytron 1.9.0.CR5

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1803: ------------------------------------- Summary: Release WildFly Elytron 1.9.0.CR5 Key: ELY-1803 URL: https://issues.jboss.org/browse/ELY-1803 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR5 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3991) java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader

by Anuradha Prabhala (Jira)

Anuradha Prabhala created DROOLS-3991: ----------------------------------------- Summary: java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader Key: DROOLS-3991 URL: https://issues.jboss.org/browse/DROOLS-3991 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 7.15.0.Final Reporter: Anuradha Prabhala Assignee: Maciej Swiderski I deployed 2 war files in wildfly 14. Both of them are drools projects that are trying to execute some rules. The problem is that only one of the war file is able to execute drools rule. The other fails with the below Internal Server Error: Caused by: java.lang.IllegalStateException: There's already another KieContainer created from a different ClassLoader at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:107) at org.drools.compiler.kie.builder.impl.KieServicesImpl.getKieClasspathContainer(KieServicesImpl.java:79) at org.drools.examples.helloworld.HelloWorldExample.drools(HelloWorldExample.java:49) at com.sample.rest.MessageRestService.Testdrools(MessageRestService.java:26) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4463) Add heartbeat, read/write timeout for remoting endpoint configuration

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4463?page=com.atlassian.jira.plugi... ] Teresa Miyar Gil updated WFCORE-4463: ------------------------------------- Affects Version/s: 6.0.2.Final (was: 9.0.0.Beta4) > Add heartbeat, read/write timeout for remoting endpoint configuration > --------------------------------------------------------------------- > > Key: WFCORE-4463 > URL: https://issues.jboss.org/browse/WFCORE-4463 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 6.0.2.Final > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4463) Add heartbeat, read/write timeout for remoting endpoint configuration

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4463?page=com.atlassian.jira.plugi... ] Teresa Miyar Gil updated WFCORE-4463: ------------------------------------- Affects Version/s: 9.0.0.Beta4 > Add heartbeat, read/write timeout for remoting endpoint configuration > --------------------------------------------------------------------- > > Key: WFCORE-4463 > URL: https://issues.jboss.org/browse/WFCORE-4463 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 9.0.0.Beta4 > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4463) Add heartbeat, read/write timeout for remoting endpoint configuration

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4463?page=com.atlassian.jira.plugi... ] Teresa Miyar Gil updated WFCORE-4463: ------------------------------------- Summary: Add heartbeat, read/write timeout for remoting endpoint configuration (was: Add heartbeat, read/write timeout for removing endpoint configuration) > Add heartbeat, read/write timeout for remoting endpoint configuration > --------------------------------------------------------------------- > > Key: WFCORE-4463 > URL: https://issues.jboss.org/browse/WFCORE-4463 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4463) Add heartbeat, read/write timeout for removing endpoint configuration

by Teresa Miyar Gil (Jira)

Teresa Miyar Gil created WFCORE-4463: ---------------------------------------- Summary: Add heartbeat, read/write timeout for removing endpoint configuration Key: WFCORE-4463 URL: https://issues.jboss.org/browse/WFCORE-4463 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Teresa Miyar Gil Assignee: Teresa Miyar Gil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2343) Change in IPv4 versus IPv6 picking algorithm

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2343?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2343 at 5/8/19 3:54 AM: -------------------------------------------------------- This is the new algorithm: h4. Only IPv4 stack is available * IPv4 addresses are created by default (e.g. by {{InetAddress.getByName()}}, or {{site_local}}) * When an IPv6 address is defined in a configuration, an exception is thrown and the stack will not start h4. Only IPv6 stack is available * IPv6 addresses are created by default * When an IPv4 address is created, convert it to an IPv6-mapped address (default behavior) h4. Both IPv4 and IPv6 stacks are available (dual stack) * If {{java.net.preferIPv4Stack=true}} and {{java.net.preferIPv6Addresses=false}}: ** Assign IPv4 addresses by default ** When an IPv6 address is encountered, throw an exception and don't start the stack * If {{java.net.preferIPv6Addresses=true}} and {{java.net.preferIPv4Stack=false}}: ** Assign IPv6 addresses by default ** When an IPv4 address is encountered, convert it to an IPv6-mapped address (default behavior) * Both {{java.net.preferIPv4Stack}} and {{java.net.preferIPv6Addresses}} are set, or none are set ** The JDK's preference is to assign IPv4 addresses ** If we have a single IPv6 address (dotted-decimal or symbolic name resolved to IPv6) in the configuration -> Assign IPv6 addresses ** Otherwise -> use IPv4 addresses For dual stacks (both IPv4 and IPv6 stack is available in the JDK), these changes allow JGroups to run different configurations in the same JVM, e.g. one channel joining an IPv4 cluster, and another one joining an IPv6 cluster. was (Author: belaban): This is the new algorithm: h4. Only IPv4 stack is available * IPv4 addresses are created by default (e.g. by {{InetAddress.getByName()}}, or {{site_local}}) * When an IPv6 address is defined in a configuration, an exception is thrown and the stack will not start h4. Only IPv6 stack is available * IPv6 addresses are created by default * When an IPv4 address is created, convert it to an IPv6-mapped address (default behavior) h4. Both IPv4 and IPv6 stacks are available (dual stack) * If {{java.net.preferIPv4Stack=true}}: ** Assign IPv4 addresses by default ** When an IPv6 address is encountered, throw an exception and don't start the stack * If {{java.net.preferIPv6Addresses=true}}: ** Assign IPv6 addresses by default ** When an IPv4 address is encountered, convert it to an IPv6-mapped address (default behavior) * Both {{java.net.preferIPv4Stack}} and {{java.net.preferIPv6Addresses}} are set, or none are set ** What's the JDK's preference? (check!) Try to implement the same preference! ** If we have a single IPv6 address (dotted-decimal or symbolic name resolved to IPv6) in the configuration -> Assign IPv6 addresses ** Otherwise -> use IPv4 addresses For dual stacks (both IPv4 and IPv6 stack is available in the JDK), these changes allow JGroups to run different configurations in the same JVM, e.g. one channel joining an IPv4 cluster, and another one joining an IPv6 cluster. > Change in IPv4 versus IPv6 picking algorithm > -------------------------------------------- > > Key: JGRP-2343 > URL: https://issues.jboss.org/browse/JGRP-2343 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > When https://issues.jboss.org/browse/JGRP-2305 was implemented, IPv4 was favored unless {{java.net.preferIPv6Addresses}} was set. > However, this makes the following case fail: no {{java.net.preferXXX}} option is set and the configuration contains one or more IPv6 addresses, e.g. {{UDP bind_addr="::1"}}. > This will fail, as the new algorithm sets the stack type as IPv4 (it works when {{java.net.preferIPv6Addresses}} is set). > Change: > * Look at all IP addresses in a configuration > * If all addresses are IPv6 and the stack type is IPv4 (and IPv6 is available) -> switch to IPv6 as stack type > * If all addresses are IPv4 and the stack type is IPv6 (and IPv4 is available) -> switch to IPv4 stack type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2019