October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12631) Server doesn't start when DNS_PING is configured

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12631?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-12631: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Server doesn't start when DNS_PING is configured > ------------------------------------------------ > > Key: WFLY-12631 > URL: https://issues.jboss.org/browse/WFLY-12631 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Jean Francois Denise > Assignee: Radoslav Husar > Priority: Blocker > > NPE at start. > The root cause is that <module name="sun.jdk"/> is missing from org.wildfly.clustering.service module. > Exception: > Caused by: java.lang.NullPointerException > at org.jgroups.protocols.dns.DNS_PING.destroy(DNS_PING.java:70) > at java.util.ArrayList.forEach(ArrayList.java:1257) > at org.jgroups.stack.ProtocolStack.destroy(ProtocolStack.java:876) > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:867) > at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:849) > at org.jgroups.JChannel.<init>(JChannel.java:155) > at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96) > Hidden exception: > Failed instantiate InitialContextFactory com.sun.jndi.dns.DnsContextFactory from classloader ModuleClassLoader for Module "org.wildfly.clustering.service" version 18.0.0.Final-SNAPSHOT from local module loader @2d3fcdbd (finder: local module finder @617c74e5 (roots: /home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules,/home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.dns.DnsContextFactory from [Module "org.wildfly.clustering.service" version 18.0.0.Final-SNAPSHOT from local module loader @2d3fcdbd (finder: local module finder @617c74e5 (roots: /home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules,/home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules/system/layers/base))]] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12631) Server doesn't start when DNS_PING is configured

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-12631: ------------------------------------------- Summary: Server doesn't start when DNS_PING is configured Key: WFLY-12631 URL: https://issues.jboss.org/browse/WFLY-12631 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Jean Francois Denise Assignee: Paul Ferraro NPE at start. The root cause is that <module name="sun.jdk"/> is missing from org.wildfly.clustering.service module. Exception: Caused by: java.lang.NullPointerException at org.jgroups.protocols.dns.DNS_PING.destroy(DNS_PING.java:70) at java.util.ArrayList.forEach(ArrayList.java:1257) at org.jgroups.stack.ProtocolStack.destroy(ProtocolStack.java:876) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:867) at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:849) at org.jgroups.JChannel.<init>(JChannel.java:155) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96) Hidden exception: Failed instantiate InitialContextFactory com.sun.jndi.dns.DnsContextFactory from classloader ModuleClassLoader for Module "org.wildfly.clustering.service" version 18.0.0.Final-SNAPSHOT from local module loader @2d3fcdbd (finder: local module finder @617c74e5 (roots: /home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules,/home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.dns.DnsContextFactory from [Module "org.wildfly.clustering.service" version 18.0.0.Final-SNAPSHOT from local module loader @2d3fcdbd (finder: local module finder @617c74e5 (roots: /home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules,/home/jdenise/workspaces/wildfly-jfdenise/build/target/wildfly-18.0.0.Final-SNAPSHOT/modules/system/layers/base))]] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4700) Add dependency on elytron-jwt

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4700: ---------------------------------------- Summary: Add dependency on elytron-jwt Key: WFCORE-4700 URL: https://issues.jboss.org/browse/WFCORE-4700 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Beta1 This is only being added to Core as this is where the remaining Elytron dependencies come in - the module will be added in WildFly with the relevant subsystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1884) Add new elytron-jwt module with SmallRye and MP JWT dependencies

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1884: ------------------------------------- Summary: Add new elytron-jwt module with SmallRye and MP JWT dependencies Key: ELY-1884 URL: https://issues.jboss.org/browse/ELY-1884 Project: WildFly Elytron Issue Type: Task Components: MicroProfile Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.0.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2387) Message from a non-member causes FD_ALL to continually suspect it

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2387: --------------------------- Fix Version/s: 4.1.6 > Message from a non-member causes FD_ALL to continually suspect it > ----------------------------------------------------------------- > > Key: JGRP-2387 > URL: https://issues.jboss.org/browse/JGRP-2387 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.1 > Reporter: Dennis Reed > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.6 > > Attachments: Test.java > > > If a FD_SOCK control message from a non-member is seen by FD_SOCK, it will start continually suspecting that node. If msg_counts_as_heartbeat=true then any message from a non-member triggers the issue. The issue is cleared on the next view change. > This does not cause any functional issues in the cluster, but can cause repeated WARN logs in some cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-223) disableHTTPRoute = true in runtime does not clean CR.status.hosts

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-223?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-223. ------------------------------ > disableHTTPRoute = true in runtime does not clean CR.status.hosts > ----------------------------------------------------------------- > > Key: WFWIP-223 > URL: https://issues.jboss.org/browse/WFWIP-223 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Reproducer: > # create CR > {code} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > generation: 1 > name: eap-cd > namespace: default > spec: > applicationImage: >- > brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4 > size: 1 > disableHTTPRoute: false > {code} > # Edit CR with disableHTTPRoute: true. I would expect Route object will be deleted. > {code} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > generation: 1 > name: eap-cd > namespace: default > spec: > applicationImage: >- > brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4 > size: 1 > disableHTTPRoute: true > {code} > # Route object eap-cd is not deleted but status.hosts is still filled > {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > creationTimestamp: '2019-10-01T17:20:34Z' > generation: 2 > name: eap-cd > namespace: mchoma > resourceVersion: '629943' > selfLink: /apis/wildfly.org/v1alpha1/namespaces/mchoma/wildflyservers/eap-cd > uid: c7535f3f-e46f-11e9-b4ad-02e6008f3048 > spec: > applicationImage: >- > image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4 > disableHTTPRoute: false > env: [] > envFrom: [] > replicas: 1 > status: > hosts: > - >- > eap-cd-route-mchoma.apps.eap-qe-cluster105.eap-qe-cluster105.fw.rhcloud.com > pods: > - name: eap-cd-0 > podIP: 10.131.0.246 > state: ACTIVE > replicas: 1 > scalingdownPods: 0 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-961) Increase quota for security_group_rule in istio-dev PSI project

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-961?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-961. --------------------------------- Resolution: Done > Increase quota for security_group_rule in istio-dev PSI project > --------------------------------------------------------------- > > Key: SWSQE-961 > URL: https://issues.jboss.org/browse/SWSQE-961 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Default quota for security_group_rule is 400. One ocp 4.2 installation creates 50 rules. > We need to ask for higher quota -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4600) Embedded Camel endpoints don't work with executable model

by Tibor Zimanyi (Jira)

Tibor Zimanyi created DROOLS-4600: ------------------------------------- Summary: Embedded Camel endpoints don't work with executable model Key: DROOLS-4600 URL: https://issues.jboss.org/browse/DROOLS-4600 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.27.0.Final Reporter: Tibor Zimanyi Assignee: Luca Molteni When having and embedded Camel endpoint it DRL, it doesn't work with executable model. Reproducer can be found here [1]. For the test to reproduce the issue, it is needed to use executable model project in the buildAll() call here [2]. [1] https://github.com/kiegroup/droolsjbpm-integration/blob/5f95febee0c081310... [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-camel/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12593) Jakarta update to Quickstarts docs

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12593?page=com.atlassian.jira.plugin... ] Eduardo Martins closed WFLY-12593. ---------------------------------- Resolution: Duplicate Issue Dupe of WFLY-12594 > Jakarta update to Quickstarts docs > ---------------------------------- > > Key: WFLY-12593 > URL: https://issues.jboss.org/browse/WFLY-12593 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Any references to Java EE, in Quickstart docs, should be updated wrt Jakarta EE. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12630) Document usage of EJB and JMS Client BOM in Quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12630?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12630: ----------------------------------- Description: Similar to WFLY-12377, all Quickstarts should explain usage of the EJB Client and JMS Client BOMs, as the proper way to manage/use the dependencies in server, assuring compatibility with it. (was: All JAXWS Quickstarts should explain usage of the JAXWS Client BOM as the proper way to manage/use the dependencies in server, assuring compatibility with it. Traditionally this kind of guidance is done along the reference to the BOM is pom.xml) > Document usage of EJB and JMS Client BOM in Quickstarts > ------------------------------------------------------- > > Key: WFLY-12630 > URL: https://issues.jboss.org/browse/WFLY-12630 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Similar to WFLY-12377, all Quickstarts should explain usage of the EJB Client and JMS Client BOMs, as the proper way to manage/use the dependencies in server, assuring compatibility with it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019