April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-118) ElasticSearch deployment fails on B11 cluster with out of memory errors

by Kevin Earls (JIRA)

Kevin Earls created SWSQE-118: --------------------------------- Summary: ElasticSearch deployment fails on B11 cluster with out of memory errors Key: SWSQE-118 URL: https://issues.jboss.org/browse/SWSQE-118 Project: Kiali QE Issue Type: QE Task Reporter: Kevin Earls Assignee: Michael Foley Priority: Blocker As part of KIALI-336 I'm trying to run Jaeger with ElasticSearch as its storage, using this Jenkinsfile: https://github.com/jaegertracing/jaeger-performance/blob/master/standalon... The test is setup on B11 in the jaeger-test project https://jenkins-jaeger-test.openshift4.jonqe.lab.eng.bos.redhat.com/job/J... I'm running into a few problems here, which may or may not be related. 1. Even though I've run this test twice, Jenkins does not have any logs. 2. ElasticSearch will not start up. I don't have the exact log of the problem yet, as it keeps trying to redeploy, but I have seen "Oom" errors messages, which I assume means out of memory. I will attach logs if I can catch it in this exact state. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9943) Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-9943?page=com.atlassian.jira.plugin.... ] Miroslav Novak closed WFLY-9943. -------------------------------- Resolution: Cannot Reproduce Currently this issue cannot be reproduced. Closing it. > Sometimes WF process does not exit on RHEL 6 (32/64 bit) and IBM JDK 8 > ---------------------------------------------------------------------- > > Key: WFLY-9943 > URL: https://issues.jboss.org/browse/WFLY-9943 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 12.0.0.Final > Environment: RHEL 6 32/64 bit > IBM SDK 8.0.5.10: > {code}java version "1.8.0_161 > Java(TM) SE Runtime Environment (build 8.0.5.10 - pxi3280sr5fp10-20180214_01(SR5 FP10)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux x86-32 20180208_378436 (JIT enabled, AOT enabled) > OpenJ9 - 39bb844 > OMR - c04ccb2 > IBM - 2321a81) > JCL - 20180209_01 based on Oracle jdk8u161-b12 > {code} > Reporter: Miroslav Novak > Assignee: Jason Greene > Attachments: pstack.txt > > > Sometimes happens that WF12 process does not exit when :shutdown CLI operation called and hangs indefinitely. This happens only RHEL 6 (32/64 bit) with IBM SDK8. > Calling kill -3 does not create any javacore dump and only output could be gathered from pstack (attached). It indicates that JVM shutdown thread is hanging on: > {code} > Thread 25 (Thread 0xb7792b70 (LWP 25507)): > #0 0x00bd4424 in __kernel_vsyscall () > #1 0x00b2243c in pthread_cond_wait@(a)GLIBC_2.3.2 () from /lib/libpthread.so.0 > #2 0x004f8b1f in monitor_wait_original () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so > #3 0x004f9957 in omrthread_monitor_wait () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9thr29.so > #4 0x0033e217 in protectedDestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so > #5 0x0042cf6e in omrsig_protect () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9prt29.so > #6 0x0033db93 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libj9vm29.so > #7 0x00815999 in DestroyJavaVM () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/lib/i386/default/libjvm.so > #8 0x00528649 in JavaMain () from /qa/tools/opt/ibm-java-i386-sdk-8.0-5.10/jre/bin/../lib/i386/jli/libjli.so > #9 0x00b1ebc9 in start_thread () from /lib/libpthread.so.0 > #10 0x001fc04e in clone () from /lib/libc.so.6 > {code} > There are other 24 threads which might be blocking this thread or a dead lock. This appears to be problem in IBM SDK 8 in combination RHEL 6 GLIBC_2.3.2 library. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2452) Project Editor: It should be possible to undefault a kbase and ksession

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2452: ------------------------------------ Summary: Project Editor: It should be possible to undefault a kbase and ksession Key: DROOLS-2452 URL: https://issues.jboss.org/browse/DROOLS-2452 Project: Drools Issue Type: Bug Components: build Reporter: Toni Rikkola Assignee: Ant Stephenson There does not have to be a default kbase or ksession. It is possible to create a configuration like this, but it you happen to set a default it is impossible to undefault it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2342) Update Kie Navigator to the new git/rest structure

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2342?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on DROOLS-2342: ------------------------------------------- Thanks [~tfernand] for the pull request. Note that before adding this bug fix in the Devstudio Integration Stack, we need to implement a backward compatibility with the older versions. > Update Kie Navigator to the new git/rest structure > -------------------------------------------------- > > Key: DROOLS-2342 > URL: https://issues.jboss.org/browse/DROOLS-2342 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.5.0.Final > Environment: 7.7.0-SNAPSHOT > Reporter: Tomas David > Assignee: Tiago Bento > Fix For: 7.8.0.Final > > > Drools eclipse plugin contains Kie Navigator tool which uses git structure and rest calls to connect to kie-wb. According to changes made in kie-wb 7.7.0 the tooling should be updated. > The rest api and the git structure changed. and the kie navigator doesn't work. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6412) Timer fails if transaction isolation set to SERIALIZABLE on Oracle 11g

by Maxim Karavaev (JIRA)

[ https://issues.jboss.org/browse/WFLY-6412?page=com.atlassian.jira.plugin.... ] Maxim Karavaev commented on WFLY-6412: -------------------------------------- Hi [~swd847]! I suppose, that the problem is much deeper. Oracle DB doesn't have AUTOCOMMIT option at ALL!!! So the client should manage his transactions every time manually. I do not see any TX management over a connection in the method {code} org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence#persistTimer {code} That's mean, that finishing timer invocation will not be persisted ( or it will be in some serendipitous cases when the same connection will be used in the method _shouldRun_, where TX is managed) Right now (I've tried to make it work in WF11 and WF12) persistent Timer logic doesn't work reliably with the Oracle DB. > Timer fails if transaction isolation set to SERIALIZABLE on Oracle 11g > ---------------------------------------------------------------------- > > Key: WFLY-6412 > URL: https://issues.jboss.org/browse/WFLY-6412 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.0.Final, 10.0.0.Final > Environment: Linux, JDK8, Oracle DB 11g > Reporter: Gábor Péntek > Assignee: Stuart Douglas > Fix For: 11.0.0.Alpha1 > > > If the transaction isolation level is set to SERIALIZABLE if one node aquires the row lock via the > UPDATE JBOSS_EJB_TIMER.. > the other nodes throw an > ORA-08177: can't serialize access for this transaction > exception. > The timer thats row threw the exception never runs any more, not even in case the other nodes were shut down. > The serialization exception is also thrown upon server/application startup sometimes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2425) [DMN Designer] Undo of relation column deletion is not proper

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2425?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2425: ------------------------------------- [~manstis] well, just to give more context, I am trying to test (unfortunately manually) things, I think could be affected by changes in the given PR. Would you like to see my "acceptance test" immediately when I file jira? > [DMN Designer] Undo of relation column deletion is not proper > ------------------------------------------------------------- > > Key: DROOLS-2425 > URL: https://issues.jboss.org/browse/DROOLS-2425 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-27 12-12-05.png, Screenshot from 2018-03-27 12-14-47.png, Screenshot from 2018-03-27 12-14-55.png > > > This issue was spotted during DROOLS-2392 review. > In special cases undo of delete relation column is not proper. > h2. Acceptance test > # Steps to reproduce fixed (/) > # Deletion is undone properly > ## Deletion of con. entry (/) > ## Deletion of Dec. table row (/) > ## Deletion of Dec. table column (x) > ## Deletion of Relation column > ## Deletion of Relation row > ## Deletion of Function parameter > # Clear of expression type is undone properly -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10172) Add support for JSR-375 EE Security as required for Java EE 8

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10172?page=com.atlassian.jira.plugin... ] Stuart Douglas moved EAP7-980 to WFLY-10172: -------------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-10172 (was: EAP7-980) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Security (was: Security) Target Release: (was: 7.2.0.GA) > Add support for JSR-375 EE Security as required for Java EE 8 > ------------------------------------------------------------- > > Key: WFLY-10172 > URL: https://issues.jboss.org/browse/WFLY-10172 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Labels: JavaEE8 > > This depends on EAP7-649 > In general at the outset this RFE should be the minimal required on top of EAP7-649 to be compliant with EE security most likely using a much from the RI as possible meaning this feature should be more about integration. If issues are found using the RI we can always choose to address those later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo edited comment on SWSQE-116 at 4/4/18 4:38 PM: ----------------------------------------------------------------------- For 1,2 and 3, we have viet quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart) I think SWSQE-111 can solve item 4. Any other thoughts [~fbrychta]? was (Author: gbaufake): For 1,2 and 3, we have @viet quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart) I think SWSQE-111 can solve item 4. Any other thoughts [~fbrychta]? > Reinstall openshift production cluster > -------------------------------------- > > Key: SWSQE-116 > URL: https://issues.jboss.org/browse/SWSQE-116 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > Currently there are following problems with our OS cluster: > * docker on nodes is using loopback devices which is strongly discouraged for production use > * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs" > * different root passwords > We need to: > # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade) > # reinstall RHELs with recommended partitions > # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/... > # install OS 3.9 > # create mojo documentation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo edited comment on SWSQE-116 at 4/4/18 4:38 PM: ----------------------------------------------------------------------- For 1,2 and 3, we have @viet quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart) I think SWSQE-111 can solve item 4. Any other thoughts [~fbrychta]? was (Author: gbaufake): For 1,2 and 3, we have Viet's quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart) I think SWSQE-111 can solve item 4. Any other thoughts [~fbrychta]? > Reinstall openshift production cluster > -------------------------------------- > > Key: SWSQE-116 > URL: https://issues.jboss.org/browse/SWSQE-116 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > Currently there are following problems with our OS cluster: > * docker on nodes is using loopback devices which is strongly discouraged for production use > * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs" > * different root passwords > We need to: > # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade) > # reinstall RHELs with recommended partitions > # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/... > # install OS 3.9 > # create mojo documentation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-116: ----------------------------------------------- For 1,2 and 3, we have Viet's quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart) I think SWSQE-111 can solve item 4. Any other thoughts [~fbrychta]? > Reinstall openshift production cluster > -------------------------------------- > > Key: SWSQE-116 > URL: https://issues.jboss.org/browse/SWSQE-116 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > Currently there are following problems with our OS cluster: > * docker on nodes is using loopback devices which is strongly discouraged for production use > * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs" > * different root passwords > We need to: > # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade) > # reinstall RHELs with recommended partitions > # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/... > # install OS 3.9 > # create mojo documentation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 April 2018