March 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3198) Disable juddi default jndi properties

by Kevin Conner (JIRA)

Disable juddi default jndi properties ------------------------------------- Key: JBESB-3198 URL: https://jira.jboss.org/jira/browse/JBESB-3198 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP3 Reporter: Kevin Conner Fix For: 4.4 CP4 -- 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, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-3196) jboss-esb.xml schema location fix

by Kevin Conner (JIRA)

jboss-esb.xml schema location fix --------------------------------- Key: JBESB-3196 URL: https://jira.jboss.org/jira/browse/JBESB-3196 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment, Documentation, Examples Affects Versions: 4.5, 4.6 Reporter: Tom Eicher 1. All jboss-esb.xml still point to http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... where nowadays it should be http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... 2. shouldn't we use version 1.1.0 now ? 3. please include a xsi:schemaLocation xsi:schemaLocation="http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem..."> Cheers, Tom. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2457) SoapUIClientService does not populate request attributes

by Kevin Conner (JIRA)

SoapUIClientService does not populate request attributes -------------------------------------------------------- Key: JBESB-2457 URL: https://jira.jboss.org/jira/browse/JBESB-2457 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP2, 4.5 Reporter: Joakim Sandström SoapUIClientService only appears to handle population of text elements and not the attributes. expected request: <soapenv:Body> <ns:updateCustomer customerId="124343"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> actual request: <soapenv:Body> <ns:updateCustomer customerId="?"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> -- 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, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2868) InVMTransport deliver NPE on missing service

by Kevin Conner (JIRA)

InVMTransport deliver NPE on missing service -------------------------------------------- Key: JBESB-2868 URL: https://jira.jboss.org/jira/browse/JBESB-2868 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP4 My bad, the code is referencing the entry before checking it is null. -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3199) Operations on the JBoss ESB Statistics level not working

by Kevin Conner (JIRA)

Operations on the JBoss ESB Statistics level not working -------------------------------------------------------- Key: JBESB-3199 URL: https://jira.jboss.org/jira/browse/JBESB-3199 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.7 Reporter: Jaroslaw Kijanowski Assignee: Tom Cunningham Fix For: 4.7 CP1 In the admin-console I go to JBoss ESB Statistics -> Control -> Stop deployment: java.lang.Exception: Operation [stop] not found on bean [jboss.esb:service=MessageCounter] at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:521) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:510) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) I guess the rhq-plugin.xml file should not list <operation name="start" displayName="Start deployment" description="Start the JBoss ESB deployment"/> <operation name="stop" displayName="Stop deployment" description="Stop the JBoss ESB deployment"/> <operation name="create" displayName="Move .esb deployment into the create state" description="Move the .esb deployment into the create state"/> <operation name="destroy" displayName="Move .esb deployment into the destroy state" description="Move the .esb deployment into the destroy state"/> for the MessageCounterService. -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3184) org.jboss.soa.esb.actions.routing.http.HttpRouter port sharing!

by Jurij (JIRA)

org.jboss.soa.esb.actions.routing.http.HttpRouter port sharing! --------------------------------------------------------------- Key: JBESB-3184 URL: https://jira.jboss.org/jira/browse/JBESB-3184 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Environment: Linux Debian, JDK 1.6.0_10 Reporter: Jurij Priority: Critical Create two services, both with org.jboss.soa.esb.actions.routing.http.HTTPRouter instance. Define for service A a URL without port, for service B URL with port for example URL for service A -> http://myserver1/bla URL for service B -> http://myserver2:8080/bla deploy both services, send message to service A and to Service B all OK. And now redeploy service B and send a message to service A. In this moment service A will connect URL http://myserver1:8080/bla !!!! -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3187) SOAPClient and EsbWsdlLoader on different services shares configuration

by Kevin Conner (JIRA)

SOAPClient and EsbWsdlLoader on different services shares configuration ----------------------------------------------------------------------- Key: JBESB-3187 URL: https://jira.jboss.org/jira/browse/JBESB-3187 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 -- 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, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-3188) HttpClient connection parameters being ignored

by Kevin Conner (JIRA)

HttpClient connection parameters being ignored ---------------------------------------------- Key: JBESB-3188 URL: https://jira.jboss.org/jira/browse/JBESB-3188 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3186) SOAPProxies on different services shares configuration

by Kevin Conner (JIRA)

SOAPProxies on different services shares configuration ------------------------------------------------------ Key: JBESB-3186 URL: https://jira.jboss.org/jira/browse/JBESB-3186 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: ER4 Reporter: Jiri Pechanec Assignee: David Ward Priority: Critical Fix For: 4.7 CP1 If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then the configuration is shared between them. Check the attached example 1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The execution is performed correctly and target service is invoked. 2) Enable Proxy-breaker service but disable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. Although you are invoking the first service the invocation will fail due to strict SSL setting. 3) Enable Proxy-breaker service and enable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. The execution is performed correctly and target service is invoked. It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy settings of Proxy service. -- 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, 1 month

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3152) ExecuteJobCommand in ESB's jBPM integration doesn't roll back the transaction even if the action handler throws Exception

by Toshiya Kobayashi (JIRA)

ExecuteJobCommand in ESB's jBPM integration doesn't roll back the transaction even if the action handler throws Exception ------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3152 URL: https://jira.jboss.org/jira/browse/JBESB-3152 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP3 Reporter: Toshiya Kobayashi In case that Job execution of an async node is processed by JCA inflow messaging service (SOA-P integration), the transaction is not rolled back even if the action handler throws Exception/RuntimeException. The transaction is commtted and then org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand.executeJob() kicks one retry which would lead to duplicate commit. It looks inconsistent with docs: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/... ============ If execution of a command message fails, the transaction will be rolled back. After that, a new transaction will be started that adds the error message to the message in the database. The command executor filters out all messages that contain an exception. ============ I've attatched a reproducer. - unzip jobexecution.zip - modify build.properties - ant deploypar - ant deploy - ant ejbclient (or access jbpm-console to start process instance) - access jbpm-console to check process instance's id which is created by the action handler (which should be rolled back) -- 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, 1 month

2
7
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 2010