August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1797) NakackTest testReceptionOfAllMessages fails to receive all messages

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1797?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1797: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 927966|https://bugzilla.redhat.com/show_bug.cgi?id=927966] from VERIFIED to CLOSED > NakackTest testReceptionOfAllMessages fails to receive all messages > ------------------------------------------------------------------- > > Key: JGRP-1797 > URL: https://issues.jboss.org/browse/JGRP-1797 > Project: JGroups > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.2.13 > Environment: RHEL (5/24), Solaris (6/24), HPUX (1/2) where x/y means x failures over y test executions. > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > Attachments: stdout.txt > > > This test does the following: > - involves channels A, B, and C where only B and C are senders and all are receivers > - B and C send 1000 multicast messages > - checks that all messages are received and in the correct order > This test is failing intermittently but quite often. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1921) Cancel operation is ignored when flushing JMS destination metrics in the management console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1921?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1921: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 999813|https://bugzilla.redhat.com/show_bug.cgi?id=999813] from VERIFIED to CLOSED > Cancel operation is ignored when flushing JMS destination metrics in the management console > ------------------------------------------------------------------------------------------- > > Key: WFLY-1921 > URL: https://issues.jboss.org/browse/WFLY-1921 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Osamu Nagano > Assignee: Harald Pehl > > When you push "Flush" button on JMS Destinations runtime tab (both of queues and topics), a confirmation dialog box brings up. "Cancel" button in the dialog box is always ignored and destination flushing is inevitably executed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-299) Add support for OpenSSL syntax when defining ciphers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-299?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-299: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1078204|https://bugzilla.redhat.com/show_bug.cgi?id=1078204] from VERIFIED to CLOSED > Add support for OpenSSL syntax when defining ciphers > ---------------------------------------------------- > > Key: JBWEB-299 > URL: https://issues.jboss.org/browse/JBWEB-299 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: JBossWeb-7.2.1.GA > Reporter: Emmanuel Hugonnet > Assignee: Remy Maucherat > Attachments: bz-1078204.patch > > > SSL connector fails to start if cipher-suite="ALL" even though in the xsd schema it is defined as default value -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3324) POJO objects are not removed from logging.properties when manually removing them from JBoss Config XML

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3324?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3324: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1095516|https://bugzilla.redhat.com/show_bug.cgi?id=1095516] from VERIFIED to CLOSED > POJO objects are not removed from logging.properties when manually removing them from JBoss Config XML > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-3324 > URL: https://issues.jboss.org/browse/WFLY-3324 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: 8.1.0.CR1 > Reporter: Kyle Lape > Assignee: James Perkins > Fix For: 8.1.0.CR2, 8.1.0.Final > > > If I remove a custom Log4J appender from my standalone.xml and restart JBoss, I can still see the POJO definition for the removed appender in my {{logging.properties}} file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-300) High CPU in concurrent access to the JSSESupport keySizeCache map

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-300?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-300: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1105160|https://bugzilla.redhat.com/show_bug.cgi?id=1105160] from VERIFIED to CLOSED > High CPU in concurrent access to the JSSESupport keySizeCache map > ----------------------------------------------------------------- > > Key: JBWEB-300 > URL: https://issues.jboss.org/browse/JBWEB-300 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossWeb-7.3.0.GA, JBossWeb-7.4.0.GA > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > > The keySizeCache map in JSSESupport isn't protected from concurrent access and so can cause high CPU loops. The complete fix from the tomcat bug that had this map access synchronized wasn't used: > https://issues.apache.org/bugzilla/show_bug.cgi?id=47744 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2261) standalone.sh --debug without port number not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2261?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2261: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1063289|https://bugzilla.redhat.com/show_bug.cgi?id=1063289] from VERIFIED to CLOSED > standalone.sh --debug without port number not working > ------------------------------------------------------ > > Key: WFLY-2261 > URL: https://issues.jboss.org/browse/WFLY-2261 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Jeff Mesnil > Fix For: 8.1.0.CR1, 8.1.0.Final > > > ./standalone.sh --debug port-num works, but it failed when omitting port number. > sh -x standalone.sh --debug (expecting the default port 8787 to be used) > {noformat} > + eval '"/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java"' '-D"[Standalone]"' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n '"-Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log"' '"-Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties"' -jar '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar"' -mp '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules"' org.jboss.as.standalone '-Djboss.home.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT"' '-Djboss.server.base.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone"' ' ""' > ++ /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java '-D[Standalone]' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log -Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties -jar /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar -mp /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules org.jboss.as.standalone -Djboss.home.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT -Djboss.server.base.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone '' > Listening for transport dt_socket at address: 8787 > 12:19:36,715 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final > 12:19:36,886 ERROR [stderr] (main) JBAS015801: Invalid option '' > 12:19:36,893 INFO [stdout] (main) > 12:19:36,893 INFO [stdout] (main) Usage: standalone.sh [args...] > {noformat} > sh -x standalone.sh --debug 8787 (the working command) > {noformat} > + eval '"/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java"' '-D"[Standalone]"' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n '"-Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log"' '"-Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties"' -jar '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar"' -mp '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules"' org.jboss.as.standalone '-Djboss.home.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT"' '-Djboss.server.base.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone"' '' > ++ /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java '-D[Standalone]' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log -Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties -jar /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar -mp /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules org.jboss.as.standalone -Djboss.home.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT -Djboss.server.base.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone > Listening for transport dt_socket at address: 8787 > 12:20:39,251 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final > 12:20:39,626 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Beta2 > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3499) POA_QUEUE_MAX is limited to 200 in EAP 5 a value of 500 was possible

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3499?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3499: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1070709|https://bugzilla.redhat.com/show_bug.cgi?id=1070709] from VERIFIED to CLOSED > POA_QUEUE_MAX is limited to 200 in EAP 5 a value of 500 was possible > -------------------------------------------------------------------- > > Key: WFLY-3499 > URL: https://issues.jboss.org/browse/WFLY-3499 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.1.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Description from Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1070709 : > POA_QUEUE_MAX is limited to 200 in EAP 5 a value of 500 was possible -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1110) Pool statistics are not cleared

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1110?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1110: ------------------------------------------------ Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1081058|https://bugzilla.redhat.com/show_bug.cgi?id=1081058] from VERIFIED to CLOSED > Pool statistics are not cleared > ------------------------------- > > Key: JBJCA-1110 > URL: https://issues.jboss.org/browse/JBJCA-1110 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.19.Final > Reporter: Koen Janssens > Assignee: Jesper Pedersen > Fix For: 1.1.2.Final > > > Invoking the 'clear statistics' JMX method on a connection pool has no effect. > Quite annoying since it forces me to restart to get a useful value for the 'average' values such as 'averageblockingtime' > Better implement the method or don't provide a clear method at all. > Today, org.jboss.jca.core.connectionmanager.pool.mcp.ManagedConnectionPoolStatisticsImpl#clear is a no-op... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1161) NPE in SemaphoreArrayListManagedConnectionPool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1161?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1161: ------------------------------------------------ Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1081058|https://bugzilla.redhat.com/show_bug.cgi?id=1081058] from VERIFIED to CLOSED > NPE in SemaphoreArrayListManagedConnectionPool > ---------------------------------------------- > > Key: JBJCA-1161 > URL: https://issues.jboss.org/browse/JBJCA-1161 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.25.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.26.Final > > > {noformat} > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.doDestroy(SemaphoreArrayListManagedConnectionPool.java:866) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:312) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:404) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1159) ConnectionListener leaked if TSR throws IllegalStateException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1159?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1159: ------------------------------------------------ Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1081058|https://bugzilla.redhat.com/show_bug.cgi?id=1081058] from VERIFIED to CLOSED > ConnectionListener leaked if TSR throws IllegalStateException > ------------------------------------------------------------- > > Key: JBJCA-1159 > URL: https://issues.jboss.org/browse/JBJCA-1159 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.24.Final, 1.1.4.Final > Environment: AS7 EAP6.1 > Reporter: Koen Janssens > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.25.Final, 1.1.5.Final, 1.2.0.Beta1 > > > When a connection is retrieved from the MCP, ironjacamar will register it to ongoing JTA transaction. However, if the ongoing TX is not 'active' anymore the connection is lost. > The code of AbstractPool demonstrates the problem. The call to getLock will throw an exception if the current TX is not active anymore and the cl is not returned to the pool. > This issue can be reproduced on AS7 by using any EJB that requires a tx and does something with a DB connection. Put a breakpoint in the code below after retrieving the connectionlistener, and then wait for the transaction to timeout. Once that's done, continue the thread. The connection is not release (can be seen in JMX) > We have noticed this problem regularly during our performance tests. > {code} > ConnectionListener cl = mcp.getConnection(subject, cri); > if (trace) > log.tracef("Got connection from pool tracked by transaction=%s tx=%s", cl, trackByTransaction); > TransactionSynchronizationRegistry tsr = getTransactionSynchronizationRegistry(); > Lock lock = getLock(); > try > { > lock.lockInterruptibly(); > } > catch (InterruptedException ie) > { > Thread.interrupted(); > throw new ResourceException(bundle.unableObtainLock(), ie); > } > {code} > It seems this issue was introduced by changes done for https://issues.jboss.org/browse/JBJCA-572 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

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 August 2014