March 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBESB-283) Support certificates with SFTP

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-283?page=all ] Mark Little closed JBESB-283. ----------------------------- Resolution: Out of Date > Support certificates with SFTP > ------------------------------ > > Key: JBESB-283 > URL: http://jira.jboss.com/jira/browse/JBESB-283 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta > Reporter: Kevin Conner > Assigned To: Bruno Georges > Fix For: 5.0 > > > The current SFTP implementation only uses username/password authentication, we should also support certificates. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1105) ESB Should have a good load generation framework

by James Williams (JIRA)

ESB Should have a good load generation framework ------------------------------------------------ Key: JBESB-1105 URL: http://jira.jboss.com/jira/browse/JBESB-1105 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Environment: I have created groovy scripts that simulate load and provide some TPS metrics. I used an external Groovy 1.1-Beta as my test for these scripts. Groovy is bootstrapped in the build script, so it's possible to swap it out with the ESB bundled, but I do not know if I'm doing any 1.1 specific stuff. Reporter: James Williams Assigned To: James Williams Priority: Minor There are 2 groovy scripts. One script, JMSLoadAgent.groovy, simulates load by dropping sample messages into a JMS gateway. There are a slew of properties entries to control the throttling of messages, and the payload file can be specified outside of the groovy script. This script is designed to be a template for other load scripts. For example, a load script that drops files into a directory that has a file system listener. The 2nd script, LoadReport.groovy, uses the JMX MBean stats at the service level to report TPS. you can specify one or more services as a comma separated list. And, there is a short circuit that will kill the reporter. The short cut is a bit crude, but it works. You specify the fastest ESB listener queue. When that queue depth is at 0, the report stops. The report will print out to the console, and to a properties file configured location. There are also several ant targets to run either the agent, reporter or both. I also include a sample ESB archive to test the quickstart and the services are hardwired so that one is distinctively faster than the other. These scripts should work for any service, provided the user adds the proper entries to "load.properties". There is no GUI for this yet, but I started out with a GUI, then realized that primary benefit of the load framework is the stats dumped into a log file or on the console. All other stuff is pretty straightforward with a simple properties file. The readme.txt probably needs a little beef, but I'm going to go ahead and check this in because I think it's going to be a very valuable contribution for users looking to load test and identify TPS at the service level. -- 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, 9 months

2
8
0 / 0

[JBoss JIRA] Updated: (JBESB-421) In-VM transport

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-421?page=all ] Mark Little updated JBESB-421: ------------------------------ Fix Version/s: 4.2.1 FP1 (was: 5.0) > In-VM transport > --------------- > > Key: JBESB-421 > URL: http://jira.jboss.com/jira/browse/JBESB-421 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Reporter: Mark Little > Assigned To: Mark Little > Priority: Critical > Fix For: 4.2.1 FP1 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1616) FTPNotify problems with passive mode

by Len DiMaggio (JIRA)

FTPNotify problems with passive mode ------------------------------------ Key: JBESB-1616 URL: http://jira.jboss.com/jira/browse/JBESB-1616 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Len DiMaggio Assigned To: Mark Little FTPNotify problems with passive mode project JIRA for SOA-P JIRA - http://jira.jboss.com/jira/browse/SOA-469 -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1333) Prevent messages from going to Dead Letter Service

by Mark Little (JIRA)

Prevent messages from going to Dead Letter Service -------------------------------------------------- Key: JBESB-1333 URL: http://jira.jboss.com/jira/browse/JBESB-1333 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1243) Sending a reply from the ActionProcessng pipeline...

by Kurt Stam (JIRA)

Sending a reply from the ActionProcessng pipeline... ---------------------------------------------------- Key: JBESB-1243 URL: http://jira.jboss.com/jira/browse/JBESB-1243 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.3 Okay, we all agree that the current situation is not ideal. It is been > in place for some time now and this is not the best point to raise > objections :) > > What we need to do is the following > - implement proper WS-A > - explicitly specify whether the service returns a response or not > - allow actions to return a message as the final action -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1379) JMS gateway and notifier do not support range of JMS messages

by Mark Little (JIRA)

JMS gateway and notifier do not support range of JMS messages ------------------------------------------------------------- Key: JBESB-1379 URL: http://jira.jboss.com/jira/browse/JBESB-1379 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.3 For some reason there's a disconnect as well: Gateway supports only ObjectMessage Notifier supports ObjectMessage or TextMessage at the very least we need to be consistent! -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1332) Gateways ignore maxThreads setting

by Kurt Stam (JIRA)

Gateways ignore maxThreads setting ---------------------------------- Key: JBESB-1332 URL: http://jira.jboss.com/jira/browse/JBESB-1332 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kurt Stam Gateways never seem to look for the maxThread setting and always end up single threaded. I don't know if this is a bug or an oversight. -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1398) Restructure labs page

by Mark Little (JIRA)

Restructure labs page --------------------- Key: JBESB-1398 URL: http://jira.jboss.com/jira/browse/JBESB-1398 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.1 CP1 Bring more immediately useful links up front on the page. Most of the information users and developers want is there, but spread over quite a few pages. Would be nice to have the front page hit the 80/20 mark. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1618) JMS/TX integration only works in very restricted circumstances

by Kevin Conner (JIRA)

JMS/TX integration only works in very restricted circumstances -------------------------------------------------------------- Key: JBESB-1618 URL: http://jira.jboss.com/jira/browse/JBESB-1618 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1, 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP2, 4.3 The current JMS/TX integration only works when the JNDI parameters are not specified as it relies on the java: namespace within JNDI. The result of this is that the integration falls back to a non transactional connection while the upper layers believe it is still transactional. As a consequence the message will never be sent. -- 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, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008