October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-773) ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor

by Petr Jurak (JIRA)

[ https://issues.jboss.org/browse/WFCORE-773?page=com.atlassian.jira.plugin... ] Petr Jurak reassigned WFCORE-773: --------------------------------- Assignee: Petr Jurak (was: Enrique González Martínez) > ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor > -------------------------------------------------------------------------------------------- > > Key: WFCORE-773 > URL: https://issues.jboss.org/browse/WFCORE-773 > Project: WildFly Core > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Petr Jurak > > BoundedQueueThreadPool does not support zero length queue setup. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFLY-7275: ------------------------------------- PR is linked in XNIO-276: https://github.com/xnio/xnio/pull/97 > Wildfly eats the CPU up to 100% and does not respond > ---------------------------------------------------- > > Key: WFLY-7275 > URL: https://issues.jboss.org/browse/WFLY-7275 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit > Reporter: Krisztian Kocsis > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-10-07 at 20.18.27.png, Screen Shot 2016-10-07 at 20.18.31.png, wildfly-after-hang+1min.txt, wildfly-after-hang.txt, wildfly-hang-real-stacktrace.txt, wildfly-hang.txt > > > Hi! > > I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server. > It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile. > > I'v attached the stack trace but I unfortunately don't see anything according to my knowledge. > Please help me, I can provide more information if necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2117) TP: messages to self are not batched

by Bela Ban (JIRA)

Bela Ban created JGRP-2117: ------------------------------ Summary: TP: messages to self are not batched Key: JGRP-2117 URL: https://issues.jboss.org/browse/JGRP-2117 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.0 If A sends 100 multicast messages (or unicast messages to self), the messages to self are not batched but looped back individually, each using a separate thread from the thread pool. So in the above case, A will receive its own 100 messages using 100 threads from the pool. It would be more efficient to batch the 100 messages into a batch and then loop the batch back, taking up 1 thread instead of 100! To do this, looping back has to be done _after_ the bundler, when the bundler is sending the message batch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2116) MPING: restart doesn't work

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2116?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2116. ---------------------------- Resolution: Done Discarding discovery request from self > MPING: restart doesn't work > --------------------------- > > Key: JGRP-2116 > URL: https://issues.jboss.org/browse/JGRP-2116 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0 > > Attachments: bla.java, tcp.xml > > > MPING in a TCP stack doesn't pass a connect-disconnect-connect cycle, but the 2nd connect has 10 failed JOIN requests and then becomes a singleton -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6921) org.wildfly.test.extension.rts.InboundBridgeTestCase failing when transaction uses JTS

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-6921?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka closed WFLY-6921. --------------------------------- Resolution: Duplicate Issue Duplicates the WFLY-5574 as this one was just moved from JBEAP space when agreed that the issue is not an issue of the product. > org.wildfly.test.extension.rts.InboundBridgeTestCase failing when transaction uses JTS > -------------------------------------------------------------------------------------- > > Key: WFLY-6921 > URL: https://issues.jboss.org/browse/WFLY-6921 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondra Chaloupka > Assignee: Gytis Trikleris > > There is failures in testcase org.wildfly.test.extension.rts.InboundBridgeTestCase when transaction uses JTS. > Example of the failure > {code} > testCommit(org.wildfly.test.extension.rts.InboundBridgeTestCase) Time elapsed: 2.54 sec <<< FAILURE! > java.lang.AssertionError: expected:<4> but was:<5> > {code} > The JBOSS_HOME distribution is change to transaction to be run with JTS: changing the {{docs/example/standalone-rts.xml}} to switch transactions parameter in iiop orb subsystem to {{full}} and adding {{jts}} element to transactions subsystem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5574) org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5574?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reopened WFLY-5574: ----------------------------------- I'm sorry to making fuss here. This jira contains more discussions and relevant information thus reopening this one and closing as duplicate the other one (WFLY-6921) > org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS > -------------------------------------------------------------------------------------- > > Key: WFLY-5574 > URL: https://issues.jboss.org/browse/WFLY-5574 > Project: WildFly > Issue Type: Bug > Components: Test Suite, Transactions > Affects Versions: 10.0.0.CR3 > Reporter: Ondra Chaloupka > Assignee: Gytis Trikleris > Fix For: 11.0.0.CR1 > > Attachments: server.log > > > There is failures in testcase org.wildfly.test.extension.rts.InboundBridgeTestCase when transaction uses JTS. > Example of the failure > {code} > testCommit(org.wildfly.test.extension.rts.InboundBridgeTestCase) Time elapsed: 2.54 sec <<< FAILURE! > java.lang.AssertionError: expected:<4> but was:<5> > {code} > The JBOSS_HOME distribution is change to transaction to be run with JTS: changing the {{docs/example/standalone-rts.xml}} to switch transactions parameter in iiop orb subsystem to {{full}} and adding {{jts}} element to transactions subsystem. > When JBOSS_HOME is set then I've run the test in this way > {{./integration-tests.sh clean install -Dts.noSmoke -Dts.rts -Djboss.dist=$JBOSS_HOME -Dtest=InboundBridgeTestCase}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5574) org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-5574?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka closed WFLY-5574. --------------------------------- Resolution: Duplicate Issue After moving WFLY-6921 from JBEAP space this one duplicates > org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS > -------------------------------------------------------------------------------------- > > Key: WFLY-5574 > URL: https://issues.jboss.org/browse/WFLY-5574 > Project: WildFly > Issue Type: Bug > Components: Test Suite, Transactions > Affects Versions: 10.0.0.CR3 > Reporter: Ondra Chaloupka > Assignee: Gytis Trikleris > Fix For: 11.0.0.CR1 > > Attachments: server.log > > > There is failures in testcase org.wildfly.test.extension.rts.InboundBridgeTestCase when transaction uses JTS. > Example of the failure > {code} > testCommit(org.wildfly.test.extension.rts.InboundBridgeTestCase) Time elapsed: 2.54 sec <<< FAILURE! > java.lang.AssertionError: expected:<4> but was:<5> > {code} > The JBOSS_HOME distribution is change to transaction to be run with JTS: changing the {{docs/example/standalone-rts.xml}} to switch transactions parameter in iiop orb subsystem to {{full}} and adding {{jts}} element to transactions subsystem. > When JBOSS_HOME is set then I've run the test in this way > {{./integration-tests.sh clean install -Dts.noSmoke -Dts.rts -Djboss.dist=$JBOSS_HOME -Dtest=InboundBridgeTestCase}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7347) No log messages comming from Elytron - kerberos

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7347?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-6499 to WFLY-7347: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7347 (was: JBEAP-6499) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR6) > No log messages comming from Elytron - kerberos > ----------------------------------------------- > > Key: WFLY-7347 > URL: https://issues.jboss.org/browse/WFLY-7347 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Priority: Critical > > Elytron is missing log messages related to kerberos authentication. These log messages should be added. See JBEAP-6041 for more details. > I consider to be useful to have TRACE log messages at least in: > - SpnegoAuthenticationMechanism > - GSSCredentialSecurityFactory > If there are more classes involved in kerberos authnetication include them as well. > Kerberos issues are very specific. So it is very important to have as much trace information as possible. Therefore raising priority to Critical. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7346) Ignore client messaging tests failing with a security manager

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-7346: --------------------------------- Summary: Ignore client messaging tests failing with a security manager Key: WFLY-7346 URL: https://issues.jboss.org/browse/WFLY-7346 Project: WildFly Issue Type: Task Components: JMS Affects Versions: 10.1.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil The upgrade to Artemis 1.4.0 (WFLY-7245) introduced a regression for JMS clients running with a security manager. The issue was fixed in Artemis master branch (https://issues.apache.org/jira/browse/ARTEMIS-808) and will be part of the next release after 1.4.0. In the meantime, ignore the failing tests when the security manager is set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5213) Injecting external context to Artemis fails

by Bartosz Andrzejewski (JIRA)

[ https://issues.jboss.org/browse/WFLY-5213?page=com.atlassian.jira.plugin.... ] Bartosz Andrzejewski edited comment on WFLY-5213 at 10/19/16 2:56 AM: ---------------------------------------------------------------------- It worked for MDB, thank you. But problem with JMSContext remain. There is still comp/TransactionSynchronizationRegistry naming exception - on first context usage(when creating a message or a producer). was (Author: drzeyan): It worked for MDB, thank you. But problem with JMSContext remain. There is still comp/TransactionSynchronizationRegistry naming exception - on first conext usage(when creating a message or a producer). > Injecting external context to Artemis fails > ------------------------------------------- > > Key: WFLY-5213 > URL: https://issues.jboss.org/browse/WFLY-5213 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Beta2 > Reporter: Ondřej Kalman > Assignee: Jeff Mesnil > Fix For: 10.0.0.CR1 > > > When external-context is defined in EAP and it's pointing to external Artemis broker, it can't be injected in to MDB via @Resource(lookup = "java:global/externalcontext"). Such injection results in null object. > Injecting destinations from external context results in javax.ejb.EJBTransactionRolledbackException. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 October 2016