August 2007 - esb-issues - Jboss List Archives

[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-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

[JBoss JIRA] Created: (JBESB-869) Document reliability characteristics as far as message delivery is concerned

by Mark Little (JIRA)

Document reliability characteristics as far as message delivery is concerned ---------------------------------------------------------------------------- Key: JBESB-869 URL: http://jira.jboss.com/jira/browse/JBESB-869 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-932) Restructure documentation

by Mark Little (JIRA)

Restructure documentation ------------------------- Key: JBESB-932 URL: http://jira.jboss.com/jira/browse/JBESB-932 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.1 As per discussion with Joshua Wulf and Burr. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBESB-865) Separate Message Store text into Services document?

by Mark Little (JIRA)

Separate Message Store text into Services document? --------------------------------------------------- Key: JBESB-865 URL: http://jira.jboss.com/jira/browse/JBESB-865 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Message Store Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.2.1 On bahelf of intern: "Since the MessageStore text needs revisiting and the MessageStore interface seems to have increased in capabilities, wouldn't it make sense to separate it out of the Programmers Guide and into its own document, like the Registry and other services?" -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-910) Make JMSCourier set JMSHeader fields and properties when sending

by Daniel Bevenius (JIRA)

Make JMSCourier set JMSHeader fields and properties when sending ----------------------------------------------------------------- Key: JBESB-910 URL: http://jira.jboss.com/jira/browse/JBESB-910 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor This jira is similar to http://jira.jboss.com/jira/browse/JBESB-691 The usecase for this would be when one has a router in the ESB pipeline configuration and the transport being JMS. Currently, having a router in the pipeline would mean losing the correlation id, and other properties that might have been set by a calling client. This can use the same code that JMSRouter and NotifyJMS uses. -- 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-701) JMS Queue Notifier does not have configured message properties attached

by Jiri Pechanec (JIRA)

JMS Queue Notifier does not have configured message properties attached ----------------------------------------------------------------------- Key: JBESB-701 URL: http://jira.jboss.com/jira/browse/JBESB-701 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 3 The configuration Notifier with class NotifyQueues can contain a list of elements "queue" and each of these "queue" can contain a list of "messageProp" elements that contains properties to be attached to message. The properties are not attached. The reason is: Constructor NotifyQueues is populated with ConfigTree that has root at the "target" element and has correctly access to the child "queue" elements from which it initilizes but the same ConfigTree is passed to NofityJMS parent class which can't initialize properties as they are stored not on this level but on the level below under each "queue" element. -- 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

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-729) JBossWS Unit tests to verify WS-Addressing support when running with SOAPProcessor Action

by Burr Sutter (JIRA)

JBossWS Unit tests to verify WS-Addressing support when running with SOAPProcessor Action ----------------------------------------------------------------------------------------- Key: JBESB-729 URL: http://jira.jboss.com/jira/browse/JBESB-729 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Refactor JBossWS Unit Tests that confirm support of WS-Addressing when using the ESB between the consumer and the producer via the SOAPProcessor Action -- 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
9
0 / 0

[JBoss JIRA] Created: (JBESB-928) Unexpected/incorrect/consistent behavior with SQL listener - when writing to DB via Java/JDBC

by Len DiMaggio (JIRA)

Unexpected/incorrect/consistent behavior with SQL listener - when writing to DB via Java/JDBC --------------------------------------------------------------------------------------------- Key: JBESB-928 URL: http://jira.jboss.com/jira/browse/JBESB-928 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Environment: RHEL5 ESB built from SVN on August 24 Reporter: Len DiMaggio Assigned To: Mark Little Attachments: supporting_files.zip Problem description: I'm seeing odd/incorrect behavior with the SQLprovider listener as used in the helloworld_sql_action quickstart. If the records are written to the database via Java/JDBC, strange things happen, in a consistent pattern. Background: The helloworld_sql_action quickstart as distributed runs without error. If the quickstart is modified to include an action based on org.jboss.soa.esb.actions.SystemPrintln, the quickstart is able to generate a event log file. Note that the quickstart as distributed writes records to its DB via an SQL script. In the course of writing an automated test for this quickstart (/trunk/product/samples/quickstarts/tests/src/org/jboss/soa/esb/quickstart/test/HelloWorldSQLActionTest.java), I discovered the behavior described below. I was able to recreate this behavior with a simple class added to the quickstart's source tree. Steps to recreate the problem: 1) Copy the files listed below to their directories and rebuild ESB (ant dist). 2) cd to /trunk/product/samples/quickstarts/helloworld_sql_action 3) First - to verify that the new class ("TempTest") is able to write to the target DB: a. start mysql b. ant createdb c. ant runtemptest d. mysql --user=root --password= e. (in mysql) use test_sql_gateway f. (in mysql) select * from gateway_table; g. verify that (5) records have been written to the DB: +-----------+----------------------------------------------------------------------------+------------+ | unique_id | data_column | status_col | +-----------+----------------------------------------------------------------------------+------------+ | 1 | data 111111[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] | p | | 2 | data 22[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] | p | | 3 | data 333333333333111111[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] | p | | 4 | data d d d d[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] | p | | 5 | data data last record[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] | p | +-----------+----------------------------------------------------------------------------+------------+ 5 rows in set (0.01 sec) 4) To illustrate the first of two problems - where the org.jboss.soa.esb.actions.SystemPrintln action never fires. a. start up the ESB server b. ant dropdb c. ant createdb d. ant clean e. ant compile f. ant deploy g. ant runtemptest h. in the ESB server log, verify that these messages are not written for each of the (5) records) 13:20:36,650 INFO [STDOUT] ** 'message' attribute not set **: 13:20:36,650 INFO [STDOUT] Writing /tmp/TempTest.log i. verify that the /tmp/TempTest.log file is not created j. verify that no records are written to the gateway_table in the test_sql_gateway database 5) To illustrate the 2nd problem - where the org.jboss.soa.esb.actions.SystemPrintln action fires - given enough time - but results in records not being written to the DB a. In TempTest.java, uncomment the sleep() statement at line 63 - adds (30) seconds per record a. ant dropdb b. ant createdb c. ant clean d. ant compile e. ant runtemptest h. in the ESB server log, verify that these messages are written for each of the (5) records) 13:20:36,650 INFO [STDOUT] ** 'message' attribute not set **: 13:20:36,650 INFO [STDOUT] Writing /tmp/TempTest.log i. verify that this text is written to the /tmp/TempTest.log file: {unique_id=1, data_column=data 111111[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] }{unique_id=2, data_column=data 22[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] }{unique_id=3, data_column=data 333333333333111111[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] }{unique_id=4, data_column=data d d d d[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] }{unique_id=5, data_column=data data last record[jbesb-filename]/tmp/TempTest.log[/jbesb-filename] j. verify that no records are written to the gateway_table in the test_sql_gateway database Supporting files - attached to this JIRA - you'll need to use these files to recreate the problem. These files have not been checked into the trunk so as to not affect the ESB GA code freeze. build.xml - copy to trunk/product/samples/quickstarts/helloworld_sql_action/ TempTest.java - copy to trunk/product/samples/quickstarts/helloworld_sql_action/src/org/jboss/soa/esb/samples/quickstart/helloworldsqlaction/ jboss-esb.xml - copy to trunk/product/samples/quickstarts/helloworld_sql_action/ SystemPrintln.java - copy to trunk/product/rosetta/src/org/jboss/soa/esb/actions/ -- 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

4
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007