June 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3356) maxThreads does not adequately propagate to HttpClient in HttpRouter, SOAPClient and SOAPProxy

by David Ward (JIRA)

maxThreads does not adequately propagate to HttpClient in HttpRouter, SOAPClient and SOAPProxy ---------------------------------------------------------------------------------------------- Key: JBESB-3356 URL: https://jira.jboss.org/browse/JBESB-3356 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Web Services Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Fix For: 4.9 First, some background: If one is trying to set the maxThreads for INVM invocation of a Service (where invmScope="GLOBAL"), then one would do it like so: <service .... invmScope="GLOBAL"> <property name="maxThreads" value="#"/> .... If one is trying to set the maxThreads for an ESB *aware* Listener's invocation of a Service, then one would do it like so: <service ...> <listeners> <xxx-listener ...> <property name="maxThreads" value="#"/> In each of these cases, an action can look for the maxThreads via it's passed in ConfigTree's parent: config.getParent().getAttribute(ListenerTagNames.MAX_THREADS_TAG). The HttpRouter takes advantage of this and *defaults* the max-total-connections property it hands to HttpClient to the value of the parent ConfigTree's maxThreads. Now, the problems: 1) HttpRouter only defaults HttpClient's max-total-connections property to the value of maxThreads. It should also default max-connections-per-host. 2) SOAPClient similarly only defaults HttpClient's max-total-connections property to the value of maxThreads. It should also default max-connections-per-host. 3) The SOAPProxy class "HttpSOAPProxyTransport" wraps HttpRouter, and creates it with a ConfigTree. However, this ConfigTree is a *clone* of the ConfigTree passed into the SOAPProxy, which does *not* have a parent ConfigTree. Thus, there is no parent to get the maxThreads from. Because of that, if someone wants to set the max-total-connections and max-connections-per-host, one has to do this: <action class="...SOAPProxy" ...> ... <property name="http-client-properties"> <http-client-property name="max-total-connections" value="#"/> <http-client-property name="max-connections-per-host" value="#"/> </property> or this: <action class="...SOAPProxy" ...> ... <property name="file" value="/file-containing-those-props.properties> In problems 1 and 2, the user needs to know to set the "max-connections-per-host" property. In problem 3, the user needs to know to set both the "max-total-connections" and "max-connections-per-host" properties. If the user doesn't know to do this, they might wonder "why am I getting such bad out-of-the-box performance?" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3276) soapui client fails to load multiple interfaces if authentication required

by Kevin Conner (JIRA)

soapui client fails to load multiple interfaces if authentication required -------------------------------------------------------------------------- Key: JBESB-3276 URL: https://jira.jboss.org/jira/browse/JBESB-3276 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP1 Reporter: Kevin Conner The reason for this is that only the last interface contains the wsdl context loaded using our httpclient, forcing prior interfaces to reload using the UrlWsdlLoader. This does not have knowledge of the authentication as we place it on the httpclient and it instantiates its own httpclient. -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3352) Upgrade picketlink to 1.0.3.final

by Kevin Conner (JIRA)

Upgrade picketlink to 1.0.3.final --------------------------------- Key: JBESB-3352 URL: https://jira.jboss.org/browse/JBESB-3352 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.7 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3309) Aggregator meta data in properties

by Kevin Conner (JIRA)

Aggregator meta data in properties ---------------------------------- Key: JBESB-3309 URL: https://jira.jboss.org/jira/browse/JBESB-3309 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 CP3 Reporter: Kevin Conner Fix For: 4.4 CP5 The MessageMulticaster creates an aggregation id and stores this value in message properties. Normally this does not prove to be an issue but when using invm transport it may cause issues. When the message is sent to multiple services, using pass by reference semantics, then all services will see the *same* properties and may, depending on timing, see the same aggregation id. The aggregation value should really be in the message context as this section is always duplicated when creating a reference, never shared. The problem we face is that users may already be referencing the property, especially if they are creating a fresh response message, so we need to think about handling this. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3343) security_saml QS fails during RequestedSecurityToken extraction.

by Kevin Conner (JIRA)

security_saml QS fails during RequestedSecurityToken extraction. ---------------------------------------------------------------- Key: JBESB-3343 URL: https://jira.jboss.org/browse/JBESB-3343 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP2 The behaviour of querying within JBossWS has changed, with methods now correctly interpreting the tag name as qualified. This may be the cause of this issue but needs to be verified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3291) wrong description of JMSEpr.messageSelector

by Marcel Sebek (JIRA)

wrong description of JMSEpr.messageSelector ------------------------------------------- Key: JBESB-3291 URL: https://jira.jboss.org/jira/browse/JBESB-3291 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Marcel Sebek All constructors of JMSEpr have description of the messageSelector the same as connectionFactory ("reference to the connection factory"). -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3289) BpmProcessor documentation anarchy

by Marcel Sebek (JIRA)

BpmProcessor documentation anarchy ---------------------------------- Key: JBESB-3289 URL: https://jira.jboss.org/jira/browse/JBESB-3289 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Marcel Sebek The documentation of BpmProcessor is misleading. In the programmers guide, there is the following: " The following jBPM commands have been implemented: - NewProcessInstanceCommand - StartProcessCommand - CancelProcessInstanceCommand - GetProcessInstanceVariablesCommand " The correct version is StartProcessInstanceCommand. A few lines bellow, there is NewProcessInstance-Command (the dash should probably not be there). Also SignalProcessInstanceCommand is mentioned but that command has been removed. Instead of "processdefinition", there should be "process-definition-name". In ServicesGuide, there is also a note about SignalProcessInstanceCommand and the "processdefinition" is there too. There may be more occurrences of these inconsistencies, I've mentioned just the most obvious. -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3346) JBossASContextPropagation should be using SecurityContextAssociation in AS5 environments, at present it uses SecurityAssociation

by Kevin Conner (JIRA)

JBossASContextPropagation should be using SecurityContextAssociation in AS5 environments, at present it uses SecurityAssociation -------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3346 URL: https://jira.jboss.org/browse/JBESB-3346 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.7 CP1 Reporter: Kevin Conner Assignee: Kevin Conner -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-3298) Update H2 version

by Gary Brown (JIRA)

Update H2 version ----------------- Key: JBESB-3298 URL: https://jira.jboss.org/jira/browse/JBESB-3298 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.8 Reporter: Gary Brown The current version uses h2-1.0.68.jar, which is placed in the server/default/lib folder on deployment to the app server. Could you update the version to a more recent version, e.g. 1.2.124 or higher, as the older version is causing concurrent update exceptions when used with riftsaw. -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3350) Incomplete access check in security_saml/picketlink-sts.war

by Kevin Conner (JIRA)

Incomplete access check in security_saml/picketlink-sts.war ----------------------------------------------------------- Key: JBESB-3350 URL: https://jira.jboss.org/browse/JBESB-3350 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor Fix For: 4.7 CP2 Need to remove http method constraints. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2010