April 2014 - jboss-jira - Jboss List Archives

[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: ------------------------------------------------ Lin Gao <lgao(a)redhat.com> changed the Status of [bug 1088469|https://bugzilla.redhat.com/show_bug.cgi?id=1088469] from ASSIGNED to POST > ConnectionListener leaked if TSR throws IllegalStateException > ------------------------------------------------------------- > > Key: JBJCA-1159 > URL: https://issues.jboss.org/browse/JBJCA-1159 > Project: IronJacamar > Issue Type: Bug > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-1859) AS won't boot with sun jmx enabled

by Robb Greathouse (JIRA)

[ https://issues.jboss.org/browse/AS7-1859?page=com.atlassian.jira.plugin.s... ] Robb Greathouse commented on AS7-1859: -------------------------------------- Does anyone know if this one has been fixed in EAP? > AS won't boot with sun jmx enabled > ---------------------------------- > > Key: AS7-1859 > URL: https://issues.jboss.org/browse/AS7-1859 > Project: Application Server 7 > Issue Type: Bug > Components: Logging > Affects Versions: 7.1.0.Alpha1 > Environment: sun jdk6 windows 7 as-7.1.0.Alpha1 > Reporter: Dan Hanley > Assignee: David Lloyd > > This appears to be a regression to https://issues.jboss.org/browse/JBAS-7427 in AS7.1 > > set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote -Djava.util.logging.manager=org.jboss.logmanager.LogManager > > standalone.bat > =============================================================================== > JBoss Bootstrap Environment > JBOSS_HOME: c:\jboss-as-7.1.0.Alpha1-SNAPSHOT > JAVA: C:\Program Files\Java\jdk1.6.0_22\bin\java > JAVA_OPTS: -Dprogram.name=standalone.bat -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+UseParallelGC -XX:PermSize=6g -XX:MaxPermSize=6g -Xms512m > -Xmx4g -Xss256k -Dhornetq.server-id=119 -Dsqs.queue.name=danQ -Duser.timezone=gmt -Djava.net.preferIPv4Stack=true -Djms.server=193.131.98.79 -Djboss.bind.address=193.131.98.79 -Djb > oss.partition.name=dan-pc -Djboss.partition.udpGroup=79 -Dpublic.firewall.address=dan-pc -Xrunjdwp:transport=dt_socket,address=8788,server=y,suspend=n -Dcom.sun.management.jmxrem > ote -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -server > =============================================================================== > Listening for transport dt_socket at address: 8788 > Could not load Logmanager "org.jboss.logmanager.LogManager" > java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > at java.util.logging.LogManager$1.run(LogManager.java:168) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.<clinit>(LogManager.java:158) > at java.util.logging.Logger.getLogger(Logger.java:273) > at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:57) > at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:42) > at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:760) > at sun.management.Agent.startAgent(Agent.java:135) > at sun.management.Agent.startAgent(Agent.java:239) > WARNING: Failed to load the specified logmodule org.jboss.logmanager:main > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:81) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogMana > ger") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more > Heap > PSYoungGen total 152896K, used 23619K [0x00000002aaaa0000, 0x00000002b5540000, 0x00000002ffff0000) > eden space 131072K, 18% used [0x00000002aaaa0000,0x00000002ac1b0f30,0x00000002b2aa0000) > from space 21824K, 0% used [0x00000002b3ff0000,0x00000002b3ff0000,0x00000002b5540000) > to space 21824K, 0% used [0x00000002b2aa0000,0x00000002b2aa0000,0x00000002b3ff0000) > PSOldGen total 349568K, used 0K [0x00000001ffff0000, 0x0000000215550000, 0x00000002aaaa0000) > object space 349568K, 0% used [0x00000001ffff0000,0x00000001ffff0000,0x0000000215550000) > PSPermGen total 6291456K, used 10763K [0x000000007fff0000, 0x00000001ffff0000, 0x00000001ffff0000) > object space 6291456K, 0% used [0x000000007fff0000,0x0000000080a72d30,0x00000001ffff0000) > Press any key to continue . . . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3271) Upgrade to Apache CXF 2.7.11

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3271?page=com.atlassian.jira.plugin.... ] Alessio Soldano resolved WFLY-3271. ----------------------------------- Resolution: Done > Upgrade to Apache CXF 2.7.11 > ---------------------------- > > Key: WFLY-3271 > URL: https://issues.jboss.org/browse/WFLY-3271 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 8.1.0.CR1 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 8.1.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3237) doing a read-only operation with the CLI sets a server in "restart-required" mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3237?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3237: ----------------------------------------------- Emanuel Muckenhuber <emuckenh(a)redhat.com> changed the Status of [bug 1085913|https://bugzilla.redhat.com/show_bug.cgi?id=1085913] from ASSIGNED to POST > doing a read-only operation with the CLI sets a server in "restart-required" mode > --------------------------------------------------------------------------------- > > Key: WFLY-3237 > URL: https://issues.jboss.org/browse/WFLY-3237 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > > In domain mode, doing a read-only operation with the CLI on a remote HC, sets the remote server in "restart-required" mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3275) Make log4j test scoped dependency

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3275?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3275: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1085730|https://bugzilla.redhat.com/show_bug.cgi?id=1085730] from POST to MODIFIED > Make log4j test scoped dependency > --------------------------------- > > Key: WFLY-3275 > URL: https://issues.jboss.org/browse/WFLY-3275 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.1.0.Final, 9.0.0.CR1 > > > There's no real need for a log4j dependency except for some tests. Currently the log4j module is aliased to {{org.jboss.log4j.logmanager}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3230) StackOverflowError when trying to access non existing page/servlet in WildFly 8.0.0

by Yaniv Peleg (JIRA)

[ https://issues.jboss.org/browse/WFLY-3230?page=com.atlassian.jira.plugin.... ] Yaniv Peleg commented on WFLY-3230: ----------------------------------- I now understand why you were unable to reproduce Please add to your web.xml mapping to error code 405: <error-page> <error-code>405</error-code> <location>/error.html</location> </error-page> Then send a post request to non existing page > StackOverflowError when trying to access non existing page/servlet in WildFly 8.0.0 > ----------------------------------------------------------------------------------- > > Key: WFLY-3230 > URL: https://issues.jboss.org/browse/WFLY-3230 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Yaniv Peleg > Assignee: Stuart Douglas > Labels: jboss > Fix For: 8.1.0.Final > > > I am using WildFly 8.0.0 (Final). > When sending Post request to non existing page/servlet I get StackOverflowError exception. > Looks like there is infinit loop in method calls when processing the request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-824) Release JBoss Negotiation 2.1.6

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-824: ----------------------------------------- Summary: Release JBoss Negotiation 2.1.6 Key: SECURITY-824 URL: https://issues.jboss.org/browse/SECURITY-824 Project: PicketBox Issue Type: Release Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_1_6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3237) doing a read-only operation with the CLI sets a server in "restart-required" mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3237?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3237: ----------------------------------------------- Emanuel Muckenhuber <emuckenh(a)redhat.com> changed the Status of [bug 1085913|https://bugzilla.redhat.com/show_bug.cgi?id=1085913] from NEW to ASSIGNED > doing a read-only operation with the CLI sets a server in "restart-required" mode > --------------------------------------------------------------------------------- > > Key: WFLY-3237 > URL: https://issues.jboss.org/browse/WFLY-3237 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > > In domain mode, doing a read-only operation with the CLI on a remote HC, sets the remote server in "restart-required" mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1172) CCM sync should be called before main sync

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1172?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1172. ------------------------------------ Resolution: Done > CCM sync should be called before main sync > ------------------------------------------ > > Key: JBJCA-1172 > URL: https://issues.jboss.org/browse/JBJCA-1172 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.1.5.Final, 1.2.0.Beta1 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Minor > Fix For: 1.1.6.Final, 1.2.0.Beta2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-102) Messages#getBundle() needs to be privileged

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-102?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on JBLOGGING-102: --------------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1080991|https://bugzilla.redhat.com/show_bug.cgi?id=1080991] from ON_QA to VERIFIED > Messages#getBundle() needs to be privileged > ------------------------------------------- > > Key: JBLOGGING-102 > URL: https://issues.jboss.org/browse/JBLOGGING-102 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.1.4.GA, 3.2.0.Beta1 > Reporter: Ivo Studensky > Assignee: James Perkins > Fix For: 3.1.3.GA, 3.2.0.Beta1 > > > It ({{org.jboss.logging.Messages#getBundle(Class<T> type, Locale locale)}}) calls {{type.getClassLoader()}} which requires privileges when running with Security Manager. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 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 April 2014