October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1872) elytron-tool.sh usage with symbolic links

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1872?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1872: ---------------------------------- Fix Version/s: 1.6.5.CR1 1.10.4.CR1 > elytron-tool.sh usage with symbolic links > ----------------------------------------- > > Key: ELY-1872 > URL: https://issues.jboss.org/browse/ELY-1872 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Affects Versions: 2.0.0.Alpha4 > Environment: Red Hat JBoss Enterprise Application Platform (7.2.3) > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > Fix For: 1.6.5.CR1, 1.10.4.CR1 > > > It looks like elytron-tool.sh doesn't work well with symbolic links. > The soft link becomes a credential store - in a "standard" file - with the newly added alias but the original credential store will not be updated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-225) Environment variable to configure the initial metaspace size - need to update standalone.conf to bring CLOUD-3270 changes

by Jan Blizňák (Jira)

Jan Blizňák created WFWIP-225: --------------------------------- Summary: Environment variable to configure the initial metaspace size - need to update standalone.conf to bring CLOUD-3270 changes Key: WFWIP-225 URL: https://issues.jboss.org/browse/WFWIP-225 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Jan Blizňák Assignee: Jean Francois Denise In CLOUD-3270, some changes were made to be able to override jvm metaspace value but current image docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... doesn't have it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

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

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-223?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFWIP-223: ------------------------------ Labels: operator (was: ) > 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)

4 years, 9 months

1
0
0 / 0

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

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-223?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-223: ----------------------------------- tracked in upstream by https://github.com/wildfly/wildfly-operator/issues/94 > 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)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-224) Redundant template eap-cd-chained-build-s2i.json

by Nikoleta Ziakova (Jira)

Nikoleta Ziakova created WFWIP-224: -------------------------------------- Summary: Redundant template eap-cd-chained-build-s2i.json Key: WFWIP-224 URL: https://issues.jboss.org/browse/WFWIP-224 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Nikoleta Ziakova Assignee: Jean Francois Denise The [chained-build|https://github.com/wildfly/temp-openshift-image/blob/EAP7-1...] template was added with old feature design when chained build was not possible to be added to the existing templates. Now the existing templates contain chained build so this new template has become redundant. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-192: ----------------------------------- Done in the eap-operator-packaging PR https://github.com/jbossas/eap-operator-packaging/pull/5 [~mchoma] I let you close the issue if the solutions satisfies you. > Sync eap CRD with wildfly CRD > ----------------------------- > > Key: WFWIP-192 > URL: https://issues.jboss.org/browse/WFWIP-192 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > Comparing wildfly and eap CRD revealed differences > {code} > wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd > wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd > diff wildfly_operator_crd eap_operator_crd > {code} > {code} > 36,37d35 > < disableHTTPRoute: > < type: boolean > 50,53d47 > < sessionAffinity: > < description: SessionAffinity defines if connections from the same client > < ip are passed to the same WildFlyServer instance/pod each time > < type: boolean > 79,82d72 > < hosts: > < items: > < type: string > < type: array > 94a85,86 > > required: > > - pods > {code} > Please sync so we can test against. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2382) JGroups version 4.0.13.Final.jar is causing memory leaks

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2382?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2382: -------------------------------- As I said before, removing UNICAST3 is a bad idea and will break your application unless it * tolerates unordered messages * tolerates missing messages > JGroups version 4.0.13.Final.jar is causing memory leaks > -------------------------------------------------------- > > Key: JGRP-2382 > URL: https://issues.jboss.org/browse/JGRP-2382 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.13 > Environment: AIX machine 7.1 with JDK 1.8 > Reporter: Rashmi Acharya > Assignee: Bela Ban > Priority: Major > Attachments: dumps_TEST_node1_20190918_after_3_hours.zip, dumps_TEST_node1_20190918_right_after_restart.zip, dumps_TEST_node2_20190918_after_3_hours.zip, dumps_TEST_node2_20190918_right_after_restart.zip > > > We are observing a constant memory growth and leak with JGroup version 4.0.13 .. > One of our customer is having two node cluster environment and in one node we are observing org.Group.Messages which contain org.groups.Header and org.groups.Stack.ipAddress objects.. these are not getting cleared from memory.. > We dont see any exception related to Jgroups from logs and but it is causing a gradual emory growth and OOM. > Here is the Jgroups cluster configuration we have: > dynamic.cluster.property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT2;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000" /> > <FD_ALL timeout="20000" interval="15000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48" /> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000"/> > <pbcast.GMS print_local_addr="true" join_timeout="15000" /> > </config> > ================================= > dynamic.cluster.distribution_property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_port="&MULTICAST_NODE_PORT1;" /> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > </config> > ================================ > dynamic.cluster.lock.protocolStack > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT3;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_ALL timeout="20000" interval="5000"/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3 /> <pbcast.STABLE desired_avg_gossip="20000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > <FRAG2 frag_size="8096"/> > <CENTRAL_LOCK2/> > </config> -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-172) not possible to change volume mount path in wildfly operator

by Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFWIP-172?page=com.atlassian.jira.plugin.... ] Martin Simka closed WFWIP-172. ------------------------------ closing, with productised operator path is correct > not possible to change volume mount path in wildfly operator > ------------------------------------------------------------ > > Key: WFWIP-172 > URL: https://issues.jboss.org/browse/WFWIP-172 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > WildFly Operator > It looks like (I'm not much familiar with go) that volume mount path is [hard coded|https://github.com/wildfly/wildfly-operator/blob/master/pkg/control...] and cannot be changed. > EAP will need {{/opt/eap/standalone/data}} > Also [documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...] says it is {{/opt/jboss/wildfly/standalone/data}} but that is different from code's {{/wildfly/standalone/data}}. > Upstream issue: https://github.com/wildfly/wildfly-operator/issues/55 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12626) Upgrade RESTEasy to 3.10.0.Final

by Ivo Studensky (Jira)

Ivo Studensky created WFLY-12626: ------------------------------------ Summary: Upgrade RESTEasy to 3.10.0.Final Key: WFLY-12626 URL: https://issues.jboss.org/browse/WFLY-12626 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Ivo Studensky Assignee: Alessio Soldano -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12575) Upgrade RESTEasy to 3.10.0.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12575?page=com.atlassian.jira.plugin... ] Ivo Studensky updated WFLY-12575: --------------------------------- Labels: downstream_dependency (was: ) > Upgrade RESTEasy to 3.10.0.Final > -------------------------------- > > Key: WFLY-12575 > URL: https://issues.jboss.org/browse/WFLY-12575 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019