February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

by Bela Ban (JIRA)

Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation -------------------------------------------------------------------------------------------- Key: JGRP-297 URL: http://jira.jboss.com/jira/browse/JGRP-297 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik). This can be run every N seconds, and is useful in both stress testing and possibly also during operation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-682) Test real-life problem/constraints with large data sets

by Geoffrey De Smet (JIRA)

Test real-life problem/constraints with large data sets ------------------------------------------------------- Key: JBRULES-682 URL: http://jira.jboss.com/jira/browse/JBRULES-682 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Exam Timetabling http://www.cs.nott.ac.uk/~rxq/data.htm Nurse rostering: http://www.cs.nott.ac.uk/~tec/NRP/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-679) Move code into JBoss svn + refactor rename packages

by Geoffrey De Smet (JIRA)

Move code into JBoss svn + refactor rename packages --------------------------------------------------- Key: JBRULES-679 URL: http://jira.jboss.com/jira/browse/JBRULES-679 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Rename package net.sf.taseree to org.drools.solver -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-480) Change contract of Receiver

by Tim Fox (JIRA)

Change contract of Receiver --------------------------- Key: JBMESSAGING-480 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-480 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-876) Allow onMessage to be executed on the remoting thread

by Tim Fox (JIRA)

Allow onMessage to be executed on the remoting thread ----------------------------------------------------- Key: JBMESSAGING-876 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-876 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 As an optimisation we should allow message listeners to be executed straight through using the same thread that delivers the message to the message callback handler. This would avoid an extra context switch.. Currently the thread used is from an executor per session - so as to be strictly JMS compliant. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-875) Non durable subscription optimisation

by Tim Fox (JIRA)

Non durable subscription optimisation ------------------------------------- Key: JBMESSAGING-875 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-875 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs. Basically I think we can acknowledge them before they are sent from server to client. This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks. On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver. This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-868) Ordering issue when mixing unicast and multicast

by Tim Fox (JIRA)

Ordering issue when mixing unicast and multicast ------------------------------------------------ Key: JBMESSAGING-868 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-868 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 When routing a set of messages to nodes in a cluster, if some are routed using unicast and others using multicast (as an optimisation), then earlier messages can "overtake" later sent messages, so they are received in the wrong order on the recipient. This caused DefaultClusteredPostOfficeTest::testClusteredNonPersistentRouteWithFilterRecoverable to fail because messages were received out of order -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-751) Check and test failover behaviour when delegate methods are executing

by Tim Fox (JIRA)

Check and test failover behaviour when delegate methods are executing --------------------------------------------------------------------- Key: JBMESSAGING-751 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-751 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.CR1 Currently failover will kick in if a connection error is detected during the invocation of any XXXDelegate method which makes a remote call, although only some of these are tested. We need to a) Make sure failure of all methods that make a remote call should be tested, e.g. connection start/stop, connection.sendTransaction, session.commit/rollback, cancel, cancelDeliveries etc b) We need to analyse whether *all* these method invocations need to be retried on the new server after failover is complete. It may be the case that only some should be retried -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-839) Recover deliveries does not deal with paged references

by Tim Fox (JIRA)

Recover deliveries does not deal with paged references ------------------------------------------------------ Key: JBMESSAGING-839 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-839 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.2.0.GA When recovering deliveries ChannelSupport::recoverDeliveries after failover then there is a small possibility that the deliveries are not in memory but paged in storage - we should cater for this situation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-872) Convert destinations to ints

by Tim Fox (JIRA)

Convert destinations to ints ---------------------------- Key: JBMESSAGING-872 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-872 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Ovidiu Feodorov Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers. When sending a message the destination (and possibly the replyto) need to be serialized with the message. If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize. This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
7
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 2007