March 2014 - jboss-jira - Jboss List Archives

[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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > 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

12 years, 2 months

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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 months

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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > 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

12 years, 2 months

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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 months

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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 months

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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 2 months

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.SP11 (was: 1.4.8.SP10) > 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.SP11 > > > 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, 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 March 2014