January 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2617) InVMcourier deliver lockstep needs reworking

by Kevin Conner (JIRA)

InVMcourier deliver lockstep needs reworking -------------------------------------------- Key: JBESB-2617 URL: https://jira.jboss.org/jira/browse/JBESB-2617 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Kevin Conner Fix For: 4.4 CP4 The code loops, using a 5ms wait, and this has a performance impact. This needs to be reworked so that it does not cycle in this manner. -- 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

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2341) local date translating error when run esb smooks examples

by Feng Qian (JIRA)

local date translating error when run esb smooks examples --------------------------------------------------------- Key: JBESB-2341 URL: https://jira.jboss.org/jira/browse/JBESB-2341 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Feng Qian I am a jboss tools guy. When I did the task for importing ESB examples to eclipse workspace, I got a issue like: https://jira.jboss.org/jira/browse/JBIDE-3654. I just fixed this issue by adding <param name="locale-language">en</param> to smooks file. I do not know if the runtime examples has this issue because I can test it on my machine. If not, please close this jira. -- 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

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2124) Message Count and Message Count (avg) don't differ

by Jaroslaw Kijanowski (JIRA)

Message Count and Message Count (avg) don't differ -------------------------------------------------- Key: JBESB-2124 URL: https://jira.jboss.org/jira/browse/JBESB-2124 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP1 Reporter: Jaroslaw Kijanowski $SUBJECT (see avg.png) + what does it mean to have a message count average? An average over what time? per minute? I guess per 'collection interval' ... but we have already an avg column for all metrics... why a separate metric? -- 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

14 years, 9 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-2051) Exception thrown by wise soap client during deployment are not easy to understand

by Stefano Maestri (JIRA)

Exception thrown by wise soap client during deployment are not easy to understand --------------------------------------------------------------------------------- Key: JBESB-2051 URL: https://jira.jboss.org/jira/browse/JBESB-2051 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Reporter: Stefano Maestri Assignee: Stefano Maestri -- 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

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1992) EBWS Security needs rework and unification

by Jiri Pechanec (JIRA)

EBWS Security needs rework and unification ------------------------------------------ Key: JBESB-1992 URL: https://jira.jboss.org/jira/browse/JBESB-1992 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Security, Web Services Affects Versions: 4.4 Reporter: Jiri Pechanec There is now security implementation at two levels - specifying webservice="security" attribute enables JBossWS security handler - specifying security elemnt enables WSSecuritySoapExtractor The WSSecuritySoapExtractor operates at XML/DOM level which means that is completely independent on JBossWS security handler. Please consider unifying the configuration and JBossWS facility use. Morever check the WSSecurityInfoExtractor if there is also a way to use JBossWS functions instead of Smooks parsing. -- 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

14 years, 9 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2273) Extend BusinessRulesProcessor action to support entry-point

by Burr Sutter (JIRA)

Extend BusinessRulesProcessor action to support entry-point ----------------------------------------------------------- Key: JBESB-2273 URL: https://jira.jboss.org/jira/browse/JBESB-2273 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Burr Sutter BusinessRulesProcessor allows for a "stateful" rules session as of ESB 4.4, however, it doesn't allow subsequent inbound messages to inject those messages into the already existing stateful rules session via the entry-point API. <action class="org.jboss.soa.esb.actions.BusinessRulesProcessor" name="OrderDiscountBasedOnCustomerHistory"> <property name="ruleSet" value="OrderDiscountOnMultipleOrders.drl" /> <property name="ruleReload" value="false" /> <property name="stateful" value="true" /> <property name="object-paths"> <object-path esb="body.TheOrderHeader" /> <object-path esb="body.TheCustomer" /> </property> </action> We might extend this like so: <object-path esb="body.TheOrderHeader" entry-point="OrderStream" /> <object-path esb="body.TheCustomer" entry-point="CustomerStream" /> The date time stamp should be based on message DOB but perhaps overrideable here as well. The use of entry-points would also mean that the Rules session is "self cleaning" as it automatically garbage collects stale facts. -- 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

14 years, 10 months

6
10
0 / 0

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

by Jiri Pechanec (JIRA)

SOAPProxies on different services shares configuration ------------------------------------------------------ Key: JBESB-3021 URL: https://jira.jboss.org/jira/browse/JBESB-3021 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: ER4 Reporter: Jiri Pechanec Priority: Critical Attachments: soapproxy-breaker.zip 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

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-2947) InternalSOAPProxyWsdlLoader hangs on ESB restart

by David Ward (JIRA)

InternalSOAPProxyWsdlLoader hangs on ESB restart ------------------------------------------------ Key: JBESB-2947 URL: https://jira.jboss.org/jira/browse/JBESB-2947 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: David Ward Assignee: David Ward Fix For: 4.7 Tom F. and I noticed a problem with the InternalSOAPProxyWsdlLoader's use of JBossWS's internal SPI, where it is *still* using an http URLConnection under-the-hood. This is an issue since on restart, Tomcat's http connector is not be available yet. This causes the main thread of the boot-up to hang. -- 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

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2903) Backwards incompatibility with HttpResponse

by Lukáš Petrovický (JIRA)

Backwards incompatibility with HttpResponse ------------------------------------------- Key: JBESB-2903 URL: https://jira.jboss.org/jira/browse/JBESB-2903 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Lukáš Petrovický Fix For: 4.7 In SOA-P 5.0 ER1 (which leverages ESB 4.7 trunk), we found the following backwards-incompatible change while compiling one of our tests (based on the http_2way_ssl QS): [javac] /home/lpetrovi/Work/QE/tests/quickstarts/https_2way_ssl/src/org/jboss/soa/esb/samples/https/client/HttpResponsePrinter.java:35: incompatible types [javac] found : java.util.List<org.jboss.soa.esb.http.HttpHeader> [javac] required: java.util.List<org.jboss.soa.esb.actions.routing.http.HttpHeader> [javac] List<HttpHeader> headers = httpResponse.getHeaders(); [javac] ^ [javac] Note: /home/lpetrovi/Work/QE/tests/quickstarts/https_2way_ssl/src/org/jboss/soa/esb/samples/https/client/HttpResponsePrinter.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. As you can see, the getHeaders() method now returns a different type than it used to. In my opinion, breaking backwards compatibility would be OK when switching to a new major version of ESB, but this is not the case. I also noticed that the QS in question has been updated in the ESB to reflect this change, so I expect the view of the ESB team is that this is not a valid bug. -- 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

14 years, 10 months

3
10
0 / 0

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

by Kevin Conner (JIRA)

ExecuteJobCommand in ESB's jBPM integration doesn't roll back the transaction even if the action handler throws Exception ------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3159 URL: https://jira.jboss.org/jira/browse/JBESB-3159 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

14 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2010