April 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2097) ServiceInvoker Exception details

by Burr Sutter (JIRA)

ServiceInvoker Exception details -------------------------------- Key: JBESB-2097 URL: https://jira.jboss.org/jira/browse/JBESB-2097 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Burr Sutter Current the ServiceInvoker.deliverSync() method might throw the following exceptions: MessageDeliverException RegistryException FaultMessageException requestMessage = MessageFactory.getInstance().getMessage(); requestMessage.getProperties().setProperty(Environment.EXCEPTION_ON_DELIVERY_FAILURE,"true"); ServiceInvoker invoker = new ServiceInvoker("MyCategory", "Service99"); replyMessage = invoker.deliverSync(requestMessage,2000); A service name which does not exist results in a MessageDeliverException, with the following information exposed via a System.err.println(mde); 11:25:16,179 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx ception: Failed to deliver message [header: [ ]] to Service [MyCategory:Servic e99]. Check for errors. It would have made more sense for it to be a RegistryException and the actual message doesn't indicate that there is a lookup problem. Futhermore, a timeout results in the following MessageDeliverException: 11:45:06,278 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx ception: Failed to deliver message [header: [ To: InVMEpr [ PortReference < <wsa :Address invm://52455354456173794553425365727669636531/false?false#10000/>, <wsa :ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferenceProperties jb ossesb:type : urn:jboss/esb/epr/type/invm/> > ] ReplyTo: InVMEpr [ PortReference < <wsa:Address invm://thread-559/>, <wsa:ReferenceProperties jbossesb:passByVal ue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/in vm/> > ] ]] to Service [MyCategory:Service1]. Told not to retry. No indication that the problem is timeout and the "Told not to retry" is a bit terse. -- 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
11
0 / 0

[JBoss JIRA] Created: (JBESB-2524) RemoteGatewayListener ignores local FTP location

by George Gastaldi (JIRA)

RemoteGatewayListener ignores local FTP location ------------------------------------------------ Key: JBESB-2524 URL: https://jira.jboss.org/jira/browse/JBESB-2524 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: George Gastaldi Priority: Trivial The class RemoteGatewayListener does an ugly checking for the temporary directory and ignores any attempt to define a local directory: This is the actual code : .. protected void checkMyParms() throws ConfigurationException, RegistryException, GatewayException { try { File temp = File.createTempFile("FTPdown", ".tmp"); temp.delete(); String localDir = temp.getParent(); if (null==localDir) localDir=new File("").getAbsolutePath(); config.setAttribute(RemoteFileSystem.PARMS_LOCAL_DIR, localDir); final String remoteDir = config.getAttribute(ListenerTagNames.FILE_INPUT_DIR_TAG) ; config.setAttribute(RemoteFileSystem.PARMS_REMOTE_DIR, remoteDir); EPR epr = ListenerUtil.assembleEpr(config); if (epr instanceof FTPEpr) { FTPEpr ftpEpr = (FTPEpr) epr; RemoteFileSystem rfs = RemoteFileSystemFactory.getRemoteFileSystem(ftpEpr, true); rfs.quit(); } else { throw new GatewayException("This Gateway only accepts FTP and SFTP."); } } catch (IOException ex) { throw new ConfigurationException(ex); } catch (RemoteFileSystemException ex) { throw new ConfigurationException(ex); } } ... The Listener should check first if a path has been defined before attempting to discover the local directory. BTW, the first lines could be replaced by System.getProperty("java.io.tmpdir"), instead of creating and deleting a file (expensive unnecessary operation). -- 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
14
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-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-2537) JAXR Registry service searches should qualify the search using the organizational key

by Kevin Conner (JIRA)

JAXR Registry service searches should qualify the search using the organizational key ------------------------------------------------------------------------------------- Key: JBESB-2537 URL: https://jira.jboss.org/jira/browse/JBESB-2537 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 At present the calls to the BusinessQueryManager pass in null as the organizational key but this would pick up other deployments in the same DB, once supported. -- 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
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2009