April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMESSAGING-1621) Provide complete message ordering in a clustered environment

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1621?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1621: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Provide complete message ordering in a clustered environment > ------------------------------------------------------------ > > Key: JBMESSAGING-1621 > URL: https://issues.jboss.org/browse/JBMESSAGING-1621 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Clustering > Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA > Reporter: Yusuke Yamamoto > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > > While JBMESSAGING-1416 states message ordering feature in a singleton configuration, customer is also requesting a complete message ordering feature which is applicable in a clustered environment. > Here's the background: > In the case JMS is used, both performance and scalability are priority. > There is a conflict between scalable JMS implementation and complete message ordering feature since order aware messages cannot be processed concurrently. > But order unaware queues should be still processed in parallel for better throughput. > Additionally, there are some cases that no downtime is acceptable. But HA-Singleton requires certain amount of time to fail-over the service to other node. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1661) Messages in JBoss 5.1 that use bridging get stuck in a devlivering mode and are not sent to the remote cluster

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1661?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1661: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Messages in JBoss 5.1 that use bridging get stuck in a devlivering mode and are not sent to the remote cluster > -------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-1661 > URL: https://issues.jboss.org/browse/JBMESSAGING-1661 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.3.GA > Environment: Linux -- JBoss 5.1 GA / JBM 1.4.3GA / Remoting 2.5.1 > Reporter: Peter Crossley > Assignee: Yong Hao Gao > Fix For: 1.4.8.SP12 > > > A Message bridge between to clusters will get in to a state where the messages will not be picked up by the bridge on the topic/queue and remain in the "delivering" counter until the bridge is restarted via the JMX console or by restarting the Jboss instance. > I attempted to use JBM 1.4.4 which has a fix (JBMESSAGING-1456) that seems to be the same issue, though do to the difference in the remoting I cannot use the 1.4.4 GA release. > Can we get the fixes that were applied to the 1.4.4 release in a usable build for JBoss AS 5.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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1648) Bridge may stop working after long time idle

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1648?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1648: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Bridge may stop working after long time idle > -------------------------------------------- > > Key: JBMESSAGING-1648 > URL: https://issues.jboss.org/browse/JBMESSAGING-1648 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Facade > Affects Versions: 1.4.3.GA > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 1.4.8.SP12 > > > Bridge service may stop working after a long time idle -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1706) JBoss Messaging sometimes causes a HeuristicMixedException

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1706?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1706: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > JBoss Messaging sometimes causes a HeuristicMixedException > ---------------------------------------------------------- > > Key: JBMESSAGING-1706 > URL: https://issues.jboss.org/browse/JBMESSAGING-1706 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Clustering > Affects Versions: 1.4.4.GA > Reporter: Richard Kennard > Assignee: Yong Hao Gao > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > Attachments: Client_Logs.txt, JBOSS_Server_Logs.txt, remoting-bisocket-service.xml, server.zip > > > I am raising this JIRA to ask the JBoss Messaging Team to take ownership of this issue. > The issue is that JBM intermittently (ie. when processing large amounts of messages, when bringing up/shutting down nodes in a cluster) throws a HeuristicMixedException. Once it does, that node in the cluster is effectively dead. No more messages get processed. My app has multiple queues, but once one queue on the node fails (say, the e-mail queue) then all queues stop working (say, the reports queues): they all report HeuristicMixedException whenever a messages is sent to them. > I am using a workaround by having a separate monitoring program that reboots the node whenever it gets stuck in this HeuristicMixedException state. > The JBoss ESB team have also had to implement a workaround: https://jira.jboss.org/jira/browse/JBESB-2484 > Others on the forum are seeing this too: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241134#4241134 > According to Kevin Conner of the ESB team, Howard worked with them on a workaround: https://jira.jboss.org/jira/browse/JBPAPP-1642, but the issue persists. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1684) Message remain in the queue and do not get dispatched

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1684?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1684: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Message remain in the queue and do not get dispatched > ----------------------------------------------------- > > Key: JBMESSAGING-1684 > URL: https://issues.jboss.org/browse/JBMESSAGING-1684 > Project: JBoss Messaging > Issue Type: Quality Risk > Components: JMS Facade > Affects Versions: 1.4.3.GA > Environment: SuSe Linux Enterprise Server 10, Java 1.5.0_11, AS 5 with JBoss Messaging - default installation > Reporter: Alexander Marktl > Assignee: Yong Hao Gao > Priority: Minor > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > Attachments: jms-provider-evaluation.zip > > > I tried to create 10 queues and send 10.000 messages per queue from a single producer per queue to a single consumer per queue. Unfortunately not all of the messages where delivered, some messages remain in the queues and wait for delivery. The JMX console for example states: 3 messages in the queue, 3 messages pending for delivery. But nothing happens. My receivers don't get these last messages. I don't know if this is a configuration issue or a bug. > The queues are named: qname_0 ...qname_n -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1718) JMS Queue MessageCount attribute isn't increased on message retrieval

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1718?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1718: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > JMS Queue MessageCount attribute isn't increased on message retrieval > --------------------------------------------------------------------- > > Key: JBMESSAGING-1718 > URL: https://issues.jboss.org/browse/JBMESSAGING-1718 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.3.GA > Reporter: Richard Opalka > Assignee: Yong Hao Gao > Fix For: 1.4.8.SP12 > > Attachments: jaxws-samples-dar-jms-client.sar, jaxws-samples-dar-jms.jar > > > We're sending JMS message to the queue and are verifying it was received by checking the JMS Queue MessageCount attribute. > This used to work on AS 500, AS 501 and AS 510 but doesn't work on AS trunk and AS Branch_5_x. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1723) Queue's delivering count == -1

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1723?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1723: -------------------------------------- Fix Version/s: 1.4.8.SP12 (was: 1.4.8.SP11) > Queue's delivering count == -1 > ------------------------------ > > Key: JBMESSAGING-1723 > URL: https://issues.jboss.org/browse/JBMESSAGING-1723 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Affects Versions: 1.4.3.GA > Reporter: Ondrej Zizka > Assignee: Yong Hao Gao > Priority: Minor > Fix For: 1.4.0.SP3.CP15, 1.4.8.SP12 > > Attachments: JMS_delivCount_-1.png > > > Delivery count of a queue is sometimes -1. See the picture attached. > Seen on EAP 5 CR3, Sun JDK 6 for Linux. > Steps to reproduce: > 1) Start a client sending messages, > 2) Start a client receiving messages, > 3) Watch the stats. If you're lucky enough, you'll see it being -1. > I haven't found anything about this in the docs: > http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone... ( 6.6.2.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

11 years, 8 months

1
0
0 / 0

[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

11 years, 8 months

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

11 years, 8 months

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

11 years, 8 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 April 2014