[JBoss JIRA] (SWSQE-947) Kiali Buildt With Code Coverage Fails To Deploy
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-947?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney closed SWSQE-947.
---------------------------------
Resolution: Done
> Kiali Buildt With Code Coverage Fails To Deploy
> -----------------------------------------------
>
> Key: SWSQE-947
> URL: https://issues.jboss.org/browse/SWSQE-947
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Matthew Mahoney
> Priority: Minor
> Labels: infrastructure
> Attachments: kiali-9b7f589c8-gxpf7-kiali.log
>
>
> Kiali build with Code-Coverage fails to start via OLM / Production Operators
> No issues when using quay.io/kiali-qe/kiali:latest
> Ex error:
> _
> MountVolume.SetUp failed for volume "kiali-cert" : secrets "kiali-cert-secret" not found_
> Repro:
> Deploy Service Mesh + Kiali + Jaeger operates via OLM
> Create Control Plane, using kiali build with code coverage
> kiali:
> enabled: true
> hub: quay.io/kiali-qe
> image: kiali
> tag: latest-cov
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ]
Stetson Robinson resolved DROOLS-1280.
--------------------------------------
Tester: Tibor Zimanyi
Resolution: Done
> further document state machine, thread-safety and include diagrams
> ------------------------------------------------------------------
>
> Key: DROOLS-1280
> URL: https://issues.jboss.org/browse/DROOLS-1280
> Project: Drools
> Issue Type: Enhancement
> Components: docs
> Reporter: Matteo Mortari
> Assignee: Stetson Robinson
> Priority: Minor
> Attachments: fireLoop.png, fireUntilHalt and fireAllRules.png, restHandler.png, waitAndEnter.png
>
>
> Spin-off remaining linked documentation work from [DROOLS-1272] for:
> Include docs on state machine and thread safety
> Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual.
> [From [~stetson.robinson]]
> Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety."
> Attached the state machine diagrams from Mark for future ref, if needed.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ]
Stetson Robinson updated DROOLS-1280:
-------------------------------------
Docs QE Status: VERIFIED (was: NEW)
> further document state machine, thread-safety and include diagrams
> ------------------------------------------------------------------
>
> Key: DROOLS-1280
> URL: https://issues.jboss.org/browse/DROOLS-1280
> Project: Drools
> Issue Type: Enhancement
> Components: docs
> Reporter: Matteo Mortari
> Assignee: Stetson Robinson
> Priority: Minor
> Attachments: fireLoop.png, fireUntilHalt and fireAllRules.png, restHandler.png, waitAndEnter.png
>
>
> Spin-off remaining linked documentation work from [DROOLS-1272] for:
> Include docs on state machine and thread safety
> Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual.
> [From [~stetson.robinson]]
> Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety."
> Attached the state machine diagrams from Mark for future ref, if needed.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ]
Stetson Robinson updated DROOLS-1280:
-------------------------------------
QE Status: VERIFIED (was: NEW)
> further document state machine, thread-safety and include diagrams
> ------------------------------------------------------------------
>
> Key: DROOLS-1280
> URL: https://issues.jboss.org/browse/DROOLS-1280
> Project: Drools
> Issue Type: Enhancement
> Components: docs
> Reporter: Matteo Mortari
> Assignee: Stetson Robinson
> Priority: Minor
> Attachments: fireLoop.png, fireUntilHalt and fireAllRules.png, restHandler.png, waitAndEnter.png
>
>
> Spin-off remaining linked documentation work from [DROOLS-1272] for:
> Include docs on state machine and thread safety
> Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual.
> [From [~stetson.robinson]]
> Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety."
> Attached the state machine diagrams from Mark for future ref, if needed.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-1280:
------------------------------------------
Incorporated in BXMSDOC-4468, with the exception of the diagrams, as noted above. Resolving.
> further document state machine, thread-safety and include diagrams
> ------------------------------------------------------------------
>
> Key: DROOLS-1280
> URL: https://issues.jboss.org/browse/DROOLS-1280
> Project: Drools
> Issue Type: Enhancement
> Components: docs
> Reporter: Matteo Mortari
> Assignee: Stetson Robinson
> Priority: Minor
> Attachments: fireLoop.png, fireUntilHalt and fireAllRules.png, restHandler.png, waitAndEnter.png
>
>
> Spin-off remaining linked documentation work from [DROOLS-1272] for:
> Include docs on state machine and thread safety
> Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual.
> [From [~stetson.robinson]]
> Confirmed with Mark and Mario that the state machine diagram does not belong in the docs, at least for now. Note from Mark in chat: "all they need to know is 1) there three interacting threads: user, timer and engine 2) we have a state machine based algorithm to efficient co-ordinate those threads and ensure thread safety."
> Attached the state machine diagrams from Mark for future ref, if needed.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (JGRP-2382) Jgroup 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:
--------------------------------
* Which of the 2 configurations do you use?
* Can you reproduce this with a simple JGroups test?
* Do you have a heap dump?
> Jgroup 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
>
> 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.5#713005)
6 years, 10 months