February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1761) LockServiceTest: deadlock

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1761?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1761. ---------------------------- Resolution: Done Narrowed synchronized scope of {{ClientLockTable.unlockAll()}}. > LockServiceTest: deadlock > ------------------------- > > Key: JGRP-1761 > URL: https://issues.jboss.org/browse/JGRP-1761 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > {noformat} > Found one Java-level deadlock: > ============================= > "Thread-157": > waiting to lock monitor 0x00007fc2d0002a98 (object 0x00000000ceed9348, a org.jgroups.protocols.Locking$ClientLockTable), > which is held by "pool-2-thread-10" > "pool-2-thread-10": > waiting to lock monitor 0x00007fc2d0002b48 (object 0x00000000cf48bc30, a org.jgroups.protocols.Locking$ClientLock), > which is held by "Thread-157" > > Java stack information for the threads listed above: > =================================================== > "Thread-157": > at org.jgroups.protocols.Locking$ClientLockTable.removeClientLock(Locking.java:1030) > - waiting to lock <0x00000000ceed9348> (a org.jgroups.protocols.Locking$ClientLockTable) > at org.jgroups.protocols.Locking$ClientLock._unlock(Locking.java:947) > - locked <0x00000000cf48bc30> (a org.jgroups.protocols.Locking$ClientLock) > at org.jgroups.protocols.Locking$ClientLock.unlock(Locking.java:878) > - locked <0x00000000cf48bc30> (a org.jgroups.protocols.Locking$ClientLock) > at org.jgroups.protocols.Locking.down(Locking.java:160) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1034) > at org.jgroups.JChannel.down(JChannel.java:765) > at org.jgroups.blocks.locking.LockService$LockImpl.unlock(LockService.java:161) > at org.jgroups.blocks.LockServiceTest.unlock(LockServiceTest.java:486) > at org.jgroups.blocks.LockServiceTest$AbstractAwaiter.run(LockServiceTest.java:366) > at java.lang.Thread.run(Thread.java:724) > "pool-2-thread-10": > at org.jgroups.protocols.Locking$ClientLock.unlock(Locking.java:878) > - waiting to lock <0x00000000cf48bc30> (a org.jgroups.protocols.Locking$ClientLock) > at org.jgroups.protocols.Locking$ClientLockTable.unlockAll(Locking.java:1046) > - locked <0x00000000ceed9348> (a org.jgroups.protocols.Locking$ClientLockTable) > at org.jgroups.protocols.Locking.unlockAll(Locking.java:282) > at org.jgroups.protocols.Locking.down(Locking.java:164) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1034) > at org.jgroups.JChannel.down(JChannel.java:765) > at org.jgroups.blocks.locking.LockService.unlockAll(LockService.java:65) > at org.jgroups.blocks.LockServiceTest.unlockAll(LockServiceTest.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:653) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > > Found 1 deadlock. > {noformat} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1140) New option for <validate-on-match/> policy

by Tom Ross (JIRA)

Tom Ross created JBJCA-1140: ------------------------------- Summary: New option for <validate-on-match/> policy Key: JBJCA-1140 URL: https://issues.jboss.org/browse/JBJCA-1140 Project: IronJacamar Issue Type: Feature Request Components: Code Generator Environment: JBoss EAP 6.2.0 Reporter: Tom Ross Assignee: Jesper Pedersen There is a requirement for a new option in the pool connection validation. <validate-on-match/> should validate, except if the connection has been returned recently into the pool for instance in the last 10 secs. The reasoning is that if the connection has been used in the last 10 secs, and it is consider as checked. so it is not worth doing an extra validation. The only way this could be approached at the moment would be to use more aggressively background validation. But this would put more needless pressure on the db considering all pool filled with many connections that will take time to shrink down. With the proposed solution, would be the best of both worlds: an active application does not pay for the price of validation before use, although it uses checked connections, without having to schedule aggressive background checks. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3027) Missing dependencies in module org.hibernate.hql

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-3027?page=com.atlassian.jira.plugin.... ] Sanne Grinovero resolved WFLY-3027. ----------------------------------- Resolution: Won't Fix > Missing dependencies in module org.hibernate.hql > ------------------------------------------------ > > Key: WFLY-3027 > URL: https://issues.jboss.org/browse/WFLY-3027 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Clustering > Affects Versions: 8.0.0.Final > Reporter: Davide D'Alto > Assignee: Sanne Grinovero > > The module *org.hibernate.hql* doesn't have some dependencies: > {code:xml} > <module name="org.apache.lucene"/> > <module name="hibernate.search.engine"/> > <module name="org.antlr"/> > {code} > it also requires org.antlr:antlr-runtime and org.antlr:stringtemplate that don't exist as a module -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3027) Missing dependencies in module org.hibernate.hql

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-3027?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned WFLY-3027: ------------------------------------- Assignee: Sanne Grinovero > Missing dependencies in module org.hibernate.hql > ------------------------------------------------ > > Key: WFLY-3027 > URL: https://issues.jboss.org/browse/WFLY-3027 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Clustering > Affects Versions: 8.0.0.Final > Reporter: Davide D'Alto > Assignee: Sanne Grinovero > > The module *org.hibernate.hql* doesn't have some dependencies: > {code:xml} > <module name="org.apache.lucene"/> > <module name="hibernate.search.engine"/> > <module name="org.antlr"/> > {code} > it also requires org.antlr:antlr-runtime and org.antlr:stringtemplate that don't exist as a module -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-797) Authentication attempts will fail if the DatabaseRolesMappingProvider's rolesQuery returns an empty set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-797?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-797: -------------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1067612|https://bugzilla.redhat.com/show_bug.cgi?id=1067612] from POST to MODIFIED > Authentication attempts will fail if the DatabaseRolesMappingProvider's rolesQuery returns an empty set > ------------------------------------------------------------------------------------------------------- > > Key: SECURITY-797 > URL: https://issues.jboss.org/browse/SECURITY-797 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-797.patch > > > If the DatabaseRolesMappingProvider's rolesQuery returns an empty set, then the authentication attempts will fail. Seems like it should not cause the authentication attempt to fail, since this is about mapping/adding roles. > It looks like the code detects that the result set is empty, but then it tries to get the role from the empty set. This causes an exception which in turn causes the authentication attempt to fail. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-796) LdapExtended login module does not handle a user that has a slash character in the uid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-796?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-796: -------------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1067599|https://bugzilla.redhat.com/show_bug.cgi?id=1067599] from POST to MODIFIED > LdapExtended login module does not handle a user that has a slash character in the uid > -------------------------------------------------------------------------------------- > > Key: SECURITY-796 > URL: https://issues.jboss.org/browse/SECURITY-796 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_20.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-796.patch > > > LdapExtended login module does not handle a user that has a slash character in the uid. > For example, JBoss will fail to authenticate the following user correctly: > dn: uid=weird/user,ou=Users,dc=my-domain,dc=com > uid: weird/user > cn: Weird User -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2198) Remote Naming throws the same exception for different causes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2198?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2198: ----------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1053426|https://bugzilla.redhat.com/show_bug.cgi?id=1053426] from POST to MODIFIED > Remote Naming throws the same exception for different causes > ------------------------------------------------------------ > > Key: WFLY-2198 > URL: https://issues.jboss.org/browse/WFLY-2198 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Reporter: Brad Maxwell > Assignee: Brad Maxwell > > A generic NamingException are thrown if all of the servers specified are unreachable as well as if the user/pass are invalid and a security exception is thrown up, they both are converted into a RuntimeException and a message listing the servers it was unable to call is reported. > We should be throwing a different exception in the cases we know the cause, such as connection timeout or authentication exception. > If all the the servers specified are not not running: > -------------------------------------------------------------------------------------------- > javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447] > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213) > If one of the servers is running, but the client's username/password are incorrect > -------------------------------------------------------------------------------------------- > javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447] > at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3027) Missing dependencies in module org.hibernate.hql

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-3027?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated WFLY-3027: ---------------------------------- Assignee: (was: Sanne Grinovero) > Missing dependencies in module org.hibernate.hql > ------------------------------------------------ > > Key: WFLY-3027 > URL: https://issues.jboss.org/browse/WFLY-3027 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Clustering > Affects Versions: 8.0.0.Final > Reporter: Davide D'Alto > > The module *org.hibernate.hql* doesn't have some dependencies: > {code:xml} > <module name="org.apache.lucene"/> > <module name="hibernate.search.engine"/> > <module name="org.antlr"/> > {code} > it also requires org.antlr:antlr-runtime and org.antlr:stringtemplate that don't exist as a module -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-332) Add sessionDrainingStrategy configuration option to modcluster subsystem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-332?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-332: ---------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 922042|https://bugzilla.redhat.com/show_bug.cgi?id=922042] from ON_QA to VERIFIED > Add sessionDrainingStrategy configuration option to modcluster subsystem > ------------------------------------------------------------------------ > > Key: WFLY-332 > URL: https://issues.jboss.org/browse/WFLY-332 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Fix For: 8.0.0.Beta1 > > > Add sessionDrainingStrategy configuration option to modcluster subsystem > * xsd 1.1 -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3027) Missing dependencies in module org.hibernate.hql

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-3027?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-3027: --------------------------------------- So why is it assigned to me? I don't think this is the right approach BTW. As I explained on IRC, the module *org.hibernate.hql* in WildFly just exists to satisfy a dependency of Infinispan Query, but should actually be removed once the dependency tree of Infinispan is cleaned up. If you need this for Hibernate OGM to work, you're going to need flexibility in versions anyway, so you should provide your own version in the scope of OGM using a slot. Unless the plan is to fully include Hibernate ORM in WildFly, but then this should be discossed on the mailing list. > Missing dependencies in module org.hibernate.hql > ------------------------------------------------ > > Key: WFLY-3027 > URL: https://issues.jboss.org/browse/WFLY-3027 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Clustering > Affects Versions: 8.0.0.Final > Reporter: Davide D'Alto > Assignee: Sanne Grinovero > > The module *org.hibernate.hql* doesn't have some dependencies: > {code:xml} > <module name="org.apache.lucene"/> > <module name="hibernate.search.engine"/> > <module name="org.antlr"/> > {code} > it also requires org.antlr:antlr-runtime and org.antlr:stringtemplate that don't exist as a module -- 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

12 years, 2 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 February 2014