July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-743) ServiceInvoker ignores ReplyTo

by Mark Little (JIRA)

ServiceInvoker ignores ReplyTo ------------------------------ Key: JBESB-743 URL: http://jira.jboss.com/jira/browse/JBESB-743 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Priority: Critical ServiceInvoker uses the default reply-to routine on CourierUtil without checking to see if there's a ReplyTo already set in the Message header. -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-679) ServiceInvoker shouldn't need synchronous/asynchronous option

by Mark Little (JIRA)

ServiceInvoker shouldn't need synchronous/asynchronous option ------------------------------------------------------------- Key: JBESB-679 URL: http://jira.jboss.com/jira/browse/JBESB-679 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little At this level, all of the necessary information is within the Message and defined by the WS-A rules: if there's a ReplyTo then it's synchronous. Otherwise, it's not. -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-680) ServiceInvoker doesn't inspect the header when deciding sync versus async

by Mark Little (JIRA)

ServiceInvoker doesn't inspect the header when deciding sync versus async ------------------------------------------------------------------------- Key: JBESB-680 URL: http://jira.jboss.com/jira/browse/JBESB-680 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little If the Message header is set, then async versus sync should be based on the WS-A rules. If the header isn't set then a default ReplyTo could be used if the user defines sync/async delivery. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-675) Eliminate org.jboss.soa.esb.listeners.message.Invoker

by Tom Fennelly (JIRA)

Eliminate org.jboss.soa.esb.listeners.message.Invoker ----------------------------------------------------- Key: JBESB-675 URL: http://jira.jboss.com/jira/browse/JBESB-675 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 And change all code using it to use ServiceInvoker. This is related to JBESB-575, but I was afraid to change this code for 4.2MR3. This code (and the code that uses it) is just so badly put together, it's scary. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-757) Remove mq Topic from registering in jboss-esb-console

by Tom Cunningham (JIRA)

Remove mq Topic from registering in jboss-esb-console ------------------------------------------------------ Key: JBESB-757 URL: http://jira.jboss.com/jira/browse/JBESB-757 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 jboss-esb-console is registering an mq MBean that conflicts with one of the same topic name in smooks.esb. Additionally, if you configure only jboss-messaging, you might not be able to load this class. We need to remove it from resources/jboss-esb-console-service.xml. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-753) Add a Quickstart for NotifyFiles

by Tom Cunningham (JIRA)

Add a Quickstart for NotifyFiles -------------------------------- Key: JBESB-753 URL: http://jira.jboss.com/jira/browse/JBESB-753 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 Adding a QS for NotifyFiles. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-760) Rewrite lifecycle identity association

by Kevin Conner (JIRA)

Rewrite lifecycle identity association -------------------------------------- Key: JBESB-760 URL: http://jira.jboss.com/jira/browse/JBESB-760 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 At present the lifecycle identiy is stored in a thread local. Prior to the recent asynchronous mechanism changes this worked as every thread inherited the context when created. Some modifications have recently been made to explicitly initialise the association but this is likely to be broken in the future. A better solution will be to associate the lifecycle identity with the thread context classloader as every async mechanism should be initialising this correctly. This will then 'just work' provided that the TCC is initialised correctly. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-759) Update scout jar to the current release candidate

by Kevin Conner (JIRA)

Update scout jar to the current release candidate ------------------------------------------------- Key: JBESB-759 URL: http://jira.jboss.com/jira/browse/JBESB-759 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kurt Stam Priority: Minor Fix For: 4.2 Update the scout jar to the latest release. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-694) ERROR [ClosedInterceptor] ClosedInterceptor.ClientConsumerDelegate

by Burr Sutter (JIRA)

ERROR [ClosedInterceptor] ClosedInterceptor.ClientConsumerDelegate ------------------------------------------------------------------ Key: JBESB-694 URL: http://jira.jboss.com/jira/browse/JBESB-694 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Priority: Minor Fix For: 4.2 The following messages are shown on the AS console (AS 4.2 + Messaging + WS 2.0 updates + ESB): 15:38:28,078 INFO [STDOUT] 1 15:38:28,093 ERROR [ClosedInterceptor] ClosedInterceptor.ClientConsumerDelegate[ 20]: method receive() did not go through, the interceptor is IN_CLOSE This happens upon undeployment of a .esb archive. You can simply just delete it from the deploy directory to see the message. Or in helloworld use 'ant deploy' and then 'ant undeploy' Note: the STDOUT 1 also appears when you simply update/touch the jboss-esb.xml. I didn't go digging for the class that must be using a System.out.println(1). Now, I do like the fact that you see some activity on the console when a .esb. is undeployed as that is "user friendly" or if we perform a hot redeployment, however, these 2 messages are not that useful in their content. I've been seeing the "1" now for a couple of months. -- 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, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-756) Contextualised information not being used in event driven gateways

by Kevin Conner (JIRA)

Contextualised information not being used in event driven gateways ------------------------------------------------------------------ Key: JBESB-756 URL: http://jira.jboss.com/jira/browse/JBESB-756 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 We currently have three gateways which are event driven instead of polled, JBossRemotingGatewayListener, HibernateInterceptor and JcaInflowGateway. These gateways receive requests driven from an external source and on unknown threads. At present we track courier assignment (and soon JMS pools) using thread context information. These gateways are unaware of this association and do not reestablish it prior to invoking ESB functionality. The result of this is that the courier assigment will no longer be associated with the deployed artifact and may not be cleared up when undeployed. -- 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, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007