August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1610) expose jbossInternalLifecycle method on jms destination mbeans

by Emanuel Muckenhuber (JIRA)

expose jbossInternalLifecycle method on jms destination mbeans -------------------------------------------------------------- Key: JBMESSAGING-1610 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1610 Project: JBoss Messaging Issue Type: Task Components: AS Integration Affects Versions: 1.4.3.GA Reporter: Emanuel Muckenhuber Assignee: Tim Fox Currently the Queue and Topic xmbean definitions don't expose the jbossInternalLifecycle(String method). This method is needed that the lifecycle and state changes of a mbean are handled by microcontainer (AS5). Otherwise profileservice cannot determine the current state and a stopped jms destination would be still exposed as running to JON/JOPR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
20
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1619) add example TCP cluster configuration

by Dennis Reed (JIRA)

add example TCP cluster configuration ------------------------------------- Key: JBMESSAGING-1619 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1619 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP07 Reporter: Dennis Reed Assignee: Tim Fox Add an example TCP cluster configuration (commented out) to all the example *-persistence-service.xml files. This will make it easier for users who have issues with UDP multicast to configure it to use TCP clustering. (The same thing is being done to all the EAP configurations that don't already include this). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
22
0 / 0

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

by Howard Gao (JIRA)

Bridge may stop working after long time idle -------------------------------------------- Key: JBMESSAGING-1648 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1648 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.3.GA Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.5.GA Bridge service may stop working after a long time idle -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker

by Victor Starenky (JIRA)

Messages are piling up in the queues in clustered environment and not pulled by message sucker ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-1631 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP08 Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or 1.4.0.SP3_CP08 running on x64 windows servers. JBoss Remoting 2.5.1 or 2.2.3 Clustered XA connection factory, clustered queues, both server and client (MDBs) are deployed as one application - identical deployment for all servers in a cluster Reporter: Victor Starenky Assignee: Tim Fox We have an EJB3 application is running on a cluster of 7 servers. All servers have the same application farmed across them. We have a clustered queue and using clustered connection factory. Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a different problem. After the cluster was running for some time (usually overnight with lots of heavy background processing hapenning at that time) we see messages are "piling up" in some queues on some nodes. Sympthoms are: MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero. These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker is configured as far as I can tell. Looks like the problem might be related to client and/or server failover leaving some nodes without consumers while sucker not doing it's job (if I understand it correctly). Once we bump the timeout values much higher than they are in the original config files the problem seems to disappear or at least show up much less frequently. Specifically I'm talking about these values: messaging-service.xml: <attribute name="FailoverStartTimeout">180000</attribute> remoting-bisocket-service.xml: <attribute name="clientLeasePeriod" isParam="true">30000</attribute> <attribute name="validatorPingPeriod" isParam="true">30000</attribute> <attribute name="validatorPingTimeout" isParam="true">20000</attribute> <attribute name="registerCallbackListener">false</attribute> <attribute name="timeout" isParam="true">240000</attribute> While this serves as a temporary workaround we don't feel we can rely on JBM in a production clustered environment without having failover working properly. This is a big showstopper for us at the moment. Attached are the log files from the prod environment of 7 servers with the config files as well as log files from the test environment with just 2 servers (having same issue) and corresponding configs. The logs were produced by the test version of the messaging code with added logging as per JBMESSAGING-1456. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

6
37
0 / 0

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

by Yusuke Yamamoto (JIRA)

Provide complete message ordering in a clustered environment ------------------------------------------------------------ Key: JBMESSAGING-1621 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1621 Project: JBoss Messaging Issue Type: Feature Request Reporter: Yusuke Yamamoto Assignee: Tim Fox 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

5
22
0 / 0

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

by Alexander Marktl (JIRA)

Message remain in the queue and do not get dispatched ----------------------------------------------------- Key: JBMESSAGING-1684 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1684 Project: JBoss Messaging Issue Type: Quality Risk Environment: SuSe Linux Enterprise Server 10, Java 1.5.0_11, AS 5 with JBoss Messaging - default installation Reporter: Alexander Marktl Assignee: Tim Fox Priority: Minor 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
21
0 / 0

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

by Richard Kennard (JIRA)

JBoss Messaging sometimes causes a HeuristicMixedException ---------------------------------------------------------- Key: JBMESSAGING-1706 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1706 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.4.GA Reporter: Richard Kennard Assignee: Tim Fox 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

8
47
0 / 0

[JBoss JIRA] Created: (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 Peter Crossley (JIRA)

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://jira.jboss.org/jira/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: Tim Fox Fix For: 1.4.4.GA 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

6
17
0 / 0

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

by Ondrej Žižka (JIRA)

Queue's delivering count == -1 ------------------------------ Key: JBMESSAGING-1723 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1723 Project: JBoss Messaging Issue Type: Bug Reporter: Ondrej Žižka Delivery count of a queue is sometimes -1. See the picture attached. 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

5
26
0 / 0

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

by Richard Opalka (JIRA)

JMS Queue MessageCount attribute isn't increased on message retrieval --------------------------------------------------------------------- Key: JBMESSAGING-1718 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1718 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.3.GA Reporter: Richard Opalka Assignee: Tim Fox Fix For: 1.4.5.GA 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

5
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2009