May 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-545) Internal services need to be deployed as part of sar deployment into AS

by Kevin Conner (JIRA)

Internal services need to be deployed as part of sar deployment into AS ----------------------------------------------------------------------- Key: JBESB-545 URL: http://jira.jboss.com/jira/browse/JBESB-545 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 2 There are mandatory services deployed into jbossesb-server which are not deployed into an AS environment. These services are required by the CBR. Deployment of the ESB sar into an AS environment should also include the definition of these 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-557) BPM using JMS transports causes connection pool problem

by Burr Sutter (JIRA)

BPM using JMS transports causes connection pool problem ------------------------------------------------------- Key: JBESB-557 URL: http://jira.jboss.com/jira/browse/JBESB-557 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 1 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 There is an attached project/quickstart that uses JMS queues for interaction between the BPM feature and ESB. Tested on the ESB Server deployment option (not tested with AS nor with BootStrapper). ant deploy ant deployProcess ant startProcess Now, run ant startProcess a several more times and it you'll connection pool errors. It seems that a transaction or a connection are being held/left open. Note: this must be tested on what is in trunk as of 5/4/2007. Not on MR1. -- 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

17 years, 6 months

2
6
0 / 0

[JBoss JIRA] Closed: (JBESB-369) WAR deployment

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-369?page=all ] Kevin Conner closed JBESB-369. ------------------------------ Resolution: Done Tomcat deployment has been shown to work with the following QSes, there may be outstanding issues with the remainder. The versions used to test the deployment are Tomcat 6.0.10 and Tomcat 5.5.23. aggregator helloworld helloworld_action helloworld_file_action helloworld_ftp_action helloworld_sql_action more_action static_router transform_CSV2XML transform_EDI2XML_Groovy_XSLT transform_XML2POJO transform_XML2XML_date_manipulation transform_XML2XML_simple The remainder should be tested as part of the further work in the linked task. At present there is no support for jbpm within the war deployment and the configuration of the ESB is a manual process (see linked tasks). The lifecycle has been tied into the initialisation and destruction of the war giving an orderly shutdown of the ESB. > WAR deployment > -------------- > > Key: JBESB-369 > URL: http://jira.jboss.com/jira/browse/JBESB-369 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 Milestone Release 2 > > > Support for running within a Tomcat container, BEA and IBM. -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-543) SystemPrintln action does not always output print message

by Kevin Conner (JIRA)

SystemPrintln action does not always output print message --------------------------------------------------------- Key: JBESB-543 URL: http://jira.jboss.com/jira/browse/JBESB-543 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2 Milestone Release 2 There is a route through SystemPrintln whereby the associated message does not get printed. This is evident in the aggregator QS -- 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

17 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml

by Burr Sutter (JIRA)

Federated: Multiple ESB Servers on same machine - jboss-bindings.xml -------------------------------------------------------------------- Key: JBESB-507 URL: http://jira.jboss.com/jira/browse/JBESB-507 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 1 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with unique services. A single message flow could be routed throughout all the different ESB/JVMs. The aggregator quickstart demonstrated this concept. In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that conflict with other running ESB Servers. You can now basically only run a single ESB Server per machine. The traditional approach to resolve this issue involves using the ServiceBindingManager MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI complains (upon ESB Server boot up). More details in the comments -- 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

17 years, 6 months

3
9
0 / 0

[JBoss JIRA] Work started: (JBESB-374) Getting Started Project Template for Eclipse/Ant

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-374?page=all ] Work on JBESB-374 started by Tom Cunningham. > Getting Started Project Template for Eclipse/Ant > ------------------------------------------------ > > Key: JBESB-374 > URL: http://jira.jboss.com/jira/browse/JBESB-374 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: Tom Cunningham > Priority: Optional > Fix For: 4.2 > > -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-542) Directory mismatch between RemoteGatewayListener and EdtFtpImpl of remote filesystem

by Kevin Conner (JIRA)

Directory mismatch between RemoteGatewayListener and EdtFtpImpl of remote filesystem ------------------------------------------------------------------------------------ Key: JBESB-542 URL: http://jira.jboss.com/jira/browse/JBESB-542 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 2 There is a mismatch between the two classes when downloading a file. RemoteGatewayListener expects the downloaded file to be placed in the normal temporary directory whereas EdtFtpImpl takes its directory from configuration. When RemoteGatewayListener asks for the download it only uses the name of the temporary file. EtdFtpImpl creates this file but in it's temporary directory and not that of the RemoteGatewayListener. RemoteGatewayListener therefore returns empty contents for the 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-541) MetaDataFilter requires message ID to be set prior to output processing

by Kevin Conner (JIRA)

MetaDataFilter requires message ID to be set prior to output processing ----------------------------------------------------------------------- Key: JBESB-541 URL: http://jira.jboss.com/jira/browse/JBESB-541 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 2 The MetaDataFilter requires a message ID for some of the EPRs being processed. This is not always set resulting in a NPE. The TwoWayCourier should ensure the message ID is set prior to calling the filter. -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Reopened: (JBESB-418) Catch-All/Otherwise/Default for CBR

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Kurt Stam reopened JBESB-418: ----------------------------- > Catch-All/Otherwise/Default for CBR > ----------------------------------- > > Key: JBESB-418 > URL: http://jira.jboss.com/jira/browse/JBESB-418 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Content Based Routing > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.2 Milestone Release 2 > > > For CBR, it currently has no exception handling. -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-418) Catch-All/Otherwise/Default for CBR

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Kurt Stam closed JBESB-418. --------------------------- Resolution: Done > Catch-All/Otherwise/Default for CBR > ----------------------------------- > > Key: JBESB-418 > URL: http://jira.jboss.com/jira/browse/JBESB-418 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Content Based Routing > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.2 Milestone Release 2 > > > For CBR, it currently has no exception handling. -- 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

17 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2007