May 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2573) SOAPProcessor Programmer Guide Documentation

by Stelios Koussouris (JIRA)

SOAPProcessor Programmer Guide Documentation -------------------------------------------- Key: JBESB-2573 URL: https://jira.jboss.org/jira/browse/JBESB-2573 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Stelios Koussouris Priority: Minor The example in the following section is meant to refer to SOAPProcessor but it has a different example. Some additional info on the paramters to pass in might also come handy 11.7. Webservices/SOAP Action Configuration The <action ... /> configuration for this action is very straightforward. The action requires only one mandatory property value, which is the "jbossws-endpoint" property. This property names the JBossWS endpoint that the SOAPProcessor is exposing (invoking). <action name="PrintAMessage" class="test.PrintMessage"> <property name="information" value="Hello World!" /> <property name="repeatCount" value="5" /> </action> -- 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
4
0 / 0

[JBoss JIRA] Created: (JBESB-2548) HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager

by Tom Fennelly (JIRA)

HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager -------------------------------------------------------------------------------------------------- Key: JBESB-2548 URL: https://jira.jboss.org/jira/browse/JBESB-2548 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 HttpClientFactory.createHttpClient creates a HttpConnectionManager instance and configures the "max-total-connections". This is somewhat irrelevant however as the HttpClient still has a default limit of 1 (or 2 - I forget) max connections per connected host, so will never use anything like the configured "max-total-connections". One fix is to also set the "default-max-connections-per-host" on the HostConnectionManager params, with a default value of the value returned from a call to HttpConnectionManager.getParams().getMaxTotalConnections(). I think this would be fine because we only ever have 1 host per httpclient, but you could also provide an override config for situations where we have more. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-2328) JBossWS getPort not thread safe

by Kevin Conner (JIRA)

JBossWS getPort not thread safe ------------------------------- Key: JBESB-2328 URL: https://jira.jboss.org/jira/browse/JBESB-2328 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP2, 4.5 This has been seen on the SOA 4.3 GA release when concurrent access are being made to getPort. Caused by: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:538) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:525) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:513) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) at javax.xml.ws.Service.getPort(Service.java:116) I reproduced this by updating the Wise-core.jar and jbossesb-soap.jar to the ESB 4.4CP2 versions and modified the webservice_consumer_wise quickstart to send 20 concurrent messages. -- 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

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-2245) Investigate support for AS 5

by Kevin Conner (JIRA)

Investigate support for AS 5 ---------------------------- Key: JBESB-2245 URL: https://jira.jboss.org/jira/browse/JBESB-2245 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 We need to take a look at ESB within AS 5 to determine how this will impact the ESB. If the necessary changes are not too invasive then we should look at supporting AS5 as well as AS 4. The focus of the ESB 4.x stream is still the AS 4.x releases. -- 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
15
0 / 0

[JBoss JIRA] Created: (JBESB-2464) MessageImpl copy() method eats exceptions

by Kevin Conner (JIRA)

MessageImpl copy() method eats exceptions ----------------------------------------- Key: JBESB-2464 URL: https://jira.jboss.org/jira/browse/JBESB-2464 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 The copy() method in *both* MessageImpl classes eats the exception on failure. The methods trap Exception and translate it into the following throw new IOException(ex.toString()); This should be something like throw new IOException("Unexpected exception during copying", ex) ; so that the original cause of the exception is not lost. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBESB-2564) Change the default value of ExistsSql

by Kevin Conner (JIRA)

Change the default value of ExistsSql ------------------------------------- Key: JBESB-2564 URL: https://jira.jboss.org/jira/browse/JBESB-2564 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 CP2 Reporter: Taro Yasuma Fix For: 4.4 CP3 Please change the default value of ExistsSql to gain performance to initialize DatabaseInitializer. The current jbossesb.esb/jbossesb-service.xml is like: <server> <mbean code="org.jboss.internal.soa.esb.dependencies.DatabaseInitializer" name="jboss.esb:service=MessageStoreDatabaseInitializer"> ... <attribute name="ExistsSql">select * from message</attribute> ... </mbean> </server> But it should be "select count(*) from message". Should also check for other occurrences. -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-2542) Caching registry interceptor findEPR fails on empty response

by Kevin Conner (JIRA)

Caching registry interceptor findEPR fails on empty response ------------------------------------------------------------ Key: JBESB-2542 URL: https://jira.jboss.org/jira/browse/JBESB-2542 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP2 Reporter: Kevin Conner Priority: Minor Fix For: 4.4 CP3 Minor because we do not call this method but it does need to be fixed. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2527) Caching registry interceptor too tightly synchronized

by Kevin Conner (JIRA)

Caching registry interceptor too tightly synchronized ----------------------------------------------------- Key: JBESB-2527 URL: https://jira.jboss.org/jira/browse/JBESB-2527 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The caching interceptor is too tightly synchronized and can lead to performance degradation. This is my bad as I had intended for it to be an example of what is possible rather than a proper cache. Need to improve the performance for concurrent accesses. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2512) CourierFactory synchronizes around access to lifecycle resource

by Kevin Conner (JIRA)

CourierFactory synchronizes around access to lifecycle resource --------------------------------------------------------------- Key: JBESB-2512 URL: https://jira.jboss.org/jira/browse/JBESB-2512 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The courier factory has synchronized, static methods for registering and deregistering the couriers with its lifecycle resource. This can lead to deadlock during shutdown as a write lock is held by the lifecycle resource when destroying. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-2559) JmsConnectionPool.handleCloseSession is returning the session to the "free" pool before releaseing its resources

by Tom Fennelly (JIRA)

JmsConnectionPool.handleCloseSession is returning the session to the "free" pool before releaseing its resources ---------------------------------------------------------------------------------------------------------------- Key: JBESB-2559 URL: https://jira.jboss.org/jira/browse/JBESB-2559 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 Perhaps this method should release the session resources before doing anything else. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2009