April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMESSAGING-1707) ConcurrentModificationException in ClientClusteredConnectionFactoryDelegate

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1707?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1707: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > ConcurrentModificationException in ClientClusteredConnectionFactoryDelegate > --------------------------------------------------------------------------- > > Key: JBMESSAGING-1707 > URL: https://issues.jboss.org/browse/JBMESSAGING-1707 > Project: JBoss Messaging > Issue Type: Quality Risk > Components: JMS Client Manager > Affects Versions: 1.4.3.GA > Reporter: Pavel Slavicek > Assignee: Clebert Suconic > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > I have found ConcurrentModificationException in ClientClusteredConnectionFactoryDelegate. > Exception in thread "Thread-11" java.util.ConcurrentModificationException > at java.util.WeakHashMap$HashIterator.nextEntry(WeakHashMap.java:784) > at java.util.WeakHashMap$KeyIterator.next(WeakHashMap.java:817) > at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:414) > Client: > client with multiple threads, every thread creates-sends-receives-closes. > Problem description: > Problem is in the ClientClusteredConnectionFactoryDelegate.java in the inner class FinalizerShutdownHook. > Shutdown hook implementation should to be written as thread safe (see javadoc for addShutdownHook() method). > Method run() in the FinalizerShutdownHook class iterates over all elements in the registered delegates > but this iteration should be synchronized on the delegates object. > Please see http://java.sun.com/javase/6/docs/api/java/util/Collections.html#synchron... -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1747: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > ClassNotFoundException while consuming a message in a JMS Queue > --------------------------------------------------------------- > > Key: JBMESSAGING-1747 > URL: https://issues.jboss.org/browse/JBMESSAGING-1747 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Destination Manager > Affects Versions: 1.4.1.GA > Environment: Jboss version : 5.0.1 GA > Reporter: Stephan Lagraulet > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > We have several JMS queues setup on our jboss server. > We are using spring to handle the messages. > When several clients simultaneously post some messages in different queues, the consumer doesn't find the class for the task, ending with this stack trace: > 2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS message listener failed > java.lang.RuntimeException: fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest > at java.net.URLClassLoader$1.run(URLClassLoader.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:252) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279) > at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102) > at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772) > at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415) > at java.lang.ClassLoader.loadClass(ClassLoader.java:252) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears that the class doesn't have the right classloader as it reuses a thread previously setup with an other classloader (the application is packaged in different ears while the queues are defined in deploy), ending in this exception. > For the moment, we patched the code so that the classloader is reloaded for every call, but it does not seem like a good solution on a long term. -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1744) More documented warnings on the usage of JMS selectors

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1744?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1744: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > More documented warnings on the usage of JMS selectors > ------------------------------------------------------ > > Key: JBMESSAGING-1744 > URL: https://issues.jboss.org/browse/JBMESSAGING-1744 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Affects Versions: 1.4.0.SP3.CP08, 1.4.0.SP3.CP09, 1.4.5.GA > Environment: EAP 4.3 CP06 / 1.4.0.SP3-CP08.patch01 > Reporter: Noel Rocher > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > I'm on-site with a customer who is soon going to production. > They have designed their application using JMS Selectors on distributed queues. > We all know this is a broken design but my point is that I think this should be explicitely written in the doc. > Moreover, GSS is talking about an "unsupported configuration" see case # 348290 (https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti...). -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1739) Update to JGroup 2.8

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1739?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1739: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Update to JGroup 2.8 > -------------------- > > Key: JBMESSAGING-1739 > URL: https://issues.jboss.org/browse/JBMESSAGING-1739 > Project: JBoss Messaging > Issue Type: Feature Request > Components: AS Integration > Affects Versions: 1.4.4.GA > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.8.SP12 > > > Also this thread > http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257080#4257080 -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1735) Paging should be taken care in Transactions

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1735?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1735: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Paging should be taken care in Transactions > ------------------------------------------- > > Key: JBMESSAGING-1735 > URL: https://issues.jboss.org/browse/JBMESSAGING-1735 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > JBM queues has paging feature to save memory, but in transaction case, messages are stored in the transaction callbacks before it committed to the queue for delivery. So if too many messages are included in one transaction, it may use up memory even paging is turned on. -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1731) Expose the JBoss Messaging Cluster partition in JMX

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1731?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1731: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Expose the JBoss Messaging Cluster partition in JMX > --------------------------------------------------- > > Key: JBMESSAGING-1731 > URL: https://issues.jboss.org/browse/JBMESSAGING-1731 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Affects Versions: 1.4.4.GA > Reporter: Brad Maxwell > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > Background: > I have had a request wanting access to the members of the JBoss Messaging Cluster so that they can configure the Recovery plugin without having to hard code hosts in the configuration file. With the JBoss Messaging Cluster Partition in JMX they would be able to get an accurate list of the members in the Messaging cluster. -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1759) JGroups cannot process incoming messages during the method execution

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1759?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1759: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > JGroups cannot process incoming messages during the method execution > -------------------------------------------------------------------- > > Key: JBMESSAGING-1759 > URL: https://issues.jboss.org/browse/JBMESSAGING-1759 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Clustering > Affects Versions: 1.4.0.SP3.CP07 > Environment: JBossMessaging-1.4.0_SP3_CP7 > Reporter: Tyronne Wickramarathne > Assignee: Yong Hao Gao > Priority: Critical > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > The GroupMember#viewAccepted() takes 31min on the IncomingPacketHandler thread. The JGroups cannot process incoming messages during this method execution. It's completely blocked and leads the following log and subsequent WARNs. > 2009-11-11 11:50:12.634 [ViewHandler] WARN [GMS] - failed to collect all ACKs (1) for view [192.168.1.221:49898|2] [192.168.1.221:49898] after 2000ms, missing ACKs from [192.168.1.221:49898] (received=[]), local_addr=192.168.1.221:49898 -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1758) Derby support

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1758?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1758: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Derby support > ------------- > > Key: JBMESSAGING-1758 > URL: https://issues.jboss.org/browse/JBMESSAGING-1758 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Configuration and Management > Affects Versions: 1.4.3.GA > Reporter: Jesper Pedersen > Assignee: Yong Hao Gao > Fix For: 1.4.8.SP12 > > > In order for the application server to support Derby as the default database we need the necessary persistence-service.xml files. > Please update Branch_5_x and trunk when released. -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1754) Implement the JBossMQ behavior on JBM, when stopDelivery() is invoked via JMX console

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1754?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1754: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Implement the JBossMQ behavior on JBM, when stopDelivery() is invoked via JMX console > ------------------------------------------------------------------------------------- > > Key: JBMESSAGING-1754 > URL: https://issues.jboss.org/browse/JBMESSAGING-1754 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Messaging Core > Affects Versions: 1.4.0.SP3.CP08 > Environment: JBoss-EAP-4.3_CP6, JBM-1.4.0-SP3_CP8P1 > Reporter: Tyronne Wickramarathne > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > When stopDelivery() is invoked via JMX console for any given MDB, the in process messages are rolled back to their corresponding destination without completing the process. This is however *not* a bug, but the expected behavior in JBM, for this is how it has defined the behavior of stopDelivery(). > However on JBossMQ, the in process messages are completed at first, before stopDelivery() is processed. Which means, the call made via stopDelivery() will be kept on hold, until all in process messages are successfully completed. The customers migrating from JBossMQ are seeing this as a compatibility issue, when porting their applications to work on JBM. Hence, would it be possible to accommodate the behavior seen in JBossMQ on JBM please ? > I have tested this on both JBoss-EAP-4.3_CP6 as well as on JBoss-EAP-4.2_CP7. Both have the same code base for EJB3,JCA but not the JMS provider. Therefore, I'm raising this feature request under JBM. -- 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

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1750) Allow arbitrary SQL statements for JDBCPersistenceManagerService

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1750?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1750: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Allow arbitrary SQL statements for JDBCPersistenceManagerService > ---------------------------------------------------------------- > > Key: JBMESSAGING-1750 > URL: https://issues.jboss.org/browse/JBMESSAGING-1750 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Configuration and Management > Affects Versions: 1.4.0.SP3.CP08 > Reporter: Justin Bertram > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > Allow arbitrary SQL statements in the SQLProperties field of org.jboss.messaging.core.jmx.JDBCPersistenceManagerService which will be executed just like all the others (e.g. if CreateTablesOnStartup = "true"). I imagine the statements will need to be named according to some pattern (e.g. "CREATE_*"). > This functionality will allow greater flexibility for our RDBMS support (e.g. a user could configure support for Oracle TimesTen). -- 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

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 2014