September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1029) ServiceInvoker.deliverAsync should tidy up message properties after delivery to deadLetterService

by Kevin Conner (JIRA)

ServiceInvoker.deliverAsync should tidy up message properties after delivery to deadLetterService ------------------------------------------------------------------------------------------------- Key: JBESB-1029 URL: http://jira.jboss.com/jira/browse/JBESB-1029 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR1 ServiceInvoker.deliverAsync uses properties on the message to effect an asynchronous redelivery. Unfortunately it does not reset these properties afterwards, resulting in all further processing of that message being marked for redelivery. -- 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, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-1030) deadletter QS SyncAction should go to DLQ

by Kevin Conner (JIRA)

deadletter QS SyncAction should go to DLQ ----------------------------------------- Key: JBESB-1030 URL: http://jira.jboss.com/jira/browse/JBESB-1030 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR1 The deadletter QS was changed, prior to GA, to reflect the current behaviour. This behaviour is wrong so the QS should be reverted. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-628) Remove use of ThreadLocal in MessageDeliveryAdapter

by Tom Fennelly (JIRA)

Remove use of ThreadLocal in MessageDeliveryAdapter --------------------------------------------------- Key: JBESB-628 URL: http://jira.jboss.com/jira/browse/JBESB-628 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly This was only suppose to be a quick hack (by me), but I noticed today that I never went back and cleaned it up :-( -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1026) bpm_orchestration scripts no longer have access to body contents

by Kevin Conner (JIRA)

bpm_orchestration scripts no longer have access to body contents ---------------------------------------------------------------- Key: JBESB-1026 URL: http://jira.jboss.com/jira/browse/JBESB-1026 Project: JBoss ESB Issue Type: Bug Components: Examples Affects Versions: 4.2.1 IR1 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2.1 IR1 The groovy scripts try to access 'message.body.contents' but this is no longer set. The result is the following error. 10:31:05,846 ERROR [GroovyActionProcessor] Error executing Groovy script. java.lang.NullPointerException at java.lang.String.<init>(String.java:144) Other QSes may also be affected. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1006) Change artifact zips to unpack into a directory.

by Kevin Conner (JIRA)

Change artifact zips to unpack into a directory. ------------------------------------------------ Key: JBESB-1006 URL: http://jira.jboss.com/jira/browse/JBESB-1006 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Release Process Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2.1 The zip artifacts should be created such that they can unpack their contents into a single directory. At present the contents are unpacked into the CWD. The jbossesb artifact should also be created with the version name. -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1028) JMSSendQueueSetup needs tidying up

by Kevin Conner (JIRA)

JMSSendQueueSetup needs tidying up ---------------------------------- Key: JBESB-1028 URL: http://jira.jboss.com/jira/browse/JBESB-1028 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR1 The JMSSendQueueSetup constructor needs to be tidied up. There are two issues with the current code - masking of NamingException from getQueueSession - potential leak of sessions on errors -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1027) Missing code for deprecating byte array

by Mark Little (JIRA)

Missing code for deprecating byte array --------------------------------------- Key: JBESB-1027 URL: http://jira.jboss.com/jira/browse/JBESB-1027 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.1 IR1 -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-993) The integrated jBPM works incorrectly

by Jiri Pechanec (JIRA)

The integrated jBPM works incorrectly ------------------------------------- Key: JBESB-993 URL: http://jira.jboss.com/jira/browse/JBESB-993 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Blocker Try to run bpm_orchestration1. Check the log below. The process steps are executed multiple times and there are error messages regarding token unlocking. 11:33:44,598 INFO [STDOUT] Executed by the process, not by the ESB 11:33:45,493 INFO [STDOUT] 1********** Begin Service 1 *********** 11:33:45,566 INFO [STDOUT] In: Start It Up 11:33:45,566 INFO [STDOUT] Out: Service 1 Start It Up 11:33:45,567 INFO [STDOUT] ************ End Service 1 ************ 11:33:45,820 INFO [STDOUT] 2********** Begin Service 2 *********** 11:33:45,821 INFO [STDOUT] In: Service 1 Start It Up 11:33:45,821 INFO [STDOUT] Out: Service 2 Service 1 Start It Up 11:33:45,821 INFO [STDOUT] ************ End Service 2 ************ 11:33:46,868 INFO [STDOUT] 3********** Begin Service 3 *********** 11:33:46,868 INFO [STDOUT] In: Service 2 Service 1 Start It Up 11:33:46,869 INFO [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up 11:33:46,869 INFO [STDOUT] ************ End Service 3 ************ 11:33:47,615 INFO [STDOUT] Executed by the process, not by the ESB 11:33:47,742 INFO [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up 11:33:48,631 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:48,631 INFO [STDOUT] Executed by the process, not by the ESB 11:33:48,773 INFO [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up 11:33:49,611 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:49,715 INFO [STDOUT] 3********** Begin Service 3 *********** 11:33:49,716 INFO [STDOUT] In: Service 3 Service 2 Service 1 Start It Up 11:33:49,716 INFO [STDOUT] Out: Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:49,716 INFO [STDOUT] ************ End Service 3 ************ 11:33:50,568 INFO [STDOUT] Executed by the process, not by the ESB 11:33:50,753 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:51,586 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:51,587 INFO [STDOUT] Executed by the process, not by the ESB 11:33:51,681 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:52,542 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:52,638 INFO [STDOUT] 2********** Begin Service 2 *********** 11:33:52,638 INFO [STDOUT] In: Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:52,659 INFO [STDOUT] Out: Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:52,659 INFO [STDOUT] ************ End Service 2 ************ 11:33:53,652 INFO [STDOUT] 3********** Begin Service 3 *********** 11:33:53,653 INFO [STDOUT] In: Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:53,653 INFO [STDOUT] Out: Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:53,653 INFO [STDOUT] ************ End Service 3 ************ 11:33:54,436 INFO [STDOUT] Executed by the process, not by the ESB 11:33:54,507 INFO [MessageSpy] Body: Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:55,383 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:55,384 INFO [STDOUT] Executed by the process, not by the ESB 11:33:55,472 INFO [MessageSpy] Body: Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:56,343 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:56,519 INFO [STDOUT] 3********** Begin Service 3 *********** 11:33:56,519 INFO [STDOUT] In: Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:56,520 INFO [STDOUT] Out: Service 3 Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:56,520 INFO [STDOUT] ************ End Service 3 ************ 11:33:57,307 INFO [STDOUT] Executed by the process, not by the ESB 11:33:57,352 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:33:58,256 WARN [Token] lock owner 'token[1]' tries to unlock token '1' which is not locked 11:33:58,256 INFO [STDOUT] Executed by the process, not by the ESB 11:33:58,385 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up 11:34:00,073 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 3 Service 3 Service 2 Service 1 Start It Up -- 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, 7 months

6
16
0 / 0

[JBoss JIRA] Created: (JBESB-748) FTP couriers leak FTP connections

by Kevin Conner (JIRA)

FTP couriers leak FTP connections --------------------------------- Key: JBESB-748 URL: http://jira.jboss.com/jira/browse/JBESB-748 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The FTP Couriers are leaking FTP connections as they are never cleaned up. The easiest way to see this is to comment out the max-connection, max-login properties in the ftpd.properties file. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-836) ScheduledRedeliveryUnitTest does not pass deterministically

by Mark Little (JIRA)

ScheduledRedeliveryUnitTest does not pass deterministically ----------------------------------------------------------- Key: JBESB-836 URL: http://jira.jboss.com/jira/browse/JBESB-836 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2 The test continues to fail most of the time on my machine: [java] [junit] Testcase: unknown took 1.959 sec [java] [junit] Testcase: unknown took 10.728 sec [java] [junit] Caused an ERROR [java] [junit] null [java] [junit] java.lang.AssertionError: null [java] [junit] at org.junit.Assert.fail(Assert.java:69) [java] [junit] at org.junit.Assert.assertTrue(Assert.java:32) [java] [junit] at org.junit.Assert.assertNull(Assert.java:241) [java] [junit] at org.junit.Assert.assertNull(Assert.java:250) [java] [junit] at org.jboss.soa.esb.esb.persistence.tests.ScheduledRedeliveryUnitTest.test_simple_schedule_01(ScheduledRedeliveryUnitTest.java:101) [java] [junit] at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) [java] [junit] at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) [java] [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [java] [junit] at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) [java] [junit] at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) [java] [junit] at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) [java] [junit] at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) [java] [junit] at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) Since this could a symptom of somethig more fundamental, we need to know what the root cause is and get a fix in place. -- 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, 7 months

3
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007