[JBoss JIRA] (JGRP-2502) If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace
by Filippe Spolti (Jira)
Filippe Spolti created JGRP-2502:
------------------------------------
Summary: If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace
Key: JGRP-2502
URL: https://issues.redhat.com/browse/JGRP-2502
Project: JGroups
Issue Type: Bug
Affects Versions: 5.0.4
Reporter: Filippe Spolti
Assignee: Bela Ban
If no namespace is set it defaults to the "default" ocp namespace which will case the warn as described in the log message below:
{code:java}
WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-9,ee,hdm78-kieserver-1-nggcf) failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:937#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@69991c01] for cluster [ee], namespace [default], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/default/pods]]
{code}
IMHO the default namespace should not be used in this case since this namespace should not be used to deploy applications.
If the namespace is not set it means that we do not want to enable the clustering feature, as the namespace is set if the namespace is not set, this condition [1] is not satisfied and the configuration will proceed.
Another problem found in the tests is that, if we do set the KUBERNETES_NAMESPACE with no value, it will detect that the env has an value and will try to use a blank namespace:
{code:java}
failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1 , headers={Authorization=#MASKED:874#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@17978314] for cluster [ee], namespace [], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/pods ]]
{code}
[1] - https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java#L145
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13790) Memory leak caused by org.eclipse.yasson.internal.JsonBinding
by r searls (Jira)
[ https://issues.redhat.com/browse/WFLY-13790?page=com.atlassian.jira.plugi... ]
r searls commented on WFLY-13790:
---------------------------------
A proposed change can be found here
[https://github.com/rsearls/Resteasy/tree/WFLY-13790-Memory-leak-JsonBindi...]
The memory analyser I am using does not present the same information you have listed.
Ahcene,
Please test this change and confirm if it resolves the issue.
> Memory leak caused by org.eclipse.yasson.internal.JsonBinding
> -------------------------------------------------------------
>
> Key: WFLY-13790
> URL: https://issues.redhat.com/browse/WFLY-13790
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 20.0.1.Final
> Reporter: Ahcene Kessal
> Assignee: r searls
> Priority: Major
>
> org.eclipse.yasson.internal.JsonBinding keeps a reference on an enum after the war is undeployed which results in a classloader leak.
> 1- Deploy the following application:
>
> {code:java}
> package au.com.spatiumxl.model;
> public class Book {
> public enum Status { READ, UNREAD }
> private String title;
> private Book.Status status;
> public Book(String title) {
> this.title = title;
> this.status = Book.Status.UNREAD;
> }
> public String getTitle() {
> return title;
> }
> public Book.Status getStatus() {
> return status;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.ejb;
> [...]
> import au.com.spatiumxl.model.Book;
> @Stateless
> @LocalBean
> public class BookService {
> public List<Book> getBooks() {
> List<Book> books = new ArrayList<>();
> books.add(new Book("title1"));
> return books;
> }
> }
> {code}
>
> {code:java}
> package au.com.spatiumxl.rest;
> [...]
> import au.com.spatiumxl.ejb.BookService;
> import au.com.spatiumxl.model.Book;
> @RequestScoped
> @Path("")public
> class BookEndPoint {
> @Inject BookService bookService;
> @GET @Path("/get-books")
> @Produces("application/json")
> public List<Book> getBooks() {
> return bookService.getBooks();
> }
> }
> {code}
>
> 2- On the browser go to: http://<host>/<context-root>/.../get-books
> 3- Undeploy the war
> 4- The memory analyser shows:
> {code:java}
> java.lang.Thread
> org.jboss.modules.ModuleClassLoader
> org.jboss.modules.Module
> org.jboss.modules.LocalModuleLoader
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.jboss.modules.ModuleLoader$FutureModule
> org.jboss.modules.Module
> org.jboss.modules.ModuleClassLoader
> java.util.Vector
> java.lang.Object[]
> org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider
> org.eclipse.yasson.internal.JsonBinding
> org.eclipse.yasson.internal.JsonbContext
> org.eclipse.yasson.internal.MappingContext
> java.util.concurrent.ConcurrentHashMap
> java.util.concurrent.ConcurrentHashMap$Node[]
> java.util.concurrent.ConcurrentHashMap$Node
> org.eclipse.yasson.internal.model.ClassModel
> org.eclipse.yasson.internal.model.PropertyModel[]
> org.eclipse.yasson.internal.model.PropertyModel
> au.com.spatiumxl.model.Book$Status
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13655) LOG INFO level message if the Hibernate second level cache is enabled
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13655?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13655:
------------------------------------
Fix Version/s: 21.0.0.Final
(was: 21.0.0.Beta1)
> LOG INFO level message if the Hibernate second level cache is enabled
> ---------------------------------------------------------------------
>
> Key: WFLY-13655
> URL: https://issues.redhat.com/browse/WFLY-13655
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Minor
> Fix For: 21.0.0.Final
>
>
> The idea is to log at INFO level if the Hibernate second level cache is to be enabled by org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator. Note that org.hibernate.cache.internal.RegionFactoryInitiator#resolveRegionFactory still needs to be able to create the second level cache.
> Update WildFlyCustomRegionFactoryInitiator#resolveRegionFactory to log at INFO level the "WildFlyCustomRegionFactoryInitiator#resolveRegionFactory will create second level cache %s" message.
> This message will only be logged during application deployment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13305) Bootable jar for Wildfly
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13305?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13305:
------------------------------------
Fix Version/s: 21.0.0.Final
(was: 21.0.0.Beta1)
> Bootable jar for Wildfly
> ------------------------
>
> Key: WFLY-13305
> URL: https://issues.redhat.com/browse/WFLY-13305
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Reporter: Jean Francois Denise
> Assignee: Jean Francois Denise
> Priority: Major
> Fix For: 21.0.0.Final
>
>
> Provides support for running MicroService apps without the need archive it as a deployment and without the need to deploy it in a running application server.
> Provides support for ability to run MicroService apps on the Operating Systems command line as a bootable jar.
> Provides support for developing and running the app. "java -jar app.jar" and maven command line interface.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12881:
------------------------------------
Fix Version/s: 21.0.0.Final
(was: 21.0.0.Beta1)
> Cannot customize split behavior and merge policy for Infinispan partition handling
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12881
> URL: https://issues.redhat.com/browse/WFLY-12881
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 18.0.1.Final, 19.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 21.0.0.Final
>
>
> Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs.
> Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13659) Fix modules with dependency on Legacy Security Subsystem or PicketBox
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13659?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13659:
------------------------------------
Fix Version/s: 21.0.0.Final
(was: 21.0.0.Beta1)
> Fix modules with dependency on Legacy Security Subsystem or PicketBox
> ---------------------------------------------------------------------
>
> Key: WFLY-13659
> URL: https://issues.redhat.com/browse/WFLY-13659
> Project: WildFly
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: EE9
> Fix For: 21.0.0.Final
>
>
> Various subsystems have dependencies on the legacy security subsystem, these need to be verified to make sure they are really required or adjusted to make optional.
> *org.jboss.as.security*
> {code}
> ./system/layers/base/org/wildfly/extension/request-controller/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/wildfly/extension/io/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/wildfly/extension/elytron/main/module.xml: <module name="org.jboss.as.security-integration" optional="true" services="import"/>
> ./system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/wildfly/extension/picketlink/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/wildfly/extension/messaging-activemq/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/apache/activemq/artemis/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/vault-tool/main/module.xml: <main-class name="org.jboss.as.security.vault.VaultTool"/>
> ./system/layers/base/org/jboss/as/vault-tool/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/webservices/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/remoting/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> ./system/layers/base/org/jboss/as/appclient/main/module.xml: <module name="org.jboss.as.security"/>
> ./system/layers/base/org/jboss/as/server/main/module.xml: <module name="org.jboss.as.security" optional="true" services="import"/>
> ./system/layers/base/org/jboss/as/weld/common/main/module.xml: <module name="org.jboss.as.security" optional="true"/>
> {code}
> *org.picketbox*
> {code}
> ./system/layers/base/org/wildfly/extension/io/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/wildfly/extension/batch/jberet/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/wildfly/extension/picketlink/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/wildfly/extension/messaging-activemq/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/wildfly/iiop-openjdk/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/apache/activemq/artemis/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/picketlink/federation/bindings/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/picketlink/federation/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/webservices/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/remoting/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/appclient/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/security-api/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/server/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/weld/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/domain-management/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/cli/main/module.xml: <module name="org.picketbox" optional="true"/>
> ./system/layers/base/org/jboss/as/security/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/as/security-integration/main/module.xml: <module name="org.picketbox">
> ./system/layers/base/org/jboss/ws/cxf/jbossws-cxf-client/main/module.xml: <module name="org.picketbox" export="true"/>
> ./system/layers/base/org/jboss/ws/cxf/jbossws-cxf-server/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/ws/jaxws-client/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/ironjacamar/impl/main/module.xml: <module name="org.picketbox"/>
> ./system/layers/base/org/jboss/security/negotiation/main/module.xml: <module name="org.picketbox"/>
> {code}
> The optional dependencies are probably Ok but the non-optional dependencies mean these will pull in the modules we do not want when these subsystems are provisioned.
> As there are quite a few affected modules I will likely group these into related areas and create sub tasks to track the individual problems to be addressed.
> Ignoring the optional dependencies the list of modules to target becomes:
> * org.apache.activemq.artemis
> * org.jboss.as.appclient
> * org.jboss.as.connector
> * org.jboss.as.ejb3
> * org.jboss.as.webservices
> * -org.jboss.as.weld-
> * org.jboss.ironjacamar.impl
> * org.jboss.ws.cxf.jbossws-cxf-client
> * org.jboss.ws.cxf.jbossws-cxf-server
> * org.jboss.ws.jaxws-client
> * -org.wildfly.extension.batch.jberet-
> * org.wildfly.extension.messaging-activemq
> * org.wildfly.iiop-openjdk
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months