March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2106) JBR listener doesn't return error to a client

by Martin Vecera (JIRA)

JBR listener doesn't return error to a client --------------------------------------------- Key: JBESB-2106 URL: https://jira.jboss.org/jira/browse/JBESB-2106 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Martin Vecera When I'm using JBR listener in synchronous way, I'm not able to find out whether the message was successfully delivered. JBossRemotingGatewayListener, method invoke(), line 345: Object response = messageDeliveryAdapter.deliverSync(invocationRequest, 20000); When an exception is thrown (e.g. SecurityServiceException), the client is never informed of this problem. As a response it simply gets null. I'd expect for the client to get the exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-2259) Create an Emailer action.

by Daniel Bevenius (JIRA)

Create an Emailer action. ------------------------- Key: JBESB-2259 URL: https://jira.jboss.org/jira/browse/JBESB-2259 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Fix For: 4.5 feature requests Create a action that can send mails. Like the notifier but that can be used as a router/wiretap in the action pipeline. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-1965) Poor Exception Message "doesn't define a Message-Aware Listener"

by Burr Sutter (JIRA)

Poor Exception Message "doesn't define a Message-Aware Listener" ---------------------------------------------------------------- Key: JBESB-1965 URL: https://jira.jboss.org/jira/browse/JBESB-1965 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Burr Sutter Priority: Minor This message should also indicate that an InVM listener can also be used by adding invmScope="GLOBAL" to the service declaration. 12:31:43,355 WARN [ServiceController] Problem starting service jboss.esb:deploy ment=Quickstart_helloworld_http.esb java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service co nfiguration for Service 'HelloWorld:HelloWorld_HTTP' doesn't define a Message-Aw are Listener (i.e. is-gateway='false'). at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration .java:138) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J Boss4ESBDeployment.java:99) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2500) Identify any issues with using IBM MQ and provide direct support within the ESB codebase

by Kevin Conner (JIRA)

Identify any issues with using IBM MQ and provide direct support within the ESB codebase ---------------------------------------------------------------------------------------- Key: JBESB-2500 URL: https://jira.jboss.org/jira/browse/JBESB-2500 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP4 Reporter: Kevin Conner Fix For: 4.2.1 CP5 TomF has already done some work on this task, in relation to a customer enquiry. The solution he created was to provide an adapter to the MQ ConnectionFactory/Connection classes which could then be referred to from within the ESB configuration. The main purpose of the adapter was to handle the requirement that there only be a single session per connection when executing within a transactional context. We need to move this requirement back into the ESB codebase and support it directly within the JMS connection pool. An additional part of this task will be to identify any further issues which arise and create appropriate JIRAs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1687) Update to bpm_orchestration3 - replace signalling with callback

by Len DiMaggio (JIRA)

Update to bpm_orchestration3 - replace signalling with callback --------------------------------------------------------------- Key: JBESB-1687 URL: http://jira.jboss.com/jira/browse/JBESB-1687 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Len DiMaggio Priority: Minor Project JIRA for SOA-520 -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1847) jBPM upload authentication is enforced for all quickstarts

by Kevin Conner (JIRA)

jBPM upload authentication is enforced for all quickstarts ---------------------------------------------------------- Key: JBESB-1847 URL: http://jira.jboss.com/jira/browse/JBESB-1847 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP3 Reporter: Kevin Conner Fix For: 4.2.1 CP4 The upload credentials should only be enforced for the jBPM quickstarts and not enforced for all. -- 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

16 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2452) SoapUIClientService: not handling nested collections properly

by Kevin Conner (JIRA)

SoapUIClientService: not handling nested collections properly ------------------------------------------------------------- Key: JBESB-2452 URL: https://jira.jboss.org/jira/browse/JBESB-2452 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2266) WARNING on OracleDialect used with Management console

by Kevin Conner (JIRA)

WARNING on OracleDialect used with Management console ----------------------------------------------------- Key: JBESB-2266 URL: https://jira.jboss.org/jira/browse/JBESB-2266 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.2.1 CP4 4.2.1 CP project issue for SOA-857. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1774) Messages are returned to client from the wrong service

by Mika Leino (JIRA)

Messages are returned to client from the wrong service ------------------------------------------------------ Key: JBESB-1774 URL: http://jira.jboss.com/jira/browse/JBESB-1774 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Environment: Windows Server 2003 Reporter: Mika Leino Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml We have a setup in which a client calls an ESB service (service A) with a webservice interface and this service then calls on another ESB service (service B). Both of the services have their action pipelines set to be "RequestResponse". For some reason the first attempt to handle the client's message always fails as the message is returned to the client from service B. As the message never returns to service A it assumes an unresponsive EPR and resends the message which on the second attempt returns to service A. The first attempt looks like this: client -> service A -> service B -> client And the second like this: (client ->) service A -> service B -> service A -> client Unfortunately the client interpreters the first response as the one it is waiting for and fails as service A has not made the necessary changes to the message. The second attempt produces a valid response but the client is no longer listening for it. -- 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

16 years, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-1904) The stateful working memory cannot be disposed based on rules processing

by Jiri Pechanec (JIRA)

The stateful working memory cannot be disposed based on rules processing ------------------------------------------------------------------------ Key: JBESB-1904 URL: https://jira.jboss.org/jira/browse/JBESB-1904 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 It should be very useful to control disposing of stateful working memory based on outcome of rules execution. Unfortunately this is not possible as the dispose message property is checked before rule execution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

4
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009