Dead-lock in rollback of scheduled messages ------------------------------------------- Key: JBMESSAGING-1161 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1161 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.SP1 Environment: OS: Windows XP SP2 / Linux RedHat JDK: Sun 1.5.0 Update 12 / 13 JBAS: 4.2.1.GA (Non-Clustered) JBM: 1.4.0.SP1 (Non-Clustered) DBMS: PostgreSQL 8.2.4 / 8.2.5 Reporter: Abel Munoz Alcaraz Assigned To: Tim Fox PRECONDITIONS: A non-clustered fresh installation of JBM 1.4.0.SP1 in a JBAS 4.2.1.GA with PostgreSQL 8.2.5. WORKFLOW: 1.- Install JBAS 4.2.1 with PostgresSQL in a Non-Clustered environment 2.- Inslall JBM 1.4.0.SP1 3.- Startup JBAS with JBM. 4.- Send 1000 scheduled messages to '/queue/QueueWithOwnRedeliveryDelay'. 5.- Session.rollback at first 5 messges. 6.- The destination is dead. If you send messages scheduling its delivery and, when they are delivered, you do more than one rollbacks then the destination is dead locked. It seems a dead lock problem in MessagingQueue.java: It uses a synchronized method from a synchronized block of code. -- 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