April 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3177) In FtpImpl.java also setSoTimeout(_timeout); in initialize(boolean bConnect)

by jarkko Lietolahti (JIRA)

In FtpImpl.java also setSoTimeout(_timeout); in initialize(boolean bConnect) ---------------------------------------------------------------------------- Key: JBESB-3177 URL: https://jira.jboss.org/jira/browse/JBESB-3177 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: jarkko Lietolahti Currently FtpImpl.java (and the others) only set DataTimeout on m_oConn. We're seeing firewall issues where this is not enough and we need SoTimeout for the socket in order to avoid infinite waiting during __getReply(); So also call m_oConn.setSoTimeout(_timeout); Aka; if (_timeout > 0) { m_oConn.setDataTimeout(_timeout); // added by jarkko lietolahti, 9.2.2010 to address hanging replies from server m_oConn.setSoTimeout(_timeout); } -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-2905) FtpImpl timeout global and not always respected

by Tom Eicher (JIRA)

FtpImpl timeout global and not always respected ----------------------------------------------- Key: JBESB-2905 URL: https://jira.jboss.org/jira/browse/JBESB-2905 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.6, 4.5 Reporter: Tom Eicher org.jboss.internal.soa.esb.util.FtpImpl does look for a property org.jboss.soa.esb.ftp.timeout in jbossesb.sar/jbossesb-properties.xml, however: it does so only in 1 out of 3 constructors! ;-) code "String timeout = ModulePropertyManager..." should be moved from the "public FtpImpl (FTPEpr p_oP)" to the "protected void initialize (boolean bConnect)". other parameters in the 3 constructor should also be checked if they are respected in all three cases. Also: - "infinite" is not so good a default, as the thread will hang forever in case of firewall issues (I have one 48hrs old now ;-) even a ridiculous long one like 6hrs woule be better...("_timeout = 0;" in 2 places) - please add "<property name="org.jboss.soa.esb.ftp.timeout" value="60000"/>" to the default jbossesb-properties.xml so that people may know that this setting exists - please also allow configuration of timeout from ConfigTree (method "checkParams()" and Constant in "RemoteFileSystem") and from FileEpr. (and then add to doc ;-) Cheers & kind regards, 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

14 years

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-3259) SOAP Invocation selects the first (wrong) endpoint

by Kurt Stam (JIRA)

SOAP Invocation selects the first (wrong) endpoint -------------------------------------------------- Key: JBESB-3259 URL: https://jira.jboss.org/jira/browse/JBESB-3259 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kurt Stam This issue was discovered when running the "webservice_esb_bpel" quickstart which is part of the RiftSaw codebase. This quickstart is based on the ActiveBPEL quickstart, and it may make sense to move this quickstart from the RiftSaw codebase into the JBossESB codebase. In the final step notificationStep the MBeanSoapUIInvoker.getEndpoint(String wsdl, Properties httpClientProps) seems to simply pick the *first* endpoint, which is not the right one.. For more details please see: https://jira.jboss.org/jira/browse/RIFTSAW-192 -- 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

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-3084) Customize Context Root of HTTP Gateway

by Fernando Ribeiro (JIRA)

Customize Context Root of HTTP Gateway -------------------------------------- Key: JBESB-3084 URL: https://jira.jboss.org/jira/browse/JBESB-3084 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Fernando Ribeiro It would be nice to be able to customize the context root in jboss-esb.xml, just like in jboss-web.xml. http://fernandoribeiro.eti.br/2009/09/13/how-to-change-the-context-root-i... -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-3038) spring_aop QS does not work with signed JARs

by Kevin Conner (JIRA)

spring_aop QS does not work with signed JARs -------------------------------------------- Key: JBESB-3038 URL: https://jira.jboss.org/jira/browse/JBESB-3038 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: 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

14 years

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2981) Support textual file contents in file and remote gateways

by Kevin Conner (JIRA)

Support textual file contents in file and remote gateways --------------------------------------------------------- Key: JBESB-2981 URL: https://jira.jboss.org/jira/browse/JBESB-2981 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 The current implementation of these gateways generates the contents of the message as a byte[], as they must assume that they are binary. We should add the ability to create textual representations, instead of binary ones, by converting the byte[] to a String using a specified character set. -- 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

4
5
0 / 0

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

by Tom Eicher (JIRA)

jboss-esb.xml schema location fix --------------------------------- Key: JBESB-3017 URL: https://jira.jboss.org/jira/browse/JBESB-3017 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment, Documentation, Examples Affects Versions: 4.6, 4.5 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3082) Optional Parameter in XsltAction

by Fernando Ribeiro (JIRA)

Optional Parameter in XsltAction -------------------------------- Key: JBESB-3082 URL: https://jira.jboss.org/jira/browse/JBESB-3082 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Fernando Ribeiro The resultType parameter should really be optional, as described in the documentation. <action name="action1" class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction"> <property name="templateFile" value="/xsl/Stylesheet1.xsl" /> </action> .. gives me an error saying resultType needs to be there. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3081) Error in Documentation of XsltAction

by Fernando Ribeiro (JIRA)

Error in Documentation of XsltAction ------------------------------------ Key: JBESB-3081 URL: https://jira.jboss.org/jira/browse/JBESB-3081 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Fernando Ribeiro On page 98 of the Programmers Guide, it says "XslAction" instead of "XsltAction". -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3234) NotifyTCP assumes payload is characher based

by Tom Fennelly (JIRA)

NotifyTCP assumes payload is characher based -------------------------------------------- Key: JBESB-3234 URL: https://jira.jboss.org/jira/browse/JBESB-3234 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Tom Fennelly Priority: Minor Fix For: 4.9 org.jboss.soa.esb.notification.NotifyTCP assumes the message payload is a String (explicitly, or encoded as a byte[]). No need to make such a restrictive assumption. If it's a byte payload, just send it out onto the target socket as raw bytes - will work for any encoded payload type then. -- 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

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2010