October 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2892) MessageAlerts is not thread safe

by Kevin Conner (JIRA)

MessageAlerts is not thread safe -------------------------------- Key: JBESB-2892 URL: https://jira.jboss.org/jira/browse/JBESB-2892 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.7 -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2875) Support sftp (ssh) keyboard-interactive auth

by Tom Eicher (JIRA)

Support sftp (ssh) keyboard-interactive auth -------------------------------------------- Key: JBESB-2875 URL: https://jira.jboss.org/jira/browse/JBESB-2875 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Reporter: Tom Eicher Priority: Minor JSch, as it is currently used in SecureFtpOverSSH, does only allow "password" authentication. However, this requires that the target system has ssh configured for "PasswordAuthentication yes" in sshd_conf, which is by default "no" nowadays... Connections will fail with {code} org.jboss.soa.esb.util.RemoteFileSystemException: com.jcraft.jsch.JSchException: Auth fail {code} To allow connections to servers configured like this, we need to support "keyboard-interactive" additionally: 1. SecureFtpImpl: change session.setConfig("PreferredAuthentications", "password"); to session.setConfig("PreferredAuthentications", "password,keyboard-interactive"); 2. SecureFtpUserInfo: additionally implement JSch interface UIKeyboardInteractive: {code} public String[] promptKeyboardInteractive( String destination, String name, String instruction, String[] prompt, boolean[] echo){ if(prompt.length!=1 || echo[0]!=false || this.password==null){ return null; } String[] response=new String[1]; response[0]=this.password; return response; } {code} -- 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, 6 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-2877) improve POSTHttpMethodFactory so it handles byte[] messages

by toby cabot (JIRA)

improve POSTHttpMethodFactory so it handles byte[] messages ----------------------------------------------------------- Key: JBESB-2877 URL: https://jira.jboss.org/jira/browse/JBESB-2877 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Environment: n/a Reporter: toby cabot I tried to use the HttpRouter to push messages to an external consumer (per http://www.jboss.org/community/wiki/HttpRouter). It almost worked but the messages had been converted to byte[] somewhere inside the ESB so when they got on the wire they looked like: 0x0000: 4500 00d9 213c 4000 4006 0000 7f00 0001 E...!<@.@....... 0x0010: 7f00 0001 f4d4 0050 85f6 5922 0afe 80de .......P..Y".... 0x0020: 8018 9f7e fecd 0000 0101 080a 2ea9 9208 ...~............ 0x0030: 2ea9 9208 504f 5354 202f 6d65 6469 6361 ....POST./medica 0x0040: 6c20 4854 5450 2f31 2e31 0d0a 436f 6e74 l.HTTP/1.1..Cont 0x0050: 656e 742d 5479 7065 3a20 7465 7874 2f78 ent-Type:.text/x 0x0060: 6d6c 3b63 6861 7273 6574 3d55 5446 2d38 ml;charset=UTF-8 0x0070: 0d0a 5573 6572 2d41 6765 6e74 3a20 4a61 ..User-Agent:.Ja 0x0080: 6b61 7274 6120 436f 6d6d 6f6e 732d 4874 karta.Commons-Ht 0x0090: 7470 436c 6965 6e74 2f33 2e30 2e31 0d0a tpClient/3.0.1.. 0x00a0: 486f 7374 3a20 6c6f 6361 6c68 6f73 742e Host:.localhost. 0x00b0: 7365 726d 6f2e 636f 6d0d 0a43 6f6e 7465 sermo.com..Conte 0x00c0: 6e74 2d4c 656e 6774 683a 2039 0d0a 0d0a nt-Length:.9.... 0x00d0: 5b42 4066 6438 3936 63 [B@fd896c I'll attach a patch to make POSTHttpMethodFactory handle byte[] as a special case (in the same spirit as JMSRouter#createJMSMessageWithObjectType() which also does 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

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2893) Remove build directory from svn in messagealerts quickstart

by Tom Cunningham (JIRA)

Remove build directory from svn in messagealerts quickstart ----------------------------------------------------------- Key: JBESB-2893 URL: https://jira.jboss.org/jira/browse/JBESB-2893 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.7 Remove build directory from svn in messagealerts quickstart -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1810) There is no retry limit when using transacted SQL listener

by Jiri Pechanec (JIRA)

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: http://jira.jboss.com/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

5
19
0 / 0

[JBoss JIRA] Created: (JBESB-2888) Change root page in standalone server to reflect new management console

by Kevin Conner (JIRA)

Change root page in standalone server to reflect new management console ----------------------------------------------------------------------- Key: JBESB-2888 URL: https://jira.jboss.org/jira/browse/JBESB-2888 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2889) RuleServiceCallHelper performance

by Kevin Conner (JIRA)

RuleServiceCallHelper performance --------------------------------- Key: JBESB-2889 URL: https://jira.jboss.org/jira/browse/JBESB-2889 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 RuleServiceCallHelper instantiates the factory on every invocation, through reflection, and reparses configuration parameters. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2890) WSSecurityInfoExtractor: Revert check for security token element before attempting to extract security information

by Daniel Bevenius (JIRA)

WSSecurityInfoExtractor: Revert check for security token element before attempting to extract security information ------------------------------------------------------------------------------------------------------------------ Key: JBESB-2890 URL: https://jira.jboss.org/jira/browse/JBESB-2890 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2891) MessageAlerts fails under 1.5

by Kevin Conner (JIRA)

MessageAlerts fails under 1.5 ----------------------------- Key: JBESB-2891 URL: https://jira.jboss.org/jira/browse/JBESB-2891 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 Also, changes made within the class are not thread safe. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2585) Add management alerting mechanism

by Kevin Conner (JIRA)

Add management alerting mechanism --------------------------------- Key: JBESB-2585 URL: https://jira.jboss.org/jira/browse/JBESB-2585 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.6 Add a mechanism whereby alerts can be specified based on the processing time or size of messages being processed. -- 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, 6 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2009